microsoft/skills-for-copilot-studio
3 skills111 installs918 starsGitHub
Install
npx skills add https://github.com/microsoft/skills-for-copilot-studioSkills in this repo
1Int Project Contextint-project-context is an internal agent skill that establishes a single source of truth for how Copilot Studio projects are laid out on disk and how authoring sub-agents should call Microsoft’s schema lookup tooling. Solo builders rarely touch Copilot Studio YAML directly, but indie teams and consultants shipping custom agents in source control need every sub-agent to agree on where topics, actions, knowledge sources, and child agents live under `.mcs.yml` files. The skill is not end-user invocable; it preloads structure and invocation patterns so author, advisor, and validator agents do not contradict each other when creating AdaptiveDialog topics or TaskDialog actions. It emphasizes running the bundled schema lookup script with search and detail commands before emitting new YAML, which reduces invalid kinds, missing triggers, and broken references. Treat it as scaffolding for the Copilot Studio skill pack rather than a standalone workflow you run from chat for a generic SaaS or CLI product.44installs2Int Referenceint-reference is an internal reference skill that loads structured tables Copilot Studio YAML authors need at authoring time: which `.mcs.yml` kind maps to which folder, how conversational topics route under generative versus classic orchestration, and where to look for variables, entities, connector actions, and Power Fx patterns. It exists so author and advisor sub-agents in the Microsoft skills-for-copilot-studio pack answer with the same vocabulary when you add AdaptiveDialog topics, TaskDialog actions, or KnowledgeSourceConfiguration files. Generative agents lean on `modelDescription` for orchestration-aware routing, while classic setups still depend on `triggerQueries`; the skill makes that distinction explicit so you do not ship topics that never fire. Because it is not user-invocable, treat it as embedded procedural knowledge rather than a step-by-step workflow. Solo builders outside Copilot Studio will not need it; inside a Copilot Studio repo it shortens the loop between schema lookup and correct YAML drafts.43installs3Best Practicesbest-practices is a Copilot Studio authoring router skill for teams building Microsoft 365 agents, packaged for agent-assisted workflows in the Prism catalog. Instead of one giant checklist, it tells the copilot-studio-author agent to open only the relevant guide—JIT glossary for acronym expansion before knowledge search, JIT user context for country- and department-aware answers, OnActivity provisioning patterns, Switch-based BeginDialog redirects, or child-agent completion rules so connected agents do not talk over the orchestrator. Solo consultants shipping customer agents use it to avoid repeating brittle init topics and to fix poor retrieval when internal jargon never hits the index. The description explicitly defers general knowledge ingestion to add-knowledge and net-new topics to new-topic, which keeps scope honest. It is multi-phase: most work happens in build, but glossary and redirect tuning recur in operate when production conversations expose gaps. Intermediate complexity assumes familiarity with Copilot Studio topics, global variables, and connected agents.24installs