int-reference
Provides structure and syntax guidance for Copilot Studio YAML component files.
Install
mkdir -p .claude/skills/int-reference && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17957" && unzip -o skill.zip -d .claude/skills/int-reference && rm skill.zipInstalls to .claude/skills/int-reference
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Reference tables for Copilot Studio YAML authoring: triggers, actions, variables, entities, Power Fx functions, templates. Preloaded by author and troubleshoot agents.Key capabilities
- →Identify the purpose of core Copilot Studio YAML files like `agent.mcs.yml` and `topics/*.mcs.yml`.
- →Distinguish between generative orchestration using `modelDescription` and classic orchestration using `triggerQueries`.
- →Understand the function of various trigger types such as `OnRecognizedIntent`, `OnConversationStart`, and `OnError`.
- →Recognize different action types including `SendActivity`, `Question`, `SetVariable`, and `BeginDialog`.
- →Configure connector actions (`TaskDialog`) by specifying connection references, operation IDs, and input/output modes.
- →Utilize Power Fx functions for logical, mathematical, and text operations within Copilot Studio.
How it works
This skill provides structured reference tables that map Copilot Studio YAML file types, trigger mechanisms, action types, and Power Fx functions to their specific purposes and configurations. It details how different orchestration modes handle topic routing and explains the properties of connector actions.
Inputs & outputs
When to use int-reference
- →Looking up YAML file structures
- →Understanding generative vs classic orchestration triggers
- →Configuring agent settings and variables
About this skill
Copilot Studio YAML Reference
Core File Types
| File | Purpose |
|---|---|
agent.mcs.yml | Main agent metadata (kind: GptComponentMetadata) |
settings.mcs.yml | Agent settings and configuration |
connectionreferences.mcs.yml | Connector references |
topics/*.mcs.yml | Conversation topics (kind: AdaptiveDialog) |
actions/*.mcs.yml | Connector-based actions (kind: TaskDialog) |
knowledge/*.mcs.yml | Knowledge sources (kind: KnowledgeSourceConfiguration) |
variables/*.mcs.yml | Global variables (kind: GlobalVariableComponent) |
agents/*.mcs.yml | Child 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.
| Kind | Purpose |
|---|---|
OnRecognizedIntent | Trigger phrases matched |
OnConversationStart | Conversation begins |
OnUnknownIntent | No topic matched (fallback) |
OnEscalate | User requests human agent |
OnError | Error handling |
OnSystemRedirect | Triggered by redirect only |
OnSelectIntent | Multiple topics matched (disambiguation) |
OnSignIn | Authentication required |
OnToolSelected | Child agent invocation |
OnKnowledgeRequested | Custom knowledge source search triggered (YAML-only, no UI) |
OnGeneratedResponse | Intercept AI-generated response before sending |
OnOutgoingMessage | Non-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.
| Feature | Notes |
|---|---|
triggerCondition on knowledge sources | The 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
| Kind | Purpose |
|---|---|
SendActivity | Send a message |
Question | Ask user for input |
SetVariable | Set/compute a variable (Power Fx expression, prefix =) |
SetTextVariable | Set a text variable using template interpolation ({}). Useful for converting non-text types (e.g., Number) to text: "You have {Topic.Count} items" |
ConditionGroup | Branching logic |
BeginDialog | Call another topic |
ReplaceDialog | Replace current topic |
EndDialog | End current topic |
CancelAllDialogs | Cancel all topics |
ClearAllVariables | Clear variables |
SearchAndSummarizeContent | Generative answers (grounded in knowledge) |
AnswerQuestionWithAI | AI answer (conversation history + general knowledge only) |
EditTable | Modify a collection |
CSATQuestion | Customer satisfaction |
LogCustomTelemetryEvent | Logging |
OAuthInput | Sign-in prompt |
SearchKnowledgeSources | Search knowledge sources (returns raw results, no AI summary) |
CreateSearchQuery | AI-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
| Field | Purpose |
|---|---|
kind: TaskDialog | Identifies this as a connector action |
inputs | Inputs: AutomaticTaskInput (AI-provided) or ManualTaskInput (fixed value) |
modelDisplayName | Display name for AI orchestrator routing |
modelDescription | Description for AI orchestrator routing |
outputs | Output property names returned by the connector |
action.kind | Always InvokeConnectorTaskAction for connector actions |
action.connectionReference | Logical name of the connection (registered in connectionreferences.mcs.yml) |
action.connectionProperties.mode | Maker (maker's credentials) or Invoker (end user's credentials) |
action.operationId | The connector's specific operation identifier |
outputMode | Usually All — exports all operation outputs |
Input Types
| Input Kind | Use When | Notes |
|---|---|---|
AutomaticTaskInput | The AI orchestrator should provide the value based on context | Includes description for the AI to understand what to provide |
ManualTaskInput | A 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 |
System Variables
| Variable | Description |
|---|---|
System.Bot.Name | Agent's name |
System.Activity.Text | User's current message |
System.Conversation.Id | Conversation identifier |
System.Conversation.InTestMode | True if in test chat |
System.FallbackCount | Number of consecutive fallbacks |
System.Error.Message | Error message |
System.Error.Code | Error code |
System.SignInReason | Why sign-in was triggered |
System.Recognizer.IntentOptions | Matched intents for disambiguation |
System.Recognizer.SelectedIntent | User's selected intent |
System.SearchQuery | AI-rewritten search query (available in OnKnowledgeRequested) |
System.KeywordSearchQuery | Keyword version of search query (available in OnKnowledgeRequested) |
System.SearchResults | Table to populate with custom search results — schema: Content, ContentLocation, Title (available in OnKnowledgeRequested) |
System.ContinueResponse | Set to false in OnGeneratedResponse to suppress auto-send |
System.Response.FormattedText | The AI-generated response text (available in OnGeneratedResponse) |
Variable Scopes
| Prefix | Scope | Lifetime |
|---|---|---|
Topic.<name> | Topic variable | Current topic only |
Global.<name> | Global variable | Entire conversation (defined in variables/ folder) |
System.<name> | System variable | Built-in, read-only |
Global variables are defined as YAML files in variables/<Name>.mcs.yml (kind: GlobalVariableComponent). aIVisibility accepts UseInAIContext (orchestrator can read and reason about the value) or Hidden (orchestrator unaware — use for flags and internal bookkeeping).
Prebuilt Entities
| Entity | Use Case |
|---|---|
BooleanPrebuiltEntity | Yes/No questions |
NumberPrebuiltEntity | Numeric inputs |
StringPrebuiltEntity | Free text |
DateTimePrebuiltEntity | Date/time |
EMailPrebuiltEntity | Email addresses |
Power Fx Expression Reference
Only use functions from the supported list below. Copilot Studio supports a subset of Power Fx — using unsupported functions will cause errors.
# Arithmetic
value: =Text(Topic.number1 + Topic.number2)
# Date formatting
value: =Text(Now(), DateTimeFormat.UTC)
# Conditions
condition: =System.FallbackCount < 3
condition: =Topic.EndConversation = true
condition: =!IsBlank(Topic.Answer)
condition: =System.Conversation.InTestMode = true
condition: =System.SignInReason = SignInReason.SignInRequired
condition: =System.Recognizer.SelectedIntent.TopicId = "NoTopic"
# String interpolation in activity (uses {} without =)
activity: "Error: {System.Error.Message}"
activity: "Error code: {System.Error.Code}, Time (UTC): {Topic.CurrentTime}"
# Record creation
value: "={ DisplayName: Topic.NoneOfTheseDisplayName, TopicId: \"NoTopic\", TriggerId: \"NoTrigger\", Score: 1.0 }"
# Variable initialization (first assignment uses init: prefix)
variable: init:Topic.UserEmail
variable: init:Topic.CurrentTime
# Subsequent assignments omit init:
variable: Topic.UserEmail
Supported Power Fx Functions
These are all the Power Fx functions available in Copilot Studio. Do NOT use any function not on this list.
Math: Abs, Acos, Acot, Asin, Atan, Atan2, Cos, Cot, Degrees, Exp, Int, Ln, Log, Mod, Pi, Power, Radians, Rand, RandBetween, Round, RoundDown, RoundUp, Sin, Sqrt, Sum, Tan, Trunc
Text: Char, Concat, Concatenate, EncodeHTML, EncodeUrl, EndsWith, Find, Left, Len, Lower, Match, MatchAll, Mid, PlainText, Proper, Replace, Right, Search, Split, StartsWith, Substitute, Text, Trim, TrimEnds, UniChar, Upper, Value
Date/Time: Date, DateAdd, DateDiff, DateTime, DateTimeValue, DateValue, Day, EDate, EOMonth, Hour, IsToday, Minute, Month, Now, Second, Time, TimeValue, TimeZoneOffset, Today, Weekday, WeekNum, Year
Logical: And, Coalesce, If, IfError, IsBlank, IsBlankOrError, IsEmpty, IsError, IsMatch, IsNumeric, IsType, Not, Or, Switch
Table: AddColumns, Column, ColumnNames, Count, CountA, CountIf, CountRows, Distinct, DropColumns, Filter, First, FirstN, ForAll, Index, Last, LastN, LookUp, Patch, Refresh, RenameColumns, Sequence, ShowColumns, Shuffle, Sort, SortByColumns, Summarize, Table
Aggregate:
Content truncated.
When not to use it
- →When the `OnOutgoingMessage` trigger is needed, as it is non-functional.
- →When expecting YAML-only features to be visible or editable in the Copilot Studio UI.
- →When hardcoding non-string values for `ManualTaskInput` in connector actions without user review.
Limitations
- →The `OnOutgoingMessage` trigger is non-functional.
- →YAML-only features are not visible in the Copilot Studio UI.
- →Connector action inputs and outputs are connector-specific and require a separate lookup script.
How it compares
This skill offers a centralized, structured reference for Copilot Studio YAML authoring, unlike manually searching through documentation or inferring configurations.
Compared to similar skills
int-reference side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| int-reference (this skill) | 0 | 4mo | No flags | Intermediate |
| command-development | 16 | 8mo | Review | Intermediate |
| prpm-development | 6 | 7mo | Review | Intermediate |
| rule-identifier | 5 | 8mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
command-development
anthropics
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
prpm-development
pr-pm
Use when developing PRPM (Prompt Package Manager) - comprehensive knowledge base covering architecture, format conversion, package types, collections, quality standards, testing, and deployment
rule-identifier
anthropics
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
autonomous-agent-patterns
davila7
Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool APIs, implementing permission systems, or creating autonomous coding assistants.
example-skill
anthropics
This skill should be used when the user asks to "demonstrate skills", "show skill format", "create a skill template", or discusses skill development patterns. Provides a reference template for creating Claude Code plugin skills.
command-creator
davila7
This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.