m365-copilot-builderlisted

## When to use this skill Trigger phrases: - "build a Copilot agent" / "M365 Copilot agent for [client]" - "declarative agent" / "agent builder" - "Copilot for [client]" when the client is a Microsoft shop Do NOT trigger on: - **Copilot Studio standalone platform** (topics, autonomous/event-triggered agents, non-M365 channels, custom engine agents) — use `copilot-studio-builder` - **Google Gemini Gems** — use a Gemini-specific builder; out of scope for this skill - Generic chatbots not bound for the Microsoft 365 Copilot surface Boundary rule of thumb: if the agent lives inside the M365 Copilot app / Teams and inherits Copilot's orchestrator and model, it is a declarative agent → this skill. If it needs its own topics, channels, autonomous triggers, or a different model, it is Copilot Studio territory → sibling skill. ## What you're building A **declarative agent** = Microsoft 365 Copilot + custom instructions + scoped knowledge + optional capabilities (code interpreter, image generator). It inherits Copilot's orchestrator and model — you cannot swap models or add custom orchestration. A business user with an M365 Copilot license builds it in **agent builder** (New agent inside the Copilot app), no code, no admin needed until org-wide distribution. This skill is CLIENT-AGNOSTIC by default - it becomes client-specific only when the brief names a client (then pull their context per Stage 1). This builder targets organizations on a Microsoft stack with Copilot licens