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 dandye/ai-runbooks --skill analyze-content-gapsgit clone --depth 1 https://github.com/dandye/ai-runbooksWrote 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/dandye/ai-runbooks/analyze-content-gaps)<a href="https://agentmods.dev/skills/dandye/ai-runbooks/analyze-content-gaps"><img src="https://agentmods.dev/badge/skills/dandye/ai-runbooks/analyze-content-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/dandye/ai-runbooks/analyze-content-gaps"><img src="https://agentmods.dev/badge/skills/dandye/ai-runbooks/analyze-content-gaps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00507 |
| Opus 5 | $0.00014 | $0.00253 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
analyze-content-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.
What it actually says
Analyze Content Gaps Skill
Identify missing, redundant, or underperforming content within a documentation set. This skill compares existing content against user needs and competitive benchmarks to find opportunities for improvement.
Inputs
PATH- The content documentation to analyze (e.g., "/documentation")USER_NEEDS- (Optional) Boolean, whether to map against user search queries or support tickets (default: true)COMPETITIVE_ANALYSIS- (Optional) Boolean, whether to compare against industry standards or competitors (default: false)
Workflow
Step 1: Baseline Assessment
Map the current state of content at PATH.
- What topics are covered?
- What is the depth of coverage?
Step 2: Needs Analysis
Determine what should be covered.
- User Needs: Analyze search logs, support tickets, or user stories (if
USER_NEEDSis true). - Standards: Compare against standard frameworks or requirements.
- Competitors: Compare against competitor documentation (if
COMPETITIVE_ANALYSISis true).
Step 3: Gap Identification
Compare Baseline vs. Needs.
- Missing: Topics required but not present.
- Thin: Topics present but lacking detail.
- Redundant: Multiple pages covering the same topic unnecessarily.
- Outdated: Content that no longer matches current needs.
Step 4: Strategic Recommendations
Prioritize gaps based on impact and effort.
Required Outputs
A GAP_ANALYSIS_REPORT in markdown format containing:
- Missing Topics: List of high-priority new content to create.
- Improvement Areas: List of existing content needing expansion.
- Consolidation Targets: List of redundant content to merge.
- Strategic Roadmap: Recommended order of execution.
Quick Reference
- Purpose: Align content with user needs and business goals.
- Outcome: Actionable content strategy roadmap.
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 · 62 lines · 27 tokens per session scan A f39892f50522
analyze-content-gaps is a skill published in the GitHub repository dandye/ai-runbooks (124 stars, last pushed 27d ago), licensed Apache-2.0. It adds 27 tokens to every session and 507 once invoked, about $0.0001 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…