Skip to content
Security
Skill

/analyze-content-gaps

Identify content gaps and organizational opportunities. Analyzes missing content areas, redundancies, and consolidation opportunities.

BOOST
From plugin
ai-runbooks
12830 skills
Install
$ npx -y skills add dandye/ai-runbooks --skill analyze-content-gaps --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/analyze-content-gaps

Context preview

The summary Claude sees to decide when to auto-load this skill.

Identify content gaps and organizational opportunities. Analyzes missing content areas, redundancies, and consolidation opportunities.

SKILL.md

analyze-content-gaps.SKILL.md
type: Skill
name: analyze-content-gaps
description: Identify content gaps and organizational opportunities. Analyzes missing content areas, redundancies, and consolidation opportunities.
required_roles:
  scribe: roles/scribe.viewer
personas: [information-architect, content-strategist, product-manager]
generated:
  by: process:google-labs-jules
  at: 2026-01-29T21:19:07Z

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.
Read more
Ships withai-runbooks

This repository provides security operations runbooks and role-based guides for AI-assisted cybersecurity workflows.

Get the whole plugin

Other skills on ai-runbooks.