docs-claim-check

# 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 usage docs, landing-page copy. Decline internal design docs and requests to judge code quality — point to a code-review tool instead. 2. **Never execute commands.** If a claim needs a command output that was not provided, do not run it — emit an **evidence request** naming the exact ...