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 nthnclrk/enablement-skills --skill content-gap-analysisgit clone --depth 1 https://github.com/nthnclrk/enablement-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/nthnclrk/enablement-skills/content-gap-analysis)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/content-gap-analysis"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/content-gap-analysis/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/nthnclrk/enablement-skills/content-gap-analysis"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/content-gap-analysis.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.00066 | $0.00899 |
| Opus 5 | $0.00033 | $0.00449 |
| Sonnet 5 | $0.00013 | $0.00180 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
content-gap-analysis 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 10d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content gap analysis
Decide what to create, update, consolidate, or retire. First separate exists from used. An asset on the wiki that no one can find is not coverage.
Fails. "Zero views this quarter, so retire the security FAQ."
Passes. "The security FAQ exists, is current, and drew 19 failed searches against 6 views. Action: improve discoverability, not retire. The mid-market ROI template does not exist; the enterprise calculator is out of scope. Action: create."
A weekly operating model for owners, review, and publishing is content-governance-system. Raw field-note synthesis is field-feedback-synthesizer.
Confirm Inputs First
Ask only for the inputs that change the backlog:
- Inventory source and the roles, stages, and jobs in scope
- Known field requests, failed searches, or usage with an eligible-audience denominator
- Evaluation horizon: this quarter, half, or annual planning
- Who can own create, update, consolidate, or retire work
If usage, ownership, or freshness is unknown, leave it unknown. Do not invent usage or ROI.
Read The Right Reference
Read references/content-gap-prioritization.md for exists-vs-used tests, action types, and scoring rules. Read references/source-system-guide.md when the inventory comes from a content repository, wiki, or field-signal channel.
Default Workflow
- Build the inventory you can defend. Stable ID, owner, audience, status, last reviewed date, canonical location. Done when each in-scope asset has enough metadata to judge exists vs used.
- Map coverage. Role, stage, job-to-be-done. An enterprise-only asset does not cover a mid-market job.
- Classify the problem before you score it. Missing, stale, duplicated, hard to find, underused, or wrong format. Low usage is a clue, not a diagnosis.
- Separate exists from used. Fit-for-purpose and findable is coverage. Fit-for-purpose and invisible is discoverability. Findable and unused is a distribution or quality question. Missing is create.
- Rate value with visible dimensions. Impact, frequency, strategic alignment. Evidence confidence and effort stay separate. Do not invent weights or divide by effort.
- Assign a decision tier. Mandatory, commit now, validate first, plan, or monitor. High potential with weak evidence is validate first, not build.
- Choose the action. Create, update, consolidate, retire, improve discoverability, or reinforce distribution. Retire only with a successor or an authorized owner, never from low usage alone.
- Sequence within the tier.
Deadline, dependency, effort, owner capacity. Route asset production to
one-pager-and-slide-outline,battlecard-builder, ortalk-track-builder.
What ships with it
3 files 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.
- 10d ago First seen · 73 lines · 66 tokens per session scan A 6f9416e8740d
content-gap-analysis is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 20d ago), licensed MIT. It adds 66 tokens to every session and 899 once invoked, about $0.0003 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-30.
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…