跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

int-reference

Reference tables for Copilot Studio YAML authoring: triggers, actions, variables, entities, Power Fx functions, templates. Preloaded by author and advisor agents.

microsoft · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add microsoft/skills-for-copilot-studio --skill int-reference

技能说明


name: int-reference description: "Reference tables for Copilot Studio YAML authoring: triggers, actions, variables, entities, Power Fx functions, templates. Preloaded by author and advisor agents." user-invocable: false

Copilot Studio YAML Reference

Core File Types

FilePurpose
agent.mcs.ymlMain agent metadata (kind: GptComponentMetadata)
settings.mcs.ymlAgent settings and configuration
connectionreferences.mcs.ymlConnector references
topics/*.mcs.ymlConversation topics (kind: AdaptiveDialog)
actions/*.mcs.ymlConnector-based actions (kind: TaskDialog)
knowledge/*.mcs.ymlKnowledge sources (kind: KnowledgeSourceConfiguration)
variables/*.mcs.ymlGlobal variables (kind: GlobalVariableComponent)
agents/*.mcs.ymlChild agents (kind: AgentDialog)

Trigger Types

Topics with OnRecognizedIntent have two routing mechanisms — which one matters depends on the orchestration mode:

  • modelDescription — used by generative orchestration (GenerativeActionsEnabled: true). The AI orchestrator reads this to decide routing. Primary mechanism for generative agents.
  • Trigger phrases (triggerQueries) — used by classic orchestration. Pattern-matched against the user's utterance. Secondary hints when generative orchestration is enabled.

System triggers (OnConversationStart, OnUnknownIntent, OnError, etc.) fire automatically and don't use either mechanism.

KindPurpose
OnRecognizedIntentTrigger phrases matched
OnConversationStartConversation begins
OnUnknownIntentNo topic matched (fallback)
OnEscalateUser requests human agent
OnErrorError handling
OnSystemRedirectTriggered by redirect only
OnSelectIntentMultiple topics matched (disambiguation)
OnSignInAuthentication required
OnToolSelectedChild agent invocation
OnKnowledgeRequestedCustom knowledge source search triggered (YAML-only, no UI)
OnGeneratedResponseIntercept AI-generated response before sending
OnOutgoingMessageNon-functional (2026-03-15) — exists in schema but does not fire at runtime. Do not use.

YAML-Only Features

These features work at runtime but are not visible in the Copilot Studio UI. Warn users that UI edits may silently remove them.

FeatureNotes
triggerCondition on knowledge sourcesThe UI only exposes this as an on/off toggle (=false to exclude from UniversalSearchTool). Arbitrary Power Fx expressions (e.g., =Global.UserDepartment = "HR") work at runtime but can only be set via YAML. Use with caution. (2026-03-16)

Action Types

KindPurpose
SendActivitySend a message
QuestionAsk user for input
SetVariableSet/compute a variable (Power Fx expression, prefix =)
SetTextVariableSet a text variable using template interpolation ({}). Useful for converting non-text types (e.g., Number) to text: "You have {Topic.Count} items"
ConditionGroupBranching logic
BeginDialogCall another topic
ReplaceDialogReplace current topic
EndDialogEnd current topic
CancelAllDialogsCancel all topics
ClearAllVariablesClear variables
SearchAndSummarizeContentGenerative answers (grounded in knowledge)
AnswerQuestionWithAIAI answer (conversation history + general knowledge only)
EditTableModify a collection
CSATQuestionCustomer satisfaction
LogCustomTelemetryEventLogging
OAuthInputSign-in prompt
SearchKnowledgeSourcesSearch knowledge sources (returns raw results, no AI summary)
CreateSearchQueryAI-generated search query from user input

Connector Actions (TaskDialog)

Connector actions (kind: TaskDialog) invoke external connector operations. They are stored in actions/ and require a connection reference in connectionreferences.mcs.yml.

Use /add-action to create new actions from available connectors. The schema describes the structural properties of TaskDialog and InvokeConnectorTaskAction, but the specific inputs and outputs for each connector operation are connector-specific — use the connector lookup script (connector-lookup.bundle.js) to get the full operation details.

Action Structure

FieldPurpose
kind: TaskDialogIdentifies this as a connector action
inputsInputs: AutomaticTaskInput (AI-provided) or ManualTaskInput (fixed value)
modelDisplayNameDisplay name for AI orchestrator routing
modelDescriptionDescription for AI orchestrator routing
outputsOutput property names returned by the connector
action.kindAlways InvokeConnectorTaskAction for connector actions
action.connectionReferenceLogical name of the connection (registered in connectionreferences.mcs.yml)
action.connectionProperties.modeMaker (maker's credentials) or Invoker (end user's credentials)
action.operationIdThe connector's specific operation identifier
outputModeUsually All — exports all operation outputs

Input Types

Input KindUse WhenNotes
AutomaticTaskInputThe AI orchestrator should provide the value based on contextIncludes description for the AI to understand what to provide
ManualTaskInputA fixed/hardcoded value (e.g., timezone, folder path)Can only hardcode strings. Non-string values (IDs, enums) should be reviewed by the user after pushing

$-Prefixed Property Names (SharePoint, OData)

Some connectors (notably SharePoint) use OData parameters like $filter, $orderby, $top. These require special quoting in TaskDialog YAML — both single and double quotes:

# TaskDialog (actions/*.mcs.yml) — CORRECT
- kind: ManualTaskInput
 
阅读完整来源 ↗