Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add kapa-ai/kapa-skills --skill analyze-coverage-gapsgit clone --depth 1 https://github.com/kapa-ai/kapa-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kapa-ai/kapa-skills/analyze-coverage-gaps)<a href="https://agentmods.dev/skills/kapa-ai/kapa-skills/analyze-coverage-gaps"><img src="https://agentmods.dev/badge/skills/kapa-ai/kapa-skills/analyze-coverage-gaps/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kapa-ai/kapa-skills/analyze-coverage-gaps"><img src="https://agentmods.dev/badge/skills/kapa-ai/kapa-skills/analyze-coverage-gaps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00032 | $0.00675 |
| Opus 5 | $0.00016 | $0.00338 |
| Sonnet 5 | $0.00006 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
analyze-coverage-gaps scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Coverage Gaps
You are helping the user analyze a Kapa coverage gaps export to identify where their documentation needs improvement.
Introduction
Before doing anything else, briefly explain to the user what this process is and how it works:
- Coverage gaps are clusters of user questions where Kapa could not find sufficient information in the knowledge sources to provide a good answer.
- First, the CSV export will be parsed into a directory of individual cluster files — one per topic.
- You will then walk through each cluster one by one, analyze the existing documentation, and recommend whether it needs a documentation fix or requires no action.
- The user makes the final call on each cluster and can choose to fix documentation issues on the spot.
- Progress is tracked by moving cluster files between directories (e.g.
to_do/→done/), so the work can be resumed across multiple sessions.
Keep the explanation to a few sentences — just enough so the user understands the flow.
Setup
- Run the setup script to parse the CSV and create cluster markdown files:
bash ${CLAUDE_SKILL_DIR}/scripts/setup.sh "$csv_path"
- Verify the files were created by listing
coverage_gaps/to_do/.
Workflow
Walk through each cluster one at a time. For each cluster:
- Read the cluster — show the user the title, summary, thread count, unique users, and questions. If the unique user count is low relative to the thread count, flag this to the user — it means a small number of people asked repeatedly rather than many users hitting the same gap.
- Analyze the documentation — search the docs in this repository to understand what is already documented about the topic. Check relevant pages, FAQs, and configuration references.
- Present your assessment to the user. Categorize it as one of:
- No action needed — already documented, noise, or not a documentation issue
- Documentation fix — there is a real gap in the documentation that should be addressed
- Wait for the user's decision before moving the file. The user may agree, disagree, or want to discuss further. They may also want to make the fix immediately.
- Update the cluster file with the analysis and decision, then move it to the appropriate directory based on the user's instruction.
- Move to the next cluster when the user is ready.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 55 lines · 32 tokens per session scan A 474da408b99a
analyze-coverage-gaps is a skill published in the GitHub repository kapa-ai/kapa-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 675 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…