analyze-content-gaps

$npx mdskill add dandye/ai-runbooks/analyze-content-gaps

Detect missing documentation topics and redundant content.

  • Finds underperforming docs by comparing against user needs.
  • Integrates with search logs and support ticket systems.
  • Uses baseline comparison to surface gaps and redundancies.
  • Outputs a prioritized list of missing and thin topics.

SKILL.md

.github/skills/analyze-content-gapsView on GitHub ↗
---
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]
---

# 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.

More from dandye/ai-runbooks

SkillDescription
audit-contentComprehensive content quality and maintenance assessment. Evaluates documentation quality, relevance, maintenance needs, and provides actionable recommendations.
check-duplicates"Check for duplicate or similar cases. Use before deep analysis to avoid investigating the same incident twice. Takes a CASE_ID and returns list of similar cases."
close-case-artifact"Close a case or alert with proper reason and documentation. Use when triage determines an alert is FP/BTP or investigation is complete. Requires artifact ID, type, closure reason, and root cause."
cluster-documentsAutomated content similarity and grouping analysis. Groups related documents by topic, purpose, or content similarity.
confirm-action"Ask the user to confirm before taking a significant action. Use before containment, remediation, or other impactful operations to ensure analyst approval. Presents options and waits for response."
correlate-ioc"Check for existing SIEM alerts and case management entries related to IOCs. Use to understand if an indicator has triggered previous alerts or is part of ongoing investigations. Takes IOC list and returns related alerts and cases."
deep-dive-ioc"Perform exhaustive analysis of a critical IOC. Use when an IOC needs Tier 2+ investigation beyond basic enrichment - includes GTI pivoting, deep SIEM searches, correlation with related entities, and threat attribution. For escalated IOCs requiring comprehensive investigation."
design-metadata-schemaDesign comprehensive metadata frameworks. Develops structured metadata templates and tagging systems.
document-in-case"Add a comment to a case to document findings, actions, or recommendations. Use to maintain audit trail during investigations. Requires CASE_ID and comment text."
enrich-ioc"Enrich an IOC (IP, domain, hash, URL) with threat intelligence. Use when you need to look up reputation and context for an indicator using GTI and SIEM. Returns threat intel findings, SIEM entity summary, and IOC match status."