Microsoft docs

Skill Jylhis/skills/skills/engineering/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.From its SKILL.md

Install

npx -y skills add Jylhis/skills --skill microsoft-docs

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.0 KB, 558 tokens by cl100k_base, as published. Nobody here has run it

Microsoft Docs

Tools

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)

When to Use

Understanding concepts — "How does Cosmos DB partitioning work?"
Learning a service — "Azure Functions overview", "Container Apps architecture"
Finding tutorials — "quickstart", "getting started", "step-by-step"
Configuration options — "App Service configuration settings"
Limits & quotas — "Azure OpenAI rate limits", "Service Bus quotas"
Best practices — "Azure security best practices"

Query Effectiveness

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:

Version when relevant (.NET 8, EF Core 8)
Task intent (quickstart, tutorial, overview, limits)
Platform for multi-platform docs (Linux, Windows)

When to Fetch Full Page

Fetch after search when:

Tutorials — need complete step-by-step instructions
Configuration guides — need all options listed
Deep dives — user wants comprehensive coverage
Search excerpt is cut off — full context needed

Why Use This

Accuracy — live docs, not training data that may be outdated
Completeness — tutorials have all steps, not fragments
Authority — official Microsoft documentation

CLI Alternative (Nix only)

If the Learn MCP server is not available, use a Nix-provided mslearn CLI only (do not use npm):

# Example (once packaged in nixpkgs)
nix run nixpkgs#mslearn -- search "azure functions timeout"

If mslearn is not yet available in nixpkgs, do not fall back to npm; report the limitation and track packaging work in ./Todo.

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.