awb-verify-docs
Skill2 starsChanged 6 months agoMITView on GitHub
WHAT: before writing framework- or library-specific code, ground it in the official docs for the version actually in use — cite the source, and flag anything you could only get from memory as unverified. USE WHEN: writing or changing code that depends on a specific library/framework/API (a hook signature, a config key, a version-sensitive pattern), or about to assert "this library does X" — anywhere a wrong-from-memory detail would compile but misbehave. DO NOT TRIGGER: choosing which library/approach to use (that's awb-research); deciding whether you may reuse outside code (that's awb-external-ref); original logic with no framework/version surface.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- awb-config-guardSkill
- awb-cookSkill
- awb-dead-code-auditSkill
- awb-debugSkill
- awb-external-refSkill
- awb-handoverSkill
- awb-install-and-verifySkill
- awb-lessons-captureSkill
- awb-optimizeSkill
- awb-output-guardSkill
- awb-plan-then-codeSkill
- awb-researchSkill
- awb-reviewSkill
- awb-session-closeSkill
- awb-stress-testSkill
- awb-tddSkill
- awb-uninstallSkill
- awb-using-skillsSkill
- prompt-refinerSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 44
Fetch the authoritative source: Prefer, in order: the project's official docs/changelog → the web standard or spec → official type stubs.
- Distinctive: line 52
Surface a docs-vs-codebase conflict — don't silently pick: If the official pattern differs from what the surrounding code already does (old …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verify against the docs (don't code frameworks from memory)
Announce on activation: "Using awb-verify-docs — I'll ground this in the official docs for the installed version before writing it."
Training data goes stale: an API you "remember" may have been renamed, deprecated, or had its default changed between versions. A detail recalled from memory can compile and still be wrong. This skill makes the cheap check — read the real docs first — routine for the parts where memory most often betrays you.
When this applies
You're about to write or change code against a specific library, framework, or external API, and the exact signature, config key, or behavior matters. The point isn't to doc-check everything — it's to not guess the version-sensitive parts.
Scope
- Does: detect the version in use, fetch the matching official docs, write the code to them, and cite the source — flagging anything still unverified.
- Does NOT: choose between libraries/approaches (→
awb-research), clear a reuse/license decision (→awb-external-ref), or guarantee the docs are current (they can lag the code too — see Honesty).
Process
- Pin the version. Find what's actually installed (
requirements.txt/package.json/ a lockfile /pip show/--version), not the latest. The docs you read must match it — a default or a signature can differ across majors. - Fetch the authoritative source. Prefer, in order: the project's official docs/changelog → the
web standard or spec → official type stubs. Use
WebFetch, or a docs MCP (e.g. Context7) if one is connected. Not authoritative — never the primary source: a random blog, a forum answer, an AI-generated summary, or your own training data. - HARD GATE: each load-bearing detail is cited, or marked UNVERIFIED. For every signature, config
key, or behavior the code relies on, either point to the doc (a deep link with an anchor — it
survives doc restructuring better than a top-level URL) or write
UNVERIFIED: <claim> — from memory, may be outdatednext to it. Do not present a from-memory detail as confirmed. - Surface a docs-vs-codebase conflict — don't silently pick. If the official pattern differs from
what the surrounding code already does (old API vs new, your convention vs theirs), state it and
let the human choose:
CONFLICT: existing code uses X; docs for v<N> recommend Y — match the codebase, or modernize?Choosing silently bakes in a decision that wasn't yours.
Anti-rationalization
| You'll think | Reality |
| "I know this API" | You know an API — possibly a prior major's. The rename / deprecation / changed default is exactly what memory misses; 20 seconds of docs beats a subtle runtime bug. |
| "It compiled, so it's right" | Wrong-from-memory code often compiles and misbehaves (a deprecated default, a changed return shape). Compilation isn't verification. |
| "The docs are basically the same across versions" | Defaults and signatures are where they quietly aren't. Pin the version and read that one. |
Honesty / limits
This is a discipline, not an oracle. Official docs can lag the code, omit edge behavior, or be wrong; the version you read must be the version you run, or the check misleads. It does not make you verify everything — it makes you stop guessing the version-sensitive parts and label what you couldn't confirm. The doc-fetch tool may be unavailable (no network, no MCP); when it is, say so and mark the detail UNVERIFIED rather than proceeding as if confirmed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

