Create agent skills for Microsoft technologies using Learn MCP tools. Use when users want to create a skill that teaches agents about any Microsoft technology, library, framework, or service (Azure, .NET, M365, VS Code, Bicep, etc.). Investigates topics deeply, then generates a hybrid skill storing

Microsoft Skill Creator Create hybrid skills for Microsoft technologies that store essential knowledge locally while enabling dynamic Learn MCP lookups for deeper details. About Skills Skills are modular packages that extend agent capabilities with specialized knowledge and workflows. A skill transforms a general purpose agent into a specialized one for a specific domain. Skill Structure Key Principles Frontmatter is critical : name and description determine when the skill triggers—be clear and comprehensive Concise is key : Only include what agents don't already know; context window is shared No duplication : Information lives in SKILL.md OR reference files, not both Learn MCP Tools Tool Purpose When to Use microsoft docs search Search official docs First pass discovery, finding topics microsoft docs fetch Get full page content Deep dive into important pages microsoft code sample search Find code examples Get implementation patterns CLI Alternative If the Learn MCP server is not available, use the mslearn CLI from a terminal or shell (for example, Bash, PowerShell, or cmd) instead: MCP Tool CLI Command microsoft docs search(query: "...") mslearn search "..." microsoft code sample search(query: "...", language: "...") mslearn code search "..." language ... microsoft docs fetch(url: "...") mslearn fetch "..." Generated skills should include this same CLI fallback table so agents can use either path. Creation Process Step 1: Investigate the Topic Build deep understanding using Learn MCP tools in three phases: Phase 1 Scope Discovery: Phase 2 Core Content: Phase 3 Depth: Investigation Checklist After investigating, verify: [ ] Can explain what the technology does in one paragraph [ ] Identified 3 5 key concepts [ ] Have working code for basic usage [ ] Know the most common API patterns [ ] Have search queries for deeper topics Step 2: Clarify with User Present findings and ask: 1. "I found these key areas: [list]. Which are most important?" 2. "What tasks will agents primarily perform with this skill?" 3. "Which programming language should code samples prioritize?" Step 3: Generate the Skill Use the appropriate template from [skill templates.md](references/skill templates.md): Technology Type Template Client library, NuGet/npm package SDK/Library Azure resource Azure Service App development framework Framework/Platform REST API, protocol API/Protocol Generated Skill Structure Step 4: Balance Local vs Dynamic Content Store locally when: Foundational (needed for any task) Frequently accessed Stable (won't change) Hard to find via search Keep dynamic when: Exhaustive reference (too large) Version specific Situational (specific tasks only) Well indexed (easy to search) Content Guidelines Content Type Local Dynamic Core concepts (3 5) ✅ Full Hello world code ✅ Full Common patterns (3 5) ✅ Full Top API methods Signature + example Full docs via fetch Best practices Top 5 bullets Search for more Troubleshooting Search queries Full API reference Doc links Step 5: Validate 1. Review: Is local content sufficient for common tasks? 2. Test: Do suggested search queries return useful results? 3. Verify: Do code samples run without errors? Common Investigation Patterns For SDKs/Libraries For Azure Services For Frameworks/Platforms Example: Creating a "Semantic Kernel" Skill Investigation Generated Skill Generated SKILL.md

microsoft-skill-creator