documentation-testing

documentation-testing is a skill for Claude Code from jimmc414/claude-code-plugin-marketplace. It costs 0 tokens per session (1,321 once invoked), scanned A, original, MIT.

A checklist and set of tests for finding incomplete, outdated, or broken developer documentation, such as README setup instructions.

In plain words
What is it for?
Use it to test onboarding, review documentation, check setup guides, and find undocumented tools or environment variables.
Why use it?
It identifies missing prerequisites and configuration details that can make installing or starting a project difficult.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the doc-linter plugin — 1 skill, 1 agent shipped together

Good fit Use it to test onboarding, review documentation, check setup guides, and find undocumented tools or environment variables.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jimmc414/claude-code-plugin-marketplace/documentation-testing
Install

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.

Any agent
npx skills add jimmc414/claude-code-plugin-marketplace --skill documentation-testing
Clone the repo
git clone --depth 1 https://github.com/jimmc414/claude-code-plugin-marketplace

Made for: Claude Code.

Or install doc-linter, the plugin that ships this one along with the rest of its 1 skill, 1 agent.

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.

agentmods badge for documentation-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/jimmc414/claude-code-plugin-marketplace/documentation-testing/github.svg)](https://agentmods.dev/skills/jimmc414/claude-code-plugin-marketplace/documentation-testing)
Your own site
<a href="https://agentmods.dev/skills/jimmc414/claude-code-plugin-marketplace/documentation-testing"><img src="https://agentmods.dev/badge/skills/jimmc414/claude-code-plugin-marketplace/documentation-testing/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.

agentmods 80×15 button for documentation-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/jimmc414/claude-code-plugin-marketplace/documentation-testing"><img src="https://agentmods.dev/badge/skills/jimmc414/claude-code-plugin-marketplace/documentation-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,321 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01321
Opus 5.5 $0.00000 $0.00528
Sonnet 5.5 $0.00000 $0.00264
Haiku 4.5 $0.00000 $0.00132

Measured 1mo ago against content hash e2a36d5499e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

documentation-testing scanned grade A with 1 finding 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 1mo 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.

Asks for rootlowPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

| **Permissions** | File/directory permissions, sudo requirements |

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

plugins/doc-linter/skills/documentation-testing/SKILL.md · 175 lines

How it starts

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

Documentation Testing Skill

Purpose

Provides systematic heuristics for identifying incomplete, outdated, or broken documentation. This skill helps catch the gaps that make onboarding painful for new developers.

Common Documentation Failures

Missing Prerequisites

Projects often assume these are installed without documenting them:

Category Examples
JavaScript Node.js, npm, yarn, pnpm (and which version)
Python Python, pip, poetry, conda (and which version)
Containers Docker, docker-compose, podman
Databases PostgreSQL, MySQL, Redis, MongoDB, SQLite
Cloud CLIs aws, gcloud, az, terraform
Build tools make, cmake, gcc, clang
Version managers nvm, pyenv, rbenv, asdf

Missing Environment Configuration

Look for these patterns that indicate undocumented environment variables:

Language Pattern to detect
JavaScript/TypeScript process.env.XXX
Python os.environ["XXX"] or os.getenv("XXX")
Ruby ENV["XXX"]
Go os.Getenv("XXX")
Rust std::env::var("XXX")

Red flags:

  • References to .env files without .env.example
  • config.yaml with placeholder values but no instructions
  • Environment variables mentioned in code but not in README

Incomplete Setup Steps

Common missing steps that break new developer onboarding:

Step What's often missing
Database setup createdb, migrations, seed data
Service dependencies Starting Redis, Postgres, etc. before the app
SSL/TLS Local HTTPS setup, certificate generation
Host files /etc/hosts modifications for local domains
Ports Required ports and how to check if they're in use
Permissions File/directory permissions, sudo requirements
Git hooks Pre-commit hooks that need manual setup
IDE setup Extensions, settings, debug configurations

Read the full file on GitHub · 175 lines

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.

  1. 1mo ago First seen · 175 lines · 0 tokens per session scan A e2a36d5499e8

Subscribe to this mod's changes

documentation-testing is a skill published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,321 tokens. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

audit-encapsulation

Audit skill-encapsulation violations; remediation runs only behind an explicit fix FILE:LINE. External citations reaching into private surfaces inside .claude/skills/X/ or plugins//skills/X/ (marketplace monorepos) beyond the slash invocation. Use when: 'audit encapsulation', 'find skill leaks', 'skill boundary…

melodic-software/claude-code-plugins · 98 tokens

extract-ssot

Deduplicate repeated markdown (rule files, skill bodies, ADRs, docs) into one named source of truth and migrate every call site to cite it by exact heading. Use when the same prose, literal, or concept recurs across files: 'DRY this prose', 'extract a shared rule', 'single source of truth for X', a value-bump diff…

melodic-software/claude-code-plugins · 99 tokens

audit-progressive-disclosure

Read-only progressive-disclosure audit of agent-facing instruction markdown: grades each file against always-loaded, invocation-loaded, and on-demand tiers and flags split and disclosure defects. Use when: 'progressive disclosure', 'split this file', 'this file is too long', 'too much context', 'mixed concerns', 'hub…

melodic-software/claude-code-plugins · 113 tokens

generate

Build a source-backed AI industry briefing from official vendor publications, configured RSS feeds, GitHub releases, reputable secondary reporting, and user-supplied URLs. Use when: 'ai briefing', 'ai news', 'what's new in AI', 'catch me up on AI', 'prep for AI meeting', 'AI roundup', or 'generate AI slides'.

melodic-software/claude-code-plugins · 72 tokens

quiz-me

Post-work comprehension check: a self-contained HTML report of a completed change (context, intuition, decisions) with a quiz at the bottom that tests the human, not the artifact; also recalls prior quizzed work. Non-gating by default; the quizpolicy userConfig tunes offer cadence. Use when the user says 'quiz me'…

melodic-software/claude-code-plugins · 152 tokens

firecrawl

Scrape, search, crawl, map, parse, or interact with web pages via the firecrawl-cli binary, writing results to disk instead of streaming them into context. Actions: scrape, search, crawl, map, parse, interact, agent, monitor, developer, research, doctor, search-feedback, credit-usage. Use when: 'scrape this page'…

melodic-software/claude-code-plugins · 161 tokens