Menu
Shared project context for all Copilot Studio sub-agents. Provides project structure, schema lookup usage, and skill invocation guidance.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guide users through adding a new connector action to a Copilot Studio agent. Connector actions require UI-based connection setup, so this skill walks users through the Copilot Studio portal steps, then delegates to edit-action for YAML modifications.
Generate and insert an Adaptive Card into a Copilot Studio topic using AdaptiveCardPrompt. Use when the user asks to add an adaptive card, rich card, form card, info card, confirmation card, or interactive card to a topic.
Add generative answer nodes (SearchAndSummarizeContent or AnswerQuestionWithAI) to a Copilot Studio topic. Use this instead of /add-node when the user asks to add grounded answers, knowledge search, generative answers, or AI-powered responses — these nodes require specific patterns (ConditionGroup follow-up, knowledge source references, autoSend, responseCaptureType) that /add-node does not cover.
Add a knowledge source (public website or SharePoint) to a Copilot Studio agent. Use when the user asks to add a knowledge source, documentation URL, website, or SharePoint site for the agent to search.
Add or modify a node in an existing Copilot Studio topic. Use when the user asks to add a question, message, condition, variable, or other node to a topic. Do NOT use this for generative answers or knowledge search — use /add-generative-answers instead.
Add child agents, connected agents, or other multi-agent patterns to a Copilot Studio agent. Use when the user asks to create a sub-agent, child agent, connected agent, or call another agent.
| name | int-project-context |
| description | Shared project context for all Copilot Studio sub-agents. Provides project structure, schema lookup usage, and skill invocation guidance. |
| user-invocable | false |
You are working inside a Copilot Studio agent project. All YAML files have the .mcs.yml extension.
<agent-dir>/ # Auto-discover via Glob: **/agent.mcs.yml
├── agent.mcs.yml # Agent metadata (display name, schema version)
├── settings.mcs.yml # Agent settings (schemaName, GenerativeActionsEnabled, instructions)
├── topics/ # Conversation topics (AdaptiveDialog YAML files)
├── actions/ # Connector-based actions (TaskDialog YAML files)
├── knowledge/ # Knowledge sources (KnowledgeSourceConfiguration YAML files)
├── variables/ # Global variables (GlobalVariableComponent YAML files)
└── agents/ # Child agents (AgentDialog YAML files, each in its own subfolder)
When you write new YAML files, be sure to use the schema lookup script to understand the schema, including mandatory fields, definitions, and references. The script is located at .github/scripts/schema-lookup.bundle.js, and you can use it in the terminal as follows:
node .github/scripts/schema-lookup.bundle.js search trigger # Search by keyword
node .github/scripts/schema-lookup.bundle.js lookup SendActivity # Look up a definition
node .github/scripts/schema-lookup.bundle.js resolve AdaptiveDialog # Resolve with $refs
node .github/scripts/schema-lookup.bundle.js kinds # List all valid kind values
node .github/scripts/schema-lookup.bundle.js summary Question # Compact overview
node .github/scripts/schema-lookup.bundle.js validate <file.yml> # Validate a YAML file
If you already know the specific definition you want to look up, use lookup. If you want to explore the schema around a certain topic, use search or summary.
Always check the schema before writing YAML to ensure you include all required fields and use valid values.
NEVER load the full schema file (reference/bot.schema.yaml-authoring.json) — it's too long. Always use the script above.
The connector lookup script is at .github/scripts/connector-lookup.bundle.js. Use it for any questions about connectors, actions, their inputs, and outputs:
node .github/scripts/connector-lookup.bundle.js list # List all connectors with operation counts
node .github/scripts/connector-lookup.bundle.js operations <connector> # List operations for a connector
node .github/scripts/connector-lookup.bundle.js operation <connector> <operationId> # Full details of one operation (inputs/outputs)
node .github/scripts/connector-lookup.bundle.js search <keyword> # Search operations across all connectors
<connector> matches by API name (shared_office365) or partial display name (outlook).
When to use this: When you need to understand available connectors, what inputs/outputs an action has, or what operations are available. The action YAML files in the agent only show configured inputs — connector-lookup shows the full connector definition with all available inputs and outputs.
You have access to specialized skills that handle YAML creation, editing, validation, and testing. ALWAYS invoke the matching skill instead of doing it manually.
Skills contain correct templates, schema validation, and patterns. Doing it manually risks hallucinated kind: values, missing required fields, and broken YAML.
Example skills include /copilot-studio:new-topic for creating new topics, /copilot-studio:add-action for adding connector actions and tools, and /copilot-studio:validate for validating YAML files.
If no skill matches, only then work manually — but always validate with /copilot-studio:validate afterward.
Glob: **/agent.mcs.yml.sendMessage_g5Ls09)._REPLACE: Always replace _REPLACE placeholder IDs with unique random IDs.=. String interpolation uses {}. Only use supported functions (check int-reference skill).GenerativeActionsEnabled: true, use topic inputs/outputs instead of hardcoded questions/messages.