domains / families / agent-tooling / read-the-damn-docs

read-the-damn-docs

separate

Use when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs, fast-moving product behavior, user requests for latest/current/official behavior, unfamiliar repo docs/specs, errors that may indicate API drift, or high-stakes auth, security, billing, data, migration, deployment, compliance, or privacy behavior. Forces Codex to web-search for current official docs and read primary docs before assuming from memory.

When to use

• implementing third-party APIs
• integrating libraries or frameworks
• upgrading packages or SDKs
• debugging API drift errors
• answering questions about latest official behavior
• handling high-stakes auth or security flows
• reading unfamiliar repo docs or specs
• verifying current version behavior

When not to use

• using Stack Overflow as primary source
• relying on model memory for external APIs
• using old blog posts as primary source
• guessing where authoritative docs can answer

Skill page

Source