copilot-studio-builderlisted
Install: claude install-skill AI-Enablement-Academy/agentic-marketplace
## When to use this skill
Trigger phrases:
- "build a Copilot Studio agent" / "build a Studio agent"
- "low-code agent for [client]" / "Power Platform agent"
- "autonomous agent for [client]" (event-triggered, unattended)
- "Copilot Studio estimate / licensing / proposal"
Do NOT trigger on:
- **Declarative agents / M365 Copilot agent builder** — agents that run
inside M365 Copilot using Copilot's own orchestrator. That is the
sibling skill `m365-copilot-builder`. Rule of thumb: if the agent needs
its own orchestrator, autonomous triggers, non-Microsoft channels, MCP
tools, or consumption billing, it is Copilot Studio (this skill). If it
only extends M365 Copilot with instructions + Graph knowledge for
licensed users, it is declarative (the sibling). Full decision guide:
`references/design-decisions.md`.
- Google Gemini Gems — use a Gemini-specific builder; out of scope for
this skill. Also out of scope: generic chatbots, or direct API
builds (Azure AI Foundry work).
## Why this skill exists
This skill builds Studio agents for enterprise deployment. It is
CLIENT-AGNOSTIC by default - it becomes client-specific only when the
brief names a client (then pull their context from your own intake
notes, discovery documents, or client brief). Two things kill enterprise deals when missing:
**governance clarity**
(IT will ask about DLP, environments, ALM before anyone builds anything)
and a **licensing estimate** (Studio billing is consumption-based Copilot
Credi