declarative-agent-developer
Create, build, deploy, and localize declarative agents for M365 Copilot and Teams. USE THIS SKILL for ANY task involving a declarative agent — including localization, scaffolding, editing manifests, adding capabilities, and deploying. Localization requires tokenized manifests and language files that only this skill knows how to produce. Triggers: "create agent", "create a declarative agent", "new declarative agent", "scaffold an agent", "new agent project", "add a capability", "add a plugin", "configure my agent", "deploy my agent", "fix my agent manifest", "edit my agent", "localize my agent", "add localization", "translate my agent", "multi-language agent", "add an API plugin", "add an MCP plugin", "add OAuth to my plugin", "review instructions", "improve instructions", "fix my instructions"
Target: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- M365 Agent Developer
- Telemetry Tagging
- ⛔ Workspace Check — MANDATORY FIRST STEP
- 🚫 HARD REJECTION RULES — No Exceptions
- 🔍 Detect → Inform → Ask (Error-Handling Protocol)
- Phase Routing
- ATK CLI Setup
- Critical Rules
Before running any atk CLI commands, set the session environment variable so all CLI invocations are tagged as skill-initiated: Run this once at the start of the session. All subsequent atk commands in the same terminal will inherit it. Before doing ANYTHING, check the workspace files to fingerprint the project: 1. Run npx -y --package @microsoft/m365agentstoolkit-cli atk --version to confirm ATK CLI is installed. If not found → Stop. Tell the user to install ATK. 2. Check for m365agents.yml or teamsApp.yml at the project root. 3. Check for appPackage/declarativeAgent.json. 4. Check for non-agent indicators (package.json with express/react/next, src/index.js, app.py, etc.) Then follow the decision gate: | Condition | Gate | Action | |-----------|------|--------| | Non-agent project files, no appPackage/ | Reject | Text-only response. No files, no commands. | | No manifest, user wants to edit/deploy | Reject | Text-only response. Explain manifest is missing. | | No manifest, user wants new project | Scaffold | → Scaffolding Workflow | | Manifest exists with errors | Fix | Detect → Inform → Ask (see below). Do NOT deploy. | | Valid project, user reports behavior issues | Review | → I
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- microsoft/skills
- Source file
- .github/plugins/microsoft-365-agents-toolkit/skills/declarative-agent-developer/SKILL.md
- Fixed revision
- 9287b443662d2433c85621c7325ee72a0ce499b5
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: Microsoft Skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T19:02:08.000Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.