docs-claim-check
Check whether the claims in public-facing documentation (README, release notes, install/usage docs) are supported by the evidence the user provides — files, manifests, logs, and command outputs supplied in the conversation. Produces per-claim findings with a confidence label (verified / unsupported / stale-suspected / needs-human) and an explicit "input scope reviewed" statement. Advisory only. Use when the user asks to fact-check docs, verify a README against a repo, audit release notes, or find stale or overstated documentation claims. Do NOT use for standalone code review or bug hunting, se
npx skills add kyungseo/skillstead --skill docs-claim-check --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# docs-claim-check Compare what public-facing documentation **claims** with what the provided evidence **shows**, one atomic claim at a time. Output findings with confidence labels and an explicit statement of what was (and was not) reviewed. This skill renders a judgment backed by evidence. It is not a checklist, not a linter, and not a substitute for code review. ## Before any tool use First confirm that the target documentation or claim text is supplied in the conversation. If it is absent, ask the user to provide it. Do not list, search, or read repository files and do not execute a command to locate the target or evidence. If the target is present but evidence is incomplete, continue with the existing evidence-request procedure below. Ask only for the missing evidence; do not ask the user to provide the target again. ## Boundaries (read first) These are **contractual guardrails**. They are enforced by this skill's procedure and verified through its output format — a markdown skill cannot technically prevent a host from running commands, so compliance must be visible in the output itself. 1. **Public-facing documentation claims only.** README files, release notes, install and u
- Before any tool use
- Boundaries (read first)
- Preflight
- Claim triage
- Label decision tree
- Output contract
- Refusal cases
- Package map
What does the docs-claim-check skill do?
Check whether the claims in public-facing documentation (README, release notes, install/usage docs) are supported by the evidence the user provides — files, manifests, logs, and command outputs supplied in the conversation. Produces per-claim findings with a confidence label (verified / unsupported / stale-suspected / needs-human) and an explicit "input scope reviewed" statement. Advisory only. Use when the user asks to fact-check docs, verify a README against a repo, audit release notes, or find stale or overstated documentation claims. Do NOT use for standalone code review or bug hunting, se
How do I install it?
Run `npx skills add kyungseo/skillstead --skill docs-claim-check --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kyungseo/skillstead, a repository with 69 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.