start-gap-finder
Find conceptual gaps in plan/spec documents. Use when user explicitly asks start-gap-finder.
npx skills add majiayu000/claude-skill-registry --skill start-gap-finder --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.
# Plan Gap Finder Find conceptual gaps by running three steps in sequence. Each step is a separate skill invocation. ## Procedure 1. Invoke `gap-finder-1` skill on the document 2. Invoke `gap-finder-2` skill (uses Step 1 output from conversation) 3. Invoke `gap-finder-3` skill (uses Step 2 output from conversation) **IMPORTANT:** Do NOT stop between steps. Output what each step requires, then immediately continue to the next skill. Run all three steps in a single turn.
- Procedure
What does the start-gap-finder skill do?
Find conceptual gaps in plan/spec documents. Use when user explicitly asks start-gap-finder.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill start-gap-finder --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.