From hb
Fetches official docs for exact dependency versions to implement features correctly, avoiding hallucinated APIs. Use when working with unfamiliar libraries or when asked to "check the docs."
How this skill is triggered — by the user, by Claude, or both
Slash command
/hb:source-drivenThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Never rely on training data for API usage. Read the actual source of truth.
Never rely on training data for API usage. Read the actual source of truth.
cat package.json | grep -E '"dependencies"|"devDependencies"' -A 50 | head -60package.json (or equivalent manifest) for exact versionsFor each dependency involved:
If docs are unavailable or ambiguous, read the library source in node_modules/.
// UNVERIFIED: could not confirm in docs for v{version}Add a brief comment on non-obvious API usage:
// Ref: https://docs.example.com/v3/api#method
Only cite when the usage is surprising or version-specific. Don't over-comment obvious calls.
| Excuse | Rebuttal |
|---|---|
| "I know this API from training data" | Training data may be outdated or wrong. Check the version. |
| "The docs are too slow to fetch" | One fetch now prevents hours debugging a hallucinated API later. |
| "It's a minor utility, no need to check" | Minor utilities have breaking changes between versions too. |
| "I'll verify later" | Unverified code compounds. Verify now or mark UNVERIFIED. |
// UNVERIFIEDnode_modules/ source over training knowledge when docs unavailablenode_modules/ source// UNVERIFIED: docs for v{closest}, installed v{actual}node_modules/{pkg}/README.md or type definitionsnpx claudepluginhub helderberto/agent-skills --plugin hbFetches current official docs before writing framework-specific code to prevent deprecated API usage. Activates on dependency changes or framework work.
Forces Claude to web-search and read current official documentation before implementing, integrating, or debugging third-party APIs, libraries, frameworks, and services when latest behavior or correctness matters.
Grounds implementation decisions in official documentation, fetching and citing authoritative sources for accurate, version-aware code generation.