Microsoft Code Reference
MicrosoftDocs/mcp
Find working code samples, verify API signatures, and fix Microsoft SDK errors using official docs.
Expert knowledge for Microsoft Foundry Tools (aka Azure AI services, Azure Cognitive Services) development including troubleshooting, best practices, decision making, architecture & design patterns…
$ npx skills add MicrosoftDocs/Agent-Skills --skill microsoft-foundry-tools -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills microsoft-foundry-tools --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/microsoft-foundry-tools .claude/skills/microsoft-foundry-tools && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "microsoft-foundry-tools" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/microsoft-foundry-tools into .claude/skills/microsoft-foundry-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microsoft-foundry-tools", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/microsoft-foundry-toolsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MicrosoftDocs/Agent-Skills --skill microsoft-foundry-tools -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills microsoft-foundry-tools --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/microsoft-foundry-tools .agents/skills/microsoft-foundry-tools && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "microsoft-foundry-tools" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/microsoft-foundry-tools into .agents/skills/microsoft-foundry-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microsoft-foundry-tools", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MicrosoftDocs/Agent-Skills --skill microsoft-foundry-tools -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills microsoft-foundry-tools --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/microsoft-foundry-tools .cursor/skills/microsoft-foundry-tools && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "microsoft-foundry-tools" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/microsoft-foundry-tools into .cursor/skills/microsoft-foundry-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microsoft-foundry-tools", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MicrosoftDocs/Agent-Skills.git --path skills/microsoft-foundry-tools--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MicrosoftDocs/Agent-Skills --skill microsoft-foundry-tools -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills microsoft-foundry-tools --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/microsoft-foundry-tools .gemini/skills/microsoft-foundry-tools && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "microsoft-foundry-tools" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/microsoft-foundry-tools into .gemini/skills/microsoft-foundry-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microsoft-foundry-tools", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MicrosoftDocs/Agent-Skills microsoft-foundry-toolsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MicrosoftDocs/Agent-Skills --skill microsoft-foundry-tools -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/microsoft-foundry-tools .github/skills/microsoft-foundry-tools && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "microsoft-foundry-tools" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/microsoft-foundry-tools into .github/skills/microsoft-foundry-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microsoft-foundry-tools", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MicrosoftDocs/Agent-Skills --skill microsoft-foundry-tools -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills microsoft-foundry-tools --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/microsoft-foundry-tools .opencode/skills/microsoft-foundry-tools && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "microsoft-foundry-tools" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/microsoft-foundry-tools into .opencode/skills/microsoft-foundry-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "microsoft-foundry-tools", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
microsoft-foundry-toolsExpert knowledge for Microsoft Foundry Tools (aka Azure AI services, Azure Cognitive Services) development including troubleshooting, best practices, decision making, architecture & design patterns…
Microsoft Foundry Tools is an agent skill from MicrosoftDocs/Agent-Skills, published by the product's own GitHub organization. Expert knowledge for Microsoft Foundry Tools (aka Azure AI services, Azure Cognitive Services) development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when using Content Moderator, Content Safety, Content Understanding analyzers, REST/.NET APIs, or document extraction workloads, and other Microsoft Foundry Tools related development tasks. Not for Microsoft Foundry (use…
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires network access. Uses mcpmicrosoftdocs:microsoftdocsfetch or fetchwebpage to retrieve documentation.
It sits in Development, covering Design patterns. It works with Azure AI Foundry, Microsoft Azure and .NET. The repository describes itself as: Curated Agent Skills for Microsoft & Azure – giving AI coding assistants structured, real-time expertise from Microsoft Learn docs. The licence is CC-BY-4.0.
Read from SKILL.md and the folder at commit ba74e8f. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
learn.microsoft.comgithub.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
From compatibility in the SKILL.md frontmatter.
Microsoft Foundry Tools loads about 2.4k tokens when it runs. Until then it costs about 165 tokens; SKILL.md has 634 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from MicrosoftDocs/Agent-Skills at commit ba74e8f, republished under its CC-BY-4.0 licence (© MicrosoftDocs). 634 words, ~2,360 tokens.
.claude/skills/microsoft-foundry-tools/SKILL.md (or your agent's skills folder).This skill provides expert guidance for Microsoft Foundry Tools. Covers troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. It combines local quick-reference content with remote documentation fetching capabilities.
IMPORTANT for Agent: Use the Category Index below to locate relevant sections. For categories with line ranges (e.g.,
L35-L120), useread_filewith the specified lines. For categories with file links (e.g.,[security.md](security.md)), useread_fileon the linked reference file
IMPORTANT for Agent: If
metadata.generated_atis more than 3 months old, suggest the user pull the latest version from the repository. Ifmcp_microsoftdocstools are not available, suggest the user install it: Installation Guide
This skill requires network access to fetch documentation content:
mcp_microsoftdocs:microsoft_docs_fetch with query string from=learn-agent-skill. Returns Markdown.fetch_webpage with query string from=learn-agent-skill&accept=text/markdown. Returns Markdown.| Category | Lines | Description |
|---|---|---|
| Troubleshooting | L36-L40 | Troubleshooting steps and FAQs for Content Understanding features, including diagnosing model issues, configuration problems, and resolving common errors in content analysis workflows. |
| Best Practices | L41-L46 | Guidance on improving Content Understanding accuracy, grounding and confidence in document extraction, and migrating from preview to GA Content Understanding APIs. |
| Decision Making | L47-L55 | Guidance for choosing and migrating between Azure AI/Foundry content tools (Content Moderator, Content Safety, Content Understanding), including feature comparisons and pricing/usage planning. |
| Architecture & Design Patterns | L56-L60 | Guidance on choosing and configuring deployment options (serverless, managed, custom) for Content Understanding models, including trade-offs, scalability, and integration patterns. |
| Limits & Quotas | L61-L68 | Quotas, limits, and supported languages for Content Moderator image/list APIs and Content Understanding, plus .NET samples showing how to stay within list and usage limits. |
| Security | L69-L73 | Securing Azure Content Understanding analyzers and data: auth options, network isolation, encryption, access control, and best practices for protecting analyzer inputs/outputs. |
| Configuration | L74-L83 | Configuring and customizing Content Understanding analyzers (prebuilt and custom), document layout, face detection, and cross-resource capacity settings. |
| Integrations & Coding Patterns | L84-L98 | Using Content Moderator and Content Understanding via REST/.NET: text/image/video moderation, term lists, multimodal analysis, and consuming Markdown/structured outputs |
| Topic | URL |
|---|---|
| Troubleshoot and answer FAQs for Content Understanding | https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/faq |
| Topic | URL |
|---|---|
| Apply best practices for Content Understanding accuracy | https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/concepts/best-practices |
| Improve document extraction with confidence and grounding | https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/document/analyzer-improvement |
| Topic | URL |
|---|---|
| Migrate Azure Content Moderator workloads to Content Safety | https://learn.microsoft.com/en-us/azure/ai-services/content-moderator/content-moderator |
| Choose Azure AI tools for document processing | https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/choosing-right-ai-tool |
| Choose between Foundry and Content Understanding Studio features | https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/foundry-vs-content-understanding-studio |
| Migrate Content Understanding from preview to GA APIs | https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/how-to/migration-preview-to-ga |
| Estimate and plan Content Understanding pricing | https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/pricing-explainer |
| Topic | URL |
|---|---|
| Select model deployment options for Content Understanding | https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/concepts/models-deployments |
| Topic | URL |
|---|---|
| Use Content Moderator image lists within quota limits | https://learn.microsoft.com/en-us/azure/ai-services/content-moderator/image-lists-quickstart-dotnet |
| Use supported languages in Content Moderator API | https://learn.microsoft.com/en-us/azure/ai-services/content-moderator/language-support |
| Apply Content Moderator .NET samples with list limits | https://learn.microsoft.com/en-us/azure/ai-services/content-moderator/samples-dotnet |
| Content Understanding service quotas and limits reference | https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/service-limits |
| Topic | URL |
|---|---|
| Secure Azure Content Understanding analyzers and data | https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/concepts/secure-communications |
© MicrosoftDocs, CC-BY-4.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/microsoft-foundry-tools of MicrosoftDocs/Agent-Skills.
Open the folder on GitHubat commit ba74e8f
Microsoft Foundry Tools next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Microsoft Foundry Tools this skillMicrosoftDocs/Agent-Skills | 777 | — | ~2.4k | Automated safety check: Pass | CC-BY-4.0 | |
| Microsoft Code ReferenceMicrosoftDocs/mcp | 1.9k | 4 repos | ~1.1k | Automated safety check: Pass | CC-BY-4.0 | |
| GitVersion .NET DevelopmentGitTools/GitVersion | 3.1k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Scaffoldcodewithmukesh/dotnet-claude-kit | 751 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Architecture Advisorcodewithmukesh/dotnet-claude-kit | 751 | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Akka.Hosting Actor PatternsAaronontheweb/dotnet-skills | 1.2k | 1 repos | ~5k | Automated safety check: Pass | MIT |
MicrosoftDocs/mcp
Find working code samples, verify API signatures, and fix Microsoft SDK errors using official docs.
GitTools/GitVersion
Gives repository-specific .NET guidance for GitVersion: build and test commands, central package management, project layout and coding conventions.
codewithmukesh/dotnet-claude-kit
Architecture-aware feature scaffolding for .NET 10 projects.
codewithmukesh/dotnet-claude-kit
Architecture selection advisor for .NET applications. An agent skill from codewithmukesh/dotnet-claude-kit.
Aaronontheweb/dotnet-skills
Shows how to build entity actors with Akka.Hosting so the same code runs in local unit tests and in a sharded cluster in production.
SebastienDegodez/copilot-instructions
A skill your agent uses when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD…
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure AI Personalizer development including troubleshooting, decision making, security, configuration, and integrations & coding patterns.
MicrosoftDocs/Agent-Skills
Guides Azure solution design by category, from reference architectures and design patterns to technology choices and migrations, fetching current Microsoft Learn pages over the network.
MicrosoftDocs/Agent-Skills
Reference guidance for Azure Advisor work: recommendations, alerts and digests, workbooks, RBAC access and sovereign-cloud limits, fetched from Microsoft Learn.
MicrosoftDocs/Agent-Skills
Looks up Microsoft Learn guidance for Azure AI Vision: Image Analysis, Read OCR containers, smart-crop thumbnails, background removal and video frame analysis, plus limits and deployment.
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure Analysis Services development including troubleshooting.
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure AI Anomaly Detector development including troubleshooting, best practices, limits & quotas, configuration, and deployment.
Works with
Categories
Expert knowledge for Microsoft Foundry Tools (aka Azure AI services, Azure Cognitive Services) development including troubleshooting, best practices, decision making, architecture & design patterns…. Microsoft Foundry Tools is an agent skill from MicrosoftDocs/Agent-Skills, published by the product's own GitHub organization. Expert knowledge for Microsoft Foundry Tools (aka Azure AI services, Azure Cognitive Services) development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns.
Microsoft Foundry Tools fits situations like: using Content Moderator; content Understanding analyzers; document extraction workloads; other Microsoft Foundry Tools related development tasks.
Run `npx skills add MicrosoftDocs/Agent-Skills --skill microsoft-foundry-tools -a claude-code`. Or copy the skill folder (skills/microsoft-foundry-tools in MicrosoftDocs/Agent-Skills) into .claude/skills/microsoft-foundry-tools in your project. Claude Code loads it when a task matches its description.
Run `npx skills add MicrosoftDocs/Agent-Skills --skill microsoft-foundry-tools -a codex`. Or copy the skill folder (skills/microsoft-foundry-tools in MicrosoftDocs/Agent-Skills) into .agents/skills/microsoft-foundry-tools in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MicrosoftDocs/Agent-Skills --skill microsoft-foundry-tools -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/microsoft-foundry-tools, .gemini/skills/microsoft-foundry-tools, .github/skills/microsoft-foundry-tools and .opencode/skills/microsoft-foundry-tools in your project.
SKILL.md names no scripts, command-line tools or credentials: Microsoft Foundry Tools is instructions for the agent only. Compatibility (from SKILL.md): Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation..
SKILL.md names 2 domains. As links in the text: learn.microsoft.com and github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Microsoft Foundry Tools is published under the CC-BY-4.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Microsoft Foundry Tools: Microsoft Code Reference (MicrosoftDocs/mcp, 1.9k stars), GitVersion .NET Development (GitTools/GitVersion, 3.1k stars), Scaffold (codewithmukesh/dotnet-claude-kit, 751 stars) and Architecture Advisor (codewithmukesh/dotnet-claude-kit, 751 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
MicrosoftDocs (a GitHub organization, an official publisher) maintains it in MicrosoftDocs/Agent-Skills, which has 777 GitHub stars. The repository holds 149 skills in this directory. The repository was last updated on October 5, 2026.
Source: MicrosoftDocs/Agent-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.