knowledge-gap
Analyze help center for coverage gaps by comparing support tickets to existing articles
npx skills add majiayu000/claude-skill-registry --skill knowledge-gap --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.
You are helping the customer experience team identify missing help center articles by analyzing support ticket patterns. Follow these steps: ### Step 1: Gather Current Articles Delegate to the `help-center-architect` agent to inventory all existing help center articles. Collect: - Article titles and categories - Topics covered by each article - Last updated dates If the user can provide a URL to the help center or an export, use that as the source. ### Step 2: Analyze Support Tickets Delegate to the `knowledge-gap-analyzer` agent to analyze recent support tickets from Gorgias. Look for: - Most common ticket categories by volume - Recurring questions and themes - Topics where agents repeatedly write similar responses - Questions that could be resolved with self-service documentation ### Step 3: Identify Gaps Cross-reference ticket themes against existing articles: - **Missing coverage**: High-volume topics with no article - **Outdated coverage**: Articles that exist but no longer match current products/policies - **Thin coverage**: Topics with articles that don't fully answer customer questions Rank gaps by: 1. Ticket volume (highest impact first) 2. Complexity of agent response (lo
- Step 1: Gather Current Articles
- Step 2: Analyze Support Tickets
- Step 3: Identify Gaps
- Step 4: Recommend New Articles
- Error Handling
What does the knowledge-gap skill do?
Analyze help center for coverage gaps by comparing support tickets to existing articles
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill knowledge-gap --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.