A documentation health audit that checks structure and meaning across project documents. It looks for issues such as broken links, unused pages, duplicate content, unclear terms, incomplete decision records, and outdated information.

Use it to review a project's README files, Markdown documentation, architecture decisions, terminology, links, and required documents.

It helps find documentation problems that make project knowledge hard to trust or maintain. Findings can be organized into a GitHub epic with linked issues.

kb-groom — Skill for Claude Code by artem-from-ua

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add artem-from-ua/claude-plugins

Claude Code

/plugin install kb-grooming

Made for: Claude Code.

Or install kb-grooming, the plugin that ships this one along with the rest of its 2 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/kb-groom/github.svg)](https://agentmods.dev/skills/artem-from-ua/claude-plugins/kb-groom)

Your own site

<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/kb-groom"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/kb-groom/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/kb-groom"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/kb-groom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,586 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00068	$0.01586
Opus 5	$0.00034	$0.00793
Sonnet 5	$0.00014	$0.00317
Haiku 4.5	$0.00007	$0.00159

Measured 11d ago against content hash 9a763660a8f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

kb-groom 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.

plugins/kb-grooming/commands/kb-groom/SKILL.md · 143 lines

How it starts

The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.

KB Grooming — Documentation Health Analysis

Run a full documentation health check on the current project.

Steps

1. Load configuration

Resolve config using this priority (first found wins):

Project: .claude-plugin/kb-grooming.json in the project root
Legacy project: .claude/kb-grooming.json in the project root
Global: ~/.claude/kb-grooming.json
Defaults: use built-in defaults from ${CLAUDE_PLUGIN_ROOT}/templates/kb-grooming.json

If no config file exists anywhere, use AskUserQuestion:

Use defaults — proceed with built-in configuration
Run setup first — invoke /kb-grooming-setup and stop

Display which config was loaded (path or "built-in defaults").

2. Structural scan

Run the structural analysis script:

env CLAUDE_PROJECT_DIR="<project_root>" KB_CONFIG_FILE="<config_path>" bash "${CLAUDE_PLUGIN_ROOT}/scripts/kb-structural-scan.sh"

The script outputs a file path to a JSON report. Read that file to get structural findings.

Display a brief status: "Structural scan complete: X findings in Y files."

3. Load context for semantic analysis

Gather these inputs for the semantic subagent:

Structural report — the JSON from step 2
Playbook presets — if playbook plugin is configured, read active preset files from ~/.claude/plugins/cache/artem-from-ua/playbook/*/presets/. Extract only RULES zones (content between  markers). Skip if playbook is not installed.
Project CLAUDE.md — read CLAUDE.md from project root (if exists)
Global CLAUDE.md — read ~/.claude/CLAUDE.md (if exists)
Documentation files — read all .md files in scope (per config scope.include / scope.exclude). For files longer than 500 lines: include first 100 lines + last 50 lines with a [... truncated ...] marker.

4. Semantic analysis

Check which semantic checks are enabled in config (readmeCompliance, terminologyConsistency, adrCompleteness, contentActuality).

If at least one semantic check is enabled, launch a subagent:

Read the full file on GitHub · 143 lines

Files

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.

Changes

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 · 143 lines · 68 tokens per session scan A 9a763660a8f3

Subscribe to this mod's changes

kb-groom is a skill published in the GitHub repository artem-from-ua/claude-plugins (11 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 1,586 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.

Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens