Platform References
@_platform-references/org-variables
Output Format Selector SKILL
Goal
Select the optimal structured response format from the 48 available types based on user intent and available data.
Response Type Decision Matrix
Meeting-Related Queries
| Intent Pattern |
Response Type |
Key Data Required |
| "What meetings today/tomorrow" |
meeting_list |
calendar_events |
| "How many meetings this week" |
meeting_count |
calendar_events count |
| "Prep for next meeting" |
next_meeting_command_center |
meeting + contact + deal |
| "Meeting briefing for X" |
meeting_briefing |
meeting + context |
| "What's on my calendar" |
calendar |
calendar_events + availability |
| "Time analysis/breakdown" |
time_breakdown |
meeting hours by type |
Pipeline-Related Queries
| Intent Pattern |
Response Type |
Key Data Required |
| "Which deals need attention" |
pipeline_focus_tasks |
deals + activity staleness |
| "Pipeline health/status" |
pipeline |
deals with health metrics |
| "Deal rescue/at-risk" |
deal_rescue_pack |
at-risk deals + rescue plan |
| "Deal forecast" |
pipeline_forecast |
weighted pipeline |
| "Stage analysis" |
stage_analysis |
conversion rates by stage |
| "Deal health check" |
deal_health |
health scores + risk factors |
| "Deal slippage alerts" |
deal_slippage_guardrails |
slipping deals + actions |
Email-Related Queries
| Intent Pattern |
Response Type |
Key Data Required |
| "Draft email/follow-up" |
email |
contact + context |
| "Email inbox triage" |
followup_zero_inbox |
email threads needing reply |
| "Post-meeting follow-up" |
post_meeting_followup_pack |
meeting + transcript + drafts |
Daily Briefings
| Intent Pattern |
Response Type |
Key Data Required |
| "Catch me up" |
daily_brief |
schedule + deals + tasks |
| "What should I focus on" |
daily_focus_plan |
priorities + tasks |
Contact & Relationship Queries
| Intent Pattern |
Response Type |
Key Data Required |
| "Tell me about X (person)" |
contact |
contact + deals + activities |
| "Contact relationship status" |
contact_relationship |
relationship strength |
| "Communication history" |
communication_history |
emails + calls + meetings |
| "Company intelligence" |
company_intelligence |
company + contacts + deals |
Task & Activity Queries
| Intent Pattern |
Response Type |
Key Data Required |
| "What tasks are due" |
task |
tasks with due dates |
| "Create a task" |
task_creation |
task details + contact |
| "Log an activity" |
activity_creation |
activity type + contact |
| "Activity breakdown" |
activity_breakdown |
activities by type |
Analytics & Insights
| Intent Pattern |
Response Type |
Key Data Required |
| "Performance review" |
sales_coach |
metrics comparison |
| "Goal tracking" |
goal_tracking |
goals + progress |
| "Trend analysis" |
trend_analysis |
metric trends |
| "Team comparison" |
team_comparison |
user vs team metrics |
| "Data quality check" |
data_quality |
missing fields, duplicates |
Write Operations
| Intent Pattern |
Response Type |
Notes |
| Any create/update/delete |
action_summary |
After successful write |
| Multiple entity selection |
contact_selection |
When disambiguation needed |
| Proposal linking |
proposal_selection |
When linking task to proposal |
Response Selection Rules
Priority Order
- Deterministic V1 sequences take precedence - If V1 router matches, use sequence response type
- Entity presence determines format - Contact query with full data ->
contact
- Time awareness - Morning (before 12pm):
daily_brief shows today focus
- Preview for writes - All write operations use
is_simulation: true first
- Fallback to text - Unknown patterns use text with action links
Sequence to Response Type Mapping
| Sequence Key |
Response Type |
seq-next-meeting-command-center |
next_meeting_command_center |
seq-post-meeting-followup-pack |
post_meeting_followup_pack |
seq-pipeline-focus-tasks |
pipeline_focus_tasks |
seq-deal-rescue-pack |
deal_rescue_pack |
seq-deal-map-builder |
deal_map_builder |
seq-daily-focus-plan |
daily_focus_plan |
seq-followup-zero-inbox |
followup_zero_inbox |
seq-deal-slippage-guardrails |
deal_slippage_guardrails |
seq-catch-me-up |
daily_brief |
Action Vocabulary
All responses must use these standard actions via onActionClick:
open_contact - Navigate to contact detail page
open_deal - Navigate to deal detail page
open_meeting - Navigate to meeting detail page
open_task - Navigate to task detail page
open_external_url - Open URL in new tab
Output Contract
interface SkillResult {
status: "success" | "partial" | "failed";
summary: string;
data: {
recommended_type: CopilotResponseType;
confidence: number;
reasoning: string;
required_data: string[];
preview_mode: boolean;
};
}
Usage
This skill should be consulted when:
detectAndStructureResponse() cannot determine format from keywords
- A sequence completes and needs to determine output format
- Multiple response types could apply (disambiguation)