Agent skill · DevOps & Cloud

microsoft-skill-creator

Create agent skills for Microsoft technologies using official documentation. Use whenever the user wants to build, generate, or scaffold a skill for any Microsoft technology (Azure, .NET, M365, VS Code, Bicep, etc.)—even phrased casually like "make a skill for Cosmos DB." Investigates the topic via official docs, then generates a hybrid skill with essential knowledge stored locally and dynamic lookups for depth.

MicrosoftDocsgithub.com/MicrosoftDocsGitHub ↗
copilotCC-BY-4.0
Install
npx skills add MicrosoftDocs/mcp --skill microsoft-skill-creator --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 2
SKILL.md size: 8 KB
Bundled scripts: none
Requires: Primarily uses the Microsoft Learn MCP Server (https://learn.microsoft.com/api/mcp); if that is unavailable, fall back…
Path: skills/microsoft-skill-creator/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,811
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 ``` skill-name/ ├── SKILL.md (required) # Frontmatter (name, description) + instructions ├── references/ # Documentation loaded into context as needed ├── sample_codes/ # Working code examples └── assets/ # Files used in output (templates, etc.) ``` ### 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

What's inside
Steps it walks through
  1. About Skills
  2. Skill Structure
  3. Key Principles
  4. Learn MCP Tools
  5. CLI Alternative
  6. Creation Process
  7. Step 1: Investigate the Topic
  8. Step 2: Clarify with User
  9. Step 3: Generate the Skill
  10. Step 4: Balance Local vs Dynamic Content
  11. Step 5: Validate
  12. Common Investigation Patterns
  13. For SDKs/Libraries
  14. For Azure Services
Ships with 1 file
  • references/skill-templates.md
Commands it runs
Run directly (no install needed)
npx @microsoft/learn-cli search "semantic kernel overview"
Or install globally, then run
npm install -g @microsoft/learn-cli
mslearn search "semantic kernel overview"
More from mcp
All skills →
About this skill
What does the microsoft-skill-creator skill do?

Create agent skills for Microsoft technologies using official documentation. Use whenever the user wants to build, generate, or scaffold a skill for any Microsoft technology (Azure, .NET, M365, VS Code, Bicep, etc.)—even phrased casually like "make a skill for Cosmos DB." Investigates the topic via official docs, then generates a hybrid skill with essential knowledge stored locally and dynamic lookups for depth.

How do I install it?

Run `npx skills add MicrosoftDocs/mcp --skill microsoft-skill-creator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From MicrosoftDocs/mcp, a repository with 1,811 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going