# Read The Damn Docs

> Use when installing or upgrading a version-sensitive package, SDK, or framework; working with auth, billing, migrations, or another security-sensitive flow; or diagnosing an error that suggests API drift (deprecation, missing exports, changed defaults, version mismatch). Web-searches for current official docs and reads them before assuming from memory. For Anthropic/Claude API questions, defer to the claude-api skill instead.

- Skill: `caneff/read-the-damn-docs` (Agent Skill)
- Install (CLI): `npx skillmds@latest add caneff/read-the-damn-docs`
- Raw SKILL.md: https://api.skillmd.com/api/skills/caneff/read-the-damn-docs/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: caneff (https://skillmd.com/u/caneff)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/caneff/read-the-damn-docs

---


# Read The Damn Docs

Do not guess where authoritative docs can answer the question. Web-search for
the current official docs, open the relevant pages, and read them before
coding. See the description above for the trigger conditions and the
Anthropic/Claude API carve-out.

## What Counts As Docs

Use the most authoritative source available:

- Official product docs, API references, migration guides, changelogs, and
  SDK source/types for third-party behavior. Find these with web search when
  you do not already have the exact URL.
- Package registry metadata for versions.
- Local repo docs, ADRs, and schemas when the question is about
  project-specific behavior rather than a third-party contract.

Avoid Stack Overflow, old blog posts, and memory as the primary source when
official docs exist.

## Required Workflow

1. Identify the exact surface: package name, installed version, target
   version, provider endpoint, or config file.
2. Search the web for the current official docs unless they're already local
   or the user supplied a URL.
3. Open and read the docs closest to that surface.
4. Extract the facts needed: option names, imports, breaking changes, limits,
   permissions, examples for the current major version.
5. Implement or answer using those facts. If the docs conflict with existing
   code, inspect the local code path and call out the discrepancy.
6. Verify with the smallest useful check: typecheck, tests, build, or a local
   reproduction.
7. Name the docs consulted when that evidence affects the recommendation.

## If Docs Are Unavailable

If network access, auth, or missing local files prevents reading the docs,
say that plainly before relying on memory.