[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699MG0KKTY6G1QBGRW17JZA":3,"skill-same:01M699MG0KKTY6G1QBGRW17JZA":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M699MG0KKTY6G1QBGRW17JZA","agent-academy-mission-builder",null,"Scaffold and author content for the microsoft\u002Fagent-academy GitHub repo. Use this skill whenever the user wants to create a new mission, lab, or module for Agent Academy — whether that's a course mission (Recruit, Operative, Commander) or a standalone Special Ops mission. Trigger whenever the user says \"write a mission\", \"scaffold a lab\", \"create a Special Ops\", \"new Agent Academy module\", or describes an agent-building concept they want to turn into a hands-on lesson. Also trigger when the user says \"add a module to agent academy\", \"I want to contribute a mission\", or asks about badge creation for Special Ops. This skill handles: repo structure lookup, duplicate detection, mission naming, markdown scaffolding, step-by-step content drafting, cross-linking, tag\u002Fcategory suggestions, difficulty rating, and badge image generation for Special Ops missions.","microsoft\u002Fagent-academy","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699MCPQNKZBY9K0MDHG9XC8",3717,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fagent-academy-mission-builder\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000039","教师与教育",[32,33,34,9,35],"agent academy mission builder","image","github","scaffold","2026-11-10 10:12:30",false,"---\nname: agent-academy-mission-builder\ndescription: >\n  Scaffold and author content for the microsoft\u002Fagent-academy GitHub repo. Use this skill whenever\n  the user wants to create a new mission, lab, or module for Agent Academy — whether that's a\n  course mission (Recruit, Operative, Commander) or a standalone Special Ops mission. Trigger\n  whenever the user says \"write a mission\", \"scaffold a lab\", \"create a Special Ops\", \"new Agent\n  Academy module\", or describes an agent-building concept they want to turn into a hands-on lesson.\n  Also trigger when the user says \"add a module to agent academy\", \"I want to contribute a mission\",\n  or asks about badge creation for Special Ops. This skill handles: repo structure lookup,\n  duplicate detection, mission naming, markdown scaffolding, step-by-step content drafting,\n  cross-linking, tag\u002Fcategory suggestions, difficulty rating, and badge image generation for\n  Special Ops missions.\n---\n\n# Agent Academy Mission Builder\n\nThis skill scaffolds new content for the **microsoft\u002Fagent-academy** repository at\nhttps:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy. It covers two distinct mission types and handles\neverything from naming to final markdown output, including badge generation for Special Ops.\n\nThink of this skill like a mission briefing officer: it gets the concept from you, does the\nreconnaissance (checks the repo, checks for duplicates, maps cross-links), then hands you back\na fully briefed document you only need to fill in the \"boots on the ground\" steps for.\n\n---\n\n## Phase 0: Gather Intel (Interview the User)\n\nBefore writing anything, collect the following. Ask in one message, not one question at a time:\n\n**Required info:**\n1. **Mission type**: Course mission (Recruit \u002F Operative \u002F Commander) OR Special Ops?\n2. **Topic \u002F feature**: What Copilot Studio capability, integration, or concept does this cover?\n3. **Rough description**: What will the learner *build or do* by the end?\n4. **Difficulty** (for Special Ops): Beginner \u002F Intermediate \u002F Advanced (maps to 1 \u002F 2 \u002F 3 stars)\n5. **Prerequisites**: What must the learner have done or have access to?\n\nFor **course missions**, also ask:\n- Which mission number does this follow? (sets the folder name like `07-`)\n- What is the overall course scenario it fits into? (e.g., Operative = Hiring system)\n\nFor **Special Ops**, also ask:\n- Industry or use-case context (healthcare, retail, HR, IT, finance, etc.)? Or \"general\"?\n- Any specific integrations (SharePoint, Teams, Dataverse, Azure, MCP, etc.)?\n\nIf the user hasn't given you enough to go on, ask. Otherwise proceed.\n\n---\n\n## Phase 1: Reconnaissance (Repo Check)\n\nUse `web_search` and `web_fetch` to:\n\n1. **Check for duplicates**: Search `site:github.com\u002Fmicrosoft\u002Fagent-academy [topic keyword]`\n   and `microsoft.github.io\u002Fagent-academy [topic keyword]`. If something very similar exists,\n   flag it and ask the user whether to proceed anyway or pivot the angle.\n\n2. **Map existing missions**: Fetch https:\u002F\u002Fmicrosoft.github.io\u002Fagent-academy\u002Frecruit\u002F and\n   https:\u002F\u002Fmicrosoft.github.io\u002Fagent-academy\u002Foperative\u002F to get the current mission list.\n   Use this to:\n   - Assign the correct next mission number for course missions\n   - Identify missions to cross-link (e.g., if this mission uses MCP, link to Mission 10 MCP)\n   - Spot curriculum gaps the new mission fills\n\n3. **Check Special Ops listing**: Fetch https:\u002F\u002Fmicrosoft.github.io\u002Fagent-academy\u002Fspecial-ops\u002F\n   to see what already exists and identify tags\u002Fcategories in use.\n\nReport findings briefly before proceeding. If there's a close duplicate, surface it clearly.\n\n---\n\n## Phase 2: Mission Naming\n\nAgent Academy missions use military\u002Fspy operation themed names. Rules:\n\n- **Course missions**: Use `? Mission XX: [Action Verb] + [What They Build]`\n  Examples: `? Mission 03: Create a Multi-Agent Orchestration System`\n  The operation name appears in the briefing paragraph: `Operation [Codename]`\n  Codenames are dramatic and thematic: \"Operation Talent Scout\", \"Operation Symphony\",\n  \"Operation MCP Rendezvous\". They relate to what the mission accomplishes.\n\n- **Special Ops**: The lab *title* is a punchy phrase, often with a symbol if relevant.\n  Examples: `Microsoft Copilot Studio & MCP`, `Power Platform CLI MCP`\n  The operation name in the briefing: same dramatic style.\n  The **badge bottom banner name** is a clever play on the mission topic. See badge section.\n\n**Naming formula for operation codenames**: [Military\u002FIntelligence Term] + [Thematic Noun].\nExamples:\n- Adaptive Cards → \"Operation Flash Card\"\n- Event Triggers → \"Operation Trip Wire\"\n- AI Safety → \"Operation Safe Harbor\"\n- Document Generation → \"Operation Paper Trail\"\n- Dataverse Grounding → \"Operation Deep Root\"\n\nGenerate 2-3 name options and let the user pick, or auto-select the best one.\n\n---\n\n## Phase 3: Scaffold the Markdown\n\n### Course Mission Template\n\nFile: `docs\u002F[rank]\u002F[NN]-[slug]\u002Findex.md`\n\n```markdown\n---\ntitle: \"Mission NN: [Title]\"\n---\n\n# [Emoji] Mission [NN]: [Full Title]\n\n**Welcome, [Rank].** [1-2 sentence scene-setter in mission briefing voice.]\n\nYour assignment, should you choose to accept it, is **[Operation Codename]** —\n[one sentence high-level goal].\n\n[2-3 sentences expanding on what they'll build and how it connects to the course scenario.]\n\n## Mission Objective\n\nBy the end of this mission, you will have:\n\n- [Concrete deliverable 1]\n- [Concrete deliverable 2]\n- [Concrete deliverable 3]\n\n## Prerequisites\n\nBefore embarking on this mission, ensure you have:\n\n- Completed [Mission N-1: Title](..\u002F[folder]\u002F)\n- [Any specific access or setup]\n\n> [!TIP]\n> [Optional tip for getting access if stuck]\n\n## Background Intel\n\n> [!NOTE]\n> [Key concept explanation — 2-4 paragraphs. Explain the why before the how. Include an analogy.]\n\n## Mission Tasks\n\n### Task 1: [Name]\n\n[Brief intro sentence]\n\n1. [Step 1]\n2. [Step 2]\n3. [Step 3]\n\n> [!NOTE]\n> [Callout with context or warning about a common mistake]\n\n### Task 2: [Name]\n\n[... repeat pattern ...]\n\n## Mission Complete\n\n**Mission [NN] is completed!** You now have mastered the following skills:\n\n✅ **[Skill 1]**: [One sentence — what they can now do]\n✅ **[Skill 2]**: [One sentence]\n✅ **[Skill 3]**: [One sentence]\n\n## Related Missions\n\n- [Mission N-1: Title](..\u002F[prev-folder]\u002F) — [Why it connects]\n- [Mission N+1: Title](..\u002F[next-folder]\u002F) — [What builds on this]\n\n## Further Reading\n\n- [Microsoft docs link]\n- [Related Academy content]\n```\n\n### Special Ops Template\n\nFile: `docs\u002Fspecial-ops\u002F[slug]\u002Findex.md`\n\n```markdown\n---\ntitle: \"[Mission Title]\"\ntags:\n  - [technology-tag]\n  - [industry-tag]\ndifficulty: [1|2|3]\n---\n\n# [Emoji] [Mission Title]\n\n> **Difficulty**: [stars] | **Time**: ~[N] min | **Type**: Special Ops\n\n![Badge](.\u002Fassets\u002Fbadge.png)\n\n**Welcome, agent.** Your mission — should you choose to accept it — is [one-liner].\n\n## What You'll Build\n\n- [Specific deliverable 1]\n- [Specific deliverable 2]\n- [Specific deliverable 3]\n\n## Prerequisites\n\n- [Access\u002Flicense requirement]\n- [Tool requirement]\n\n> [!WARNING]\n> [Access barrier callout if needed]\n\n## Concept Brief\n\n[2-4 paragraphs on the core concept. Why does it exist? When would you use it?\nInclude an analogy.]\n\n### Key Terms\n\n| Term | Definition |\n|------|------------|\n| [Term] | [Plain-language definition] |\n\n## The Scenario\n\n> [!NOTE]\n> **Scenario:** [Company] is a [industry] company that needs to [problem]. You are building\n> an agent that [solution].\n\n## Mission Tasks\n\n### Task 1: [Name]\n\n1. [Step]\n2. [Step]\n\n### Task 2: [Name]\n\n[...]\n\n## Mission Accomplished\n\nCongrats, agent — mission accomplished! Claim your badge:\n`https:\u002F\u002Faka.ms\u002Fagent-academy-special-ops\u002F[slug]\u002Fform`\n\n## Tags\n\n**Technology**: [tag1], [tag2]\n**Industry**: [industry]\n**Difficulty**: [stars]\n\n## Related Content\n\n- [Relevant course mission link]\n- [Official docs link]\n```\n\n---\n\n## Phase 4: Auto-Draft Background Intel and Scenario\n\nDon't leave these blank. Fill them in using knowledge of Copilot Studio and the feature:\n\n1. Write 2-4 paragraphs of background. Voice: energetic, not dry docs.\n2. Always include an analogy. Existing ones in the repo:\n   - MCP = \"USB-C of AI integration\"\n   - Orchestrator = \"symphony conductor\"\n   - Agent = \"digital coworker\"\n   Find a new one for the new concept.\n3. For Special Ops: draft the fictional scenario with company name, industry, and problem.\n\n---\n\n## Phase 5: Step-by-Step Drafting\n\nFill in Mission Tasks based on Copilot Studio knowledge:\n\n- One action per step, clear action verbs (Select, Navigate, Enter, Configure, Test)\n- Bold UI element names: **Test your agent**, **Publish**, **Save**\n- Code format for: values to type, field names, test messages to send\n- Use `[!NOTE]`, `[!TIP]`, `[!WARNING]` callouts freely\n- Where exact steps are unknown, add `\u003C!-- TODO: Add screenshot -->` and\n  `[FILL IN: describe what needs to happen here]` placeholders\n\n---\n\n## Phase 6: Tags and Cross-Links (Special Ops Only)\n\nSee `references\u002Ftags.md` for full tag taxonomy. Select 1-3 technology tags and 1-3 industry tags.\n\nDifficulty = number of stars on the badge:\n- 1 star: Beginner (single feature, under 30 min, no admin required)\n- 2 stars: Intermediate (2-3 concepts, 30-60 min, some config)\n- 3 stars: Advanced (multi-step, VSCode, Azure\u002Fadmin required, 60+ min)\n\nAlways cross-link to the most relevant course mission. Check `docs\u002Frecruit\u002Findex.md`, `docs\u002Foperative\u002Findex.md`, `docs\u002Fcommander\u002Findex.md`, and `docs\u002Fspecial-ops\u002Findex.md` for the current mission inventory.\n\n---\n\n## Phase 7: Deliver Output\n\n1. **Scaffolded markdown file** create the mission file directly in the repo in the corresponding folder. If it's a recruit course mission, create a folder under `docs\u002Frecruit\u002F` with the appropriate mission name and place an `index.md` file inside as well as an `assets` folder for images, for example, `docs\u002Frecruit\u002Fmcp-lab\u002Findex.md`. Repeat this pattern for operative and commander missions under their respective folders. For Special Ops, create the folder under `docs\u002Fspecial-ops\u002F` with the slug name and place the `index.md` file and `assets` folder inside, for example, `docs\u002Fspecial-ops\u002Fmcp-lab\u002Findex.md`.\n2. **Summary** of what was pre-filled vs. what needs manual work (be explicit about TODOs)\n3. **Cross-link map** of which missions link here, and where this links\n4. **For Special Ops**: Tags, difficulty, badge banner name, and image generation prompt\n5. **Duplicate check result** with links to anything similar that exists\n\nEnd every delivery with:\n> \"The bones are done. Fill in the step-by-step and swap in real screenshots. Want me to\n> draft any specific task section in more detail?\"\n\n---\n\n## Reference Files\n\nRead these when needed:\n- `WRITING_STYLE.md` (repo root) — Voice, tone, formatting rules\n- `docs\u002Frecruit\u002Findex.md` — Recruit mission inventory for numbering and cross-linking\n- `docs\u002Foperative\u002Findex.md` — Operative mission inventory\n- `docs\u002Fcommander\u002Findex.md` — Commander mission inventory\n- `docs\u002Fspecial-ops\u002Findex.md` — Existing Special Ops for tag patterns and duplicate check","# Agent Academy Mission Builder\n\nThis skill scaffolds new content for the **microsoft\u002Fagent-academy** repository at\nhttps:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy. It covers two distinct mission types and handles\neverything from naming to final markdown output, including badge generation for Special Ops.\n\nThink of this skill like a mission briefing officer: it gets the concept from you, does the\nreconnaissance (checks the repo, checks for duplicates, maps cross-links), then hands you back\na fully briefed document you only need to fill in the \"boots on the ground\" steps for.\n\n---\n\n## Phase 0: Gather Intel (Interview the User)\n\nBefore writing anything, collect the following. Ask in one message, not one question at a time:\n\n**Required info:**\n1. **Mission type**: Course mission (Recruit \u002F Operative \u002F Commander) OR Special Ops?\n2. **Topic \u002F feature**: What Copilot Studio capability, integration, or concept does this cover?\n3. **Rough description**: What will the learner *build or do* by the end?\n4. **Difficulty** (for Special Ops): Beginner \u002F Intermediate \u002F Advanced (maps to 1 \u002F 2 \u002F 3 stars)\n5. **Prerequisites**: What must the learner have done or have access to?\n\nFor **course missions**, also ask:\n- Which mission number does this follow? (sets the folder name like `07-`)\n- What is the overall course scenario it fits into? (e.g., Operative = Hiring system)\n\nFor **Special Ops**, also ask:\n- Industry or use-case context (healthcare, retail, HR, IT, finance, etc.)? Or \"general\"?\n- Any specific integrations (SharePoint, Teams, Dataverse, Azure, MCP, etc.)?\n\nIf the user hasn't given you enough to go on, ask. Otherwise proceed.\n\n---\n\n## Phase 1: Reconnaissance (Repo Check)\n\nUse `web_search` and `web_fetch` to:\n\n1. **Check for duplicates**: Search `site:github.com\u002Fmicrosoft\u002Fagent-academy [topic keyword]`\n   and `microsoft.github.io\u002Fagent-academy [topic keyword]`. If something very similar exists,\n   flag it and ask the user whether to proceed anyway or pivot the angle.\n\n2. **Map existing missions**: Fetch https:\u002F\u002Fmicrosoft.github.io\u002Fagent-academy\u002Frecruit\u002F and\n   https:\u002F\u002Fmicrosoft.github.io\u002Fagent-academy\u002Foperative\u002F to get the current mission list.\n   Use this to:\n   - Assign the correct next mission number for course missions\n   - Identify missions to cross-link (e.g., if this mission uses MCP, link to Mission 10 MCP)\n   - Spot curriculum gaps the new mission fills\n\n3. **Check Special Ops listing**: Fetch https:\u002F\u002Fmicrosoft.github.io\u002Fagent-academy\u002Fspecial-ops\u002F\n   to see what already exists and identify tags\u002Fcategories in use.\n\nReport findings briefly before proceeding. If there's a close duplicate, surface it clearly.\n\n---\n\n## Phase 2: Mission Naming\n\nAgent Academy missions use military\u002Fspy operation themed names. Rules:\n\n- **Course missions**: Use `? Mission XX: [Action Verb] + [What They Build]`\n  Examples: `? Mission 03: Create a Multi-Agent Orchestration System`\n  The operation name appears in the briefing paragraph: `Operation [Codename]`\n  Codenames are dramatic and thematic: \"Operation Talent Scout\", \"Operation Symphony\",\n  \"Operation MCP Rendezvous\". They relate to what the mission accomplishes.\n\n- **Special Ops**: The lab *title* is a punchy phrase, often with a symbol if relevant.\n  Examples: `Microsoft Copilot Studio & MCP`, `Power Platform CLI MCP`\n  The operation name in the briefing: same dramatic style.\n  The **badge bottom banner name** is a clever play on the mission topic. See badge section.\n\n**Naming formula for operation codenames**: [Military\u002FIntelligence Term] + [Thematic Noun].\nExamples:\n- Adaptive Cards → \"Operation Flash Card\"\n- Event Triggers → \"Operation Trip Wire\"\n- AI Safety → \"Operation Safe Harbor\"\n- Document Generation → \"Operation Paper Trail\"\n- Dataverse Grounding → \"Operation Deep Root\"\n\nGenerate 2-3 name options and let the user pick, or auto-select the best one.\n\n---\n\n## Phase 3: Scaffold the Markdown\n\n### Course Mission Template\n\nFile: `docs\u002F[rank]\u002F[NN]-[slug]\u002Findex.md`\n\n```markdown\n---\ntitle: \"Mission NN: [Title]\"\n---\n\n# [Emoji] Mission [NN]: [Full Title]\n\n**Welcome, [Rank].** [1-2 sentence scene-setter in mission briefing voice.]\n\nYour assignment, should you choose to accept it, is **[Operation Codename]** —\n[one sentence high-level goal].\n\n[2-3 sentences expanding on what they'll build and how it connects to the course scenario.]\n\n## Mission Objective\n\nBy the end of this mission, you will have:\n\n- [Concrete deliverable 1]\n- [Concrete deliverable 2]\n- [Concrete deliverable 3]\n\n## Prerequisites\n\nBefore embarking on this mission, ensure you have:\n\n- Completed [Mission N-1: Title](..\u002F[folder]\u002F)\n- [Any specific access or setup]\n\n> [!TIP]\n> [Optional tip for getting access if stuck]\n\n## Background Intel\n\n> [!NOTE]\n> [Key concept explanation — 2-4 paragraphs. Explain the why before the how. Include an analogy.]\n\n## Mission Tasks\n\n### Task 1: [Name]\n\n[Brief intro sentence]\n\n1. [Step 1]\n2. [Step 2]\n3. [Step 3]\n\n> [!NOTE]\n> [Callout with context or warning about a common mistake]\n\n### Task 2: [Name]\n\n[... repeat pattern ...]\n\n## Mission Complete\n\n**Mission [NN] is completed!** You now have mastered the following skills:\n\n✅ **[Skill 1]**: [One sentence — what they can now do]\n✅ **[Skill 2]**: [One sentence]\n✅ **[Skill 3]**: [One sentence]\n\n## Related Missions\n\n- [Mission N-1: Title](..\u002F[prev-folder]\u002F) — [Why it connects]\n- [Mission N+1: Title](..\u002F[next-folder]\u002F) — [What builds on this]\n\n## Further Reading\n\n- [Microsoft docs link]\n- [Related Academy content]\n```\n\n### Special Ops Template\n\nFile: `docs\u002Fspecial-ops\u002F[slug]\u002Findex.md`\n\n```markdown\n---\ntitle: \"[Mission Title]\"\ntags:\n  - [technology-tag]\n  - [industry-tag]\ndifficulty: [1|2|3]\n---\n\n# [Emoji] [Mission Title]\n\n> **Difficulty**: [stars] | **Time**: ~[N] min | **Type**: Special Ops\n\n![Badge](.\u002Fassets\u002Fbadge.png)\n\n**Welcome, agent.** Your mission — should you choose to accept it — is [one-liner].\n\n## What You'll Build\n\n- [Specific deliverable 1]\n- [Specific deliverable 2]\n- [Specific deliverable 3]\n\n## Prerequisites\n\n- [Access\u002Flicense requirement]\n- [Tool requirement]\n\n> [!WARNING]\n> [Access barrier callout if needed]\n\n## Concept Brief\n\n[2-4 paragraphs on the core concept. Why does it exist? When would you use it?\nInclude an analogy.]\n\n### Key Terms\n\n| Term | Definition |\n|------|------------|\n| [Term] | [Plain-language definition] |\n\n## The Scenario\n\n> [!NOTE]\n> **Scenario:** [Company] is a [industry] company that needs to [problem]. You are building\n> an agent that [solution].\n\n## Mission Tasks\n\n### Task 1: [Name]\n\n1. [Step]\n2. [Step]\n\n### Task 2: [Name]\n\n[...]\n\n## Mission Accomplished\n\nCongrats, agent — mission accomplished! Claim your badge:\n`https:\u002F\u002Faka.ms\u002Fagent-academy-special-ops\u002F[slug]\u002Fform`\n\n## Tags\n\n**Technology**: [tag1], [tag2]\n**Industry**: [industry]\n**Difficulty**: [stars]\n\n## Related Content\n\n- [Relevant course mission link]\n- [Official docs link]\n```\n\n---\n\n## Phase 4: Auto-Draft Background Intel and Scenario\n\nDon't leave these blank. Fill them in using knowledge of Copilot Studio and the feature:\n\n1. Write 2-4 paragraphs of background. Voice: energetic, not dry docs.\n2. Always include an analogy. Existing ones in the repo:\n   - MCP = \"USB-C of AI integration\"\n   - Orchestrator = \"symphony conductor\"\n   - Agent = \"digital coworker\"\n   Find a new one for the new concept.\n3. For Special Ops: draft the fictional scenario with company name, industry, and problem.\n\n---\n\n## Phase 5: Step-by-Step Drafting\n\nFill in Mission Tasks based on Copilot Studio knowledge:\n\n- One action per step, clear action verbs (Select, Navigate, Enter, Configure, Test)\n- Bold UI element names: **Test your agent**, **Publish**, **Save**\n- Code format for: values to type, field names, test messages to send\n- Use `[!NOTE]`, `[!TIP]`, `[!WARNING]` callouts freely\n- Where exact steps are unknown, add `\u003C!-- TODO: Add screenshot -->` and\n  `[FILL IN: describe what needs to happen here]` placeholders\n\n---\n\n## Phase 6: Tags and Cross-Links (Special Ops Only)\n\nSee `references\u002Ftags.md` for full tag taxonomy. Select 1-3 technology tags and 1-3 industry tags.\n\nDifficulty = number of stars on the badge:\n- 1 star: Beginner (single feature, under 30 min, no admin required)\n- 2 stars: Intermediate (2-3 concepts, 30-60 min, some config)\n- 3 stars: Advanced (multi-step, VSCode, Azure\u002Fadmin required, 60+ min)\n\nAlways cross-link to the most relevant course mission. Check `docs\u002Frecruit\u002Findex.md`, `docs\u002Foperative\u002Findex.md`, `docs\u002Fcommander\u002Findex.md`, and `docs\u002Fspecial-ops\u002Findex.md` for the current mission inventory.\n\n---\n\n## Phase 7: Deliver Output\n\n1. **Scaffolded markdown file** create the mission file directly in the repo in the corresponding folder. If it's a recruit course mission, create a folder under `docs\u002Frecruit\u002F` with the appropriate mission name and place an `index.md` file inside as well as an `assets` folder for images, for example, `docs\u002Frecruit\u002Fmcp-lab\u002Findex.md`. Repeat this pattern for operative and commander missions under their respective folders. For Special Ops, create the folder under `docs\u002Fspecial-ops\u002F` with the slug name and place the `index.md` file and `assets` folder inside, for example, `docs\u002Fspecial-ops\u002Fmcp-lab\u002Findex.md`.\n2. **Summary** of what was pre-filled vs. what needs manual work (be explicit about TODOs)\n3. **Cross-link map** of which missions link here, and where this links\n4. **For Special Ops**: Tags, difficulty, badge banner name, and image generation prompt\n5. **Duplicate check result** with links to anything similar that exists\n\nEnd every delivery with:\n> \"The bones are done. Fill in the step-by-step and swap in real screenshots. Want me to\n> draft any specific task section in more detail?\"\n\n---\n\n## Reference Files\n\nRead these when needed:\n- `WRITING_STYLE.md` (repo root) — Voice, tone, formatting rules\n- `docs\u002Frecruit\u002Findex.md` — Recruit mission inventory for numbering and cross-linking\n- `docs\u002Foperative\u002Findex.md` — Operative mission inventory\n- `docs\u002Fcommander\u002Findex.md` — Commander mission inventory\n- `docs\u002Fspecial-ops\u002Findex.md` — Existing Special Ops for tag patterns and duplicate check",{"name":5,"description":7},"main","989277d271bbc8776ba09173471689ea151c193d",".github\u002Fskills\u002Fagent-academy-mission-builder",218,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy","https:\u002F\u002Faka.ms\u002Fagent-academy","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 07:13:07",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add microsoft\u002Fagent-academy --skill agent-academy-mission-builder",{"tool":57,"command":58},"bunx","bunx skills add microsoft\u002Fagent-academy --skill agent-academy-mission-builder",{"tool":60,"command":61},"pnpm","pnpm dlx skills add microsoft\u002Fagent-academy --skill agent-academy-mission-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fagent-academy-mission-builder\u002FSKILL.md",true,[65,71,75,79],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fbadge-spec.md","REFERENCE","参考文档",4948,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fagent-academy-mission-builder\u002Freferences\u002Fbadge-spec.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fnaming-guide.md",4455,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fagent-academy-mission-builder\u002Freferences\u002Fnaming-guide.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fspecial-ops-template.md",2962,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fagent-academy-mission-builder\u002Freferences\u002Fspecial-ops-template.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Ftags.md",4195,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fagent-academy-mission-builder\u002Freferences\u002Ftags.md",[84,97,105,113,120,127],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":94,"publishedAt":36},"01M699N3CMNAZY11BM55YDB2VY","outlook-pre-onboarding-checklist-meeting","Create a 1-hour Outlook follow-up meeting for pre-onboarding after a successful Docusign workflow trigger, using the employee name and agreement effective date from workflow context.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy\u002Fblob\u002Fmain\u002Fdocs\u002Fspecial-ops\u002Fdocusign-mcp\u002Fassets\u002Fsample-skill\u002FSKILL.md",[90,93],{"categoryNo":91,"categoryName":92,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[95,96],"outlook pre onboarding checklist meeting","workflow",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":36},"01M699N27KQF7X22QHFTYBCGH2","device-guidance-v1-0-4","Helps employees identify available device options based on their needs, using the `Get Employee Assets` tool.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy\u002Fblob\u002Fmain\u002Fdocs\u002Frecruit-nextgen\u002F07-automate-with-workflows\u002Fassets\u002Fdevice-guidance-v1-0-4\u002FSKILL.md",[],[104],"device guidance v1 0 4",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":36},"01M699N109HNVTY7D4TARZ6WCT","troubleshooting-procedure","Call this when a user states an IT issue and requests troubleshooting help. It provides step-by-step procedure for diagnosing and resolving IT issues, including escalation with a ticket summary.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy\u002Fblob\u002Fmain\u002Fdocs\u002Frecruit-nextgen\u002F06-add-skills\u002Fassets\u002Fit-troubleshooting-procedure\u002FSKILL.md",[],[112],"troubleshooting procedure",{"skillNo":114,"name":115,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":36},"01M699MZTEGG5Z9HJEPPWR8MX0","device-guidance-v1-0-3","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy\u002Fblob\u002Fmain\u002Fdocs\u002Frecruit-nextgen\u002F06-add-skills\u002Fassets\u002Fdevice-guidance-v1-0-3\u002FSKILL.md",[],[119],"device guidance v1 0 3",{"skillNo":121,"name":122,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":36},"01M699MY3MXWR14ZKG8J2S2W81","device-guidance-v1-0-2","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy\u002Fblob\u002Fmain\u002Fdocs\u002Frecruit-nextgen\u002F06-add-skills\u002Fassets\u002Fdevice-guidance-v1-0-2\u002FSKILL.md",[],[126],"device guidance v1 0 2",{"skillNo":128,"name":129,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":36},"01M699MWSGDSNKX7F5A9E9TC4K","device-guidance-v1-0-1","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagent-academy\u002Fblob\u002Fmain\u002Fdocs\u002Frecruit-nextgen\u002F06-add-skills\u002Fassets\u002Fdevice-guidance-v1-0-1\u002FSKILL.md",[],[133],"device guidance v1 0 1"]