microsoft/microsoft-docs
Understand Microsoft technologies by querying official documentation. Use whenever the user asks how something works, wants tutorials, needs configuration options, limits, quotas, or best practices for any Microsoft technology (Azure, .NET, M365, Windows, Power Platform, etc.)—even if they don't mention "docs." If the question is about understanding a concept rather than writing code, this is the right skill.
npx skills add https://github.com/microsoft/skills --skill microsoft-docs
| Tool | Use For |
|------|---------|
| microsoft_docs_search | Find documentation—concepts, guides, tutorials, configuration |
| microsoft_docs_fetch | Get full page content (when search excerpts aren't enough) |
Good queries are specific:
# ❌ Too broad
"Azure Functions"
# ✅ Specific
"Azure Functions Python v2 programming model"
"Cosmos DB partition key design best practices"
"Container Apps scaling rules KEDA"
Include context:
.NET 8, EF Core 8)quickstart, tutorial, overview, limits)Linux, Windows)Fetch after search when:
If the Learn MCP server is not available, use the mslearn CLI from the command line instead:
# Run directly (no install needed)
npx @microsoft/learn-cli search "azure functions timeout"
# Or install globally, then run
npm install -g @microsoft/learn-cli
mslearn search "azure functions timeout"
| MCP Tool | CLI Command |
|----------|-------------|
| microsoft_docs_search(query: "...") | mslearn search "..." |
| microsoft_docs_fetch(url: "...") | mslearn fetch "..." |
The fetch command also supports --section <heading> to extract a single section and --max-chars <number> to truncate output.
Take microsoft/microsoft-docs from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npm, npx.
Without those the skill loads but fails at the first command.