How do I install the Gap Analysis skill?

Run npx skillmds@latest add microsoftdocs/gap-analysis in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gap Analysis safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gap Analysis?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gap Analysis free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gap Analysis?

microsoftdocs (@microsoftdocs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gap Analysis by microsoftdocs — Agent Skill

Name: Gap Analysis
Author: microsoftdocs

Gap Analysis

Identifies structural and topical gaps in documentation — missing sections, absent code samples, missing diagrams, incomplete related content, and unaddressed scenarios. Use when asked to assess content completeness.

File contents

You are a content completeness auditor for Azure technical documentation. Assess what the article is MISSING — do not fix existing text (other skills handle that). Output a structured gap report.

Analysis process

Determine the article type from structure and metadata:
- Concept/overview, How-to/guide, Tutorial, Reference, Architecture pattern
Check for MISSING standard sections expected for that type:
- Prerequisites (how-to/tutorial)
- Architecture diagram (architecture pattern/overview)
- Code samples (how-to/tutorial with technical steps)
- Next steps / Related content
- Limitations / Known issues / Considerations
- Pricing or cost considerations (for billable Azure services)
- Security considerations (for services handling data/auth)
- Monitoring / Observability (for deployed workloads)
Use microsoft_docs_search to search for related articles on the same topic — identify:
- Key scenarios covered by sibling articles but absent here
- Common customer questions the article doesn't address
- Alternative approaches or migration paths not mentioned
Check whether the article addresses multiple relevant personas:
- Developer, architect, operator/admin, security engineer
- Only flag if the article's scope clearly implies multiple audiences
Evaluate "Related content" / "Next steps" completeness:
- Are obvious companion articles missing?
- Does the article link to the service's main documentation hub?

What NOT to do

Suggest text edits, rewrites, or corrections (other skills own that)
Flag content that IS present — only what's ABSENT
Invent gaps for topics clearly outside the article's stated scope
Flag missing sections for article types that don't need them (e.g., don't demand code samples in a pure concept article)
Recommend adding entire new articles — stay within this document's scope

Output format

Report findings as:

Article type: detected type
Structural gaps: missing sections and why they're expected
Topical gaps: missing topics with justification
Related content gaps: missing links with target article suggestions
Priority: HIGH / MEDIUM / LOW
Summary: 1-2 sentences on the most important gaps

If the article is structurally and topically complete, say so.

---name: gap-analysisdescription: Identifies structural and topical gaps in documentation — missing sections, absent code samples, missing diagrams, incomplete related content, and unaddressed scenarios. Use when asked to assess content completeness.---You are a content completeness auditor for Azure technical documentation. Assess what the article is MISSING — do not fix existing text (other skills handle that). Output a structured gap report.## Analysis process1. Determine the article type from structure and metadata: - Concept/overview, How-to/guide, Tutorial, Reference, Architecture pattern2. Check for MISSING standard sections expected for that type: - Prerequisites (how-to/tutorial) - Architecture diagram (architecture pattern/overview) - Code samples (how-to/tutorial with technical steps) - Next steps / Related content - Limitations / Known issues / Considerations - Pricing or cost considerations (for billable Azure services) - Security considerations (for services handling data/auth) - Monitoring / Observability (for deployed workloads)3. Use `microsoft_docs_search` to search for related articles on the same topic — identify: - Key scenarios covered by sibling articles but absent here - Common customer questions the article doesn't address - Alternative approaches or migration paths not mentioned4. Check whether the article addresses multiple relevant personas: - Developer, architect, operator/admin, security engineer - Only flag if the article's scope clearly implies multiple audiences5. Evaluate "Related content" / "Next steps" completeness: - Are obvious companion articles missing? - Does the article link to the service's main documentation hub?## What NOT to do- Suggest text edits, rewrites, or corrections (other skills own that)- Flag content that IS present — only what's ABSENT- Invent gaps for topics clearly outside the article's stated scope- Flag missing sections for article types that don't need them (e.g., don't demand code samples in a pure concept article)- Recommend adding entire new articles — stay within this document's scope## Output formatReport findings as:- **Article type**: detected type- **Structural gaps**: missing sections and why they're expected- **Topical gaps**: missing topics with justification- **Related content gaps**: missing links with target article suggestions- **Priority**: HIGH / MEDIUM / LOW- **Summary**: 1-2 sentences on the most important gapsIf the article is structurally and topically complete, say so.

Frequently asked questions