How do I install the Analyze Content Gaps skill?

Run npx skillmds add majiayu000/analyze-content-gaps 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 Analyze Content Gaps safe to use?

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

Which AI agents work with Analyze Content Gaps?

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 Analyze Content Gaps free to use?

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

Who published Analyze Content Gaps?

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

Analyze Content Gaps by majiayu000 — Agent Skill

Name: Analyze Content Gaps
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

Analyze Content Gaps Skill

Identify missing, redundant, or underperforming content within a documentation set. This skill compares existing content against user needs and competitive benchmarks to find opportunities for improvement.

Inputs

PATH - The content documentation to analyze (e.g., "/documentation")
USER_NEEDS - (Optional) Boolean, whether to map against user search queries or support tickets (default: true)
COMPETITIVE_ANALYSIS - (Optional) Boolean, whether to compare against industry standards or competitors (default: false)

Workflow

Step 1: Baseline Assessment

Map the current state of content at PATH.

What topics are covered?
What is the depth of coverage?

Step 2: Needs Analysis

Determine what should be covered.

User Needs: Analyze search logs, support tickets, or user stories (if USER_NEEDS is true).
Standards: Compare against standard frameworks or requirements.
Competitors: Compare against competitor documentation (if COMPETITIVE_ANALYSIS is true).

Step 3: Gap Identification

Compare Baseline vs. Needs.

Missing: Topics required but not present.
Thin: Topics present but lacking detail.
Redundant: Multiple pages covering the same topic unnecessarily.
Outdated: Content that no longer matches current needs.

Step 4: Strategic Recommendations

Prioritize gaps based on impact and effort.

Required Outputs

A GAP_ANALYSIS_REPORT in markdown format containing:

Missing Topics: List of high-priority new content to create.
Improvement Areas: List of existing content needing expansion.
Consolidation Targets: List of redundant content to merge.
Strategic Roadmap: Recommended order of execution.

Quick Reference

Purpose: Align content with user needs and business goals.
Outcome: Actionable content strategy roadmap.

---name: analyze-content-gapsdescription: Identify content gaps and organizational opportunities. Analyzes missing content areas, redundancies, and consolidation opportunities.--- # Analyze Content Gaps Skill Identify missing, redundant, or underperforming content within a documentation set. This skill compares existing content against user needs and competitive benchmarks to find opportunities for improvement. ## Inputs - `PATH` - The content documentation to analyze (e.g., "/documentation") - `USER_NEEDS` - (Optional) Boolean, whether to map against user search queries or support tickets (default: true) - `COMPETITIVE_ANALYSIS` - (Optional) Boolean, whether to compare against industry standards or competitors (default: false) ## Workflow ### Step 1: Baseline Assessment Map the current state of content at `PATH`. - What topics are covered? - What is the depth of coverage? ### Step 2: Needs Analysis Determine what *should* be covered. - **User Needs**: Analyze search logs, support tickets, or user stories (if `USER_NEEDS` is true). - **Standards**: Compare against standard frameworks or requirements. - **Competitors**: Compare against competitor documentation (if `COMPETITIVE_ANALYSIS` is true). ### Step 3: Gap Identification Compare Baseline vs. Needs. - **Missing**: Topics required but not present. - **Thin**: Topics present but lacking detail. - **Redundant**: Multiple pages covering the same topic unnecessarily. - **Outdated**: Content that no longer matches current needs. ### Step 4: Strategic Recommendations Prioritize gaps based on impact and effort. ## Required Outputs A `GAP_ANALYSIS_REPORT` in markdown format containing: - **Missing Topics**: List of high-priority new content to create. - **Improvement Areas**: List of existing content needing expansion. - **Consolidation Targets**: List of redundant content to merge. - **Strategic Roadmap**: Recommended order of execution. ## Quick Reference - **Purpose**: Align content with user needs and business goals. - **Outcome**: Actionable content strategy roadmap.

Frequently asked questions