メニュー
Microsoft Copilot Studio agent building. Use when: creating Copilot agents, multi-agent orchestration, autonomous agents, MCP integration, knowledge sources, generative actions, Agent API for Power Pages, ALM for agents, testing agents.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | copilot-studio |
| description | Microsoft Copilot Studio agent building. Use when: creating Copilot agents, multi-agent orchestration, autonomous agents, MCP integration, knowledge sources, generative actions, Agent API for Power Pages, ALM for agents, testing agents. |
Trigger when building, configuring, testing, deploying, or reviewing Copilot Studio agents (formerly Power Virtual Agents) — including standalone agents, Copilot extensions, autonomous agents, and multi-agent orchestrations.
| Type | Description | Use Case |
|---|---|---|
| Copilot agent | Custom agent with topics + generative AI | Customer support, employee self-service |
| Copilot extension | Extends Microsoft 365 Copilot | Enterprise Copilot with custom knowledge |
| Autonomous agent | Event-driven, runs without user interaction | Monitoring, proactive notifications |
| Connected agent | Agent-to-agent via A2A protocol | Cross-domain orchestration |
| Embedded agent | Agent embedded within another agent | Specialized sub-agent for delegation |
SKILL.md is a summary only — it is NOT sufficient for implementation.
The detailed content (complete payloads, XML templates, working examples, edge-case handling) lives in sub-files in the same directory as this SKILL.md. Before writing any code, you MUST use read_file on the sub-files relevant to your task:
power-automate — Agent Flows, plugin actions via flowsazure-openai — BYOM, AI architecture decisionsdataverse — Structured knowledge sourcessecurity — Agent authentication configurationalm — Solution packaging for agent promotionpower-pages — Agent API for custom chat experiencesModel-Driven Apps Development. Use when: building Model-Driven Apps, forms, views, business rules, site map, command bar customization, custom pages, embedded Canvas Apps, subgrids, role-based form switching, generative pages.
Power Apps Code Apps Development (React + TypeScript + Vite). Use when: building Code Apps, three-layer architecture, PAC CLI workflow, Zustand state management, TanStack Query, shadcn/ui components, router basename, provider stack, form patterns, Dataverse integration from React.
WCAG 2.2 AA compliance, accessibility patterns, UX design for Power Platform. Use when: building accessible components, reviewing WCAG compliance, designing loading/empty/error states, responsive design, form accessibility, keyboard navigation, screen reader support, color contrast, focus management.
Dataverse Web API reference. Use when: CRUD operations, OData queries, FetchXML, bulk operations, batch requests, metadata operations, Custom APIs, file/image columns, change tracking, solution management via API, schema creation, programmatic builds.
PCF (Power Apps Component Framework) control development. Use when: building PCF controls, ReactControl, dataset controls, manifest patterns, Fluent UI v9 integration, Canvas App deployment, debugging PCF.
Dataverse C# Plugin development. Use when: writing plugins, IPlugin interface, execution pipeline, entity images, shared variables, unit testing with FakeXrmEasy, plugin registration, ITracingService, sandbox limitations.