analyzing-kb-gaps
Use when you have Knowledge Base exports and want to identify user pain points, missing articles, and AI assistance opportunities.
npx skills add majiayu000/claude-skill-registry --skill analyzing-kb-gaps --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Analyzing KB Gaps ## Overview Uses the Knowledge Base as a proxy for where users struggle. Identifies high-volume topics, missing guidance, and opportunities for better self-service or AI-assisted resolution. ## When to Use - Have KB article exports to analyze - Want to understand what users struggle with most - Exploring AI assistant opportunities - Planning documentation improvements ## Core Pattern **Step 1: Gather Sources** Read files in: - `inputs/knowledge_base/` - KB article exports - `outputs/insights/voc-synthesis-*.md` - VOC insights (if available, for correlation) **Step 2: Analyze Article Coverage** For each KB article (or category), note: - Topic / Category - Article count - Last updated date - Estimated complexity (simple how-to vs. complex troubleshooting) **Step 3: Identify Gaps** Look for: 1. **High-volume topics** - Many articles = users struggle here 2. **Outdated articles** - Not updated in 6+ months 3. **Missing topics** - VOC mentions issues with no KB coverage 4. **Complex troubleshooting** - Multi-step processes that could be simplified **Step 4: Assess AI Opportunities** For each gap, evaluate: | Opportunity Type | Criteria | Risk Level | |---------------
- Overview
- When to Use
- Core Pattern
- Quick Reference
- Common Mistakes
- Verification Checklist
- Evidence Tracking
What does the analyzing-kb-gaps skill do?
Use when you have Knowledge Base exports and want to identify user pain points, missing articles, and AI assistance opportunities.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill analyzing-kb-gaps --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.