Check The Docs
Use when writing or modifying code that calls an external library, framework, SDK, or API — especially one that is niche, recently updated, or whose exact method names and parameters you are not certain of. Makes the agent confirm real, current API signatures before using them, instead of inventing plausible-but-wrong calls from memory.
Install
$ agentstack add skill-buildmoonshot-skillpacks-check-the-docs ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-buildmoonshot-skillpacks-check-the-docs) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Check the Docs
Before calling into an external library or API, confirm the API is real and current — do not code it from memory and hope.
When to stop and check
- You're reaching for a method, option, or parameter and you're not certain it exists with that exact name/shape.
- The library has had major version changes (the API you remember may be gone).
- It's niche or fast-moving — small libraries and recent releases are where memory is least reliable.
- The user reported an error that looks like a wrong signature (
X is not a function, unexpected argument).
What to do
- Verify the signature against current documentation, the installed version's types/source, or an official reference — not your recollection.
- Check the installed version. Read
package.json/ lockfile /requirements.txt. Match the docs to that version, not the latest. - Prefer the project's existing usage. If the codebase already calls this library, copy that real, working pattern over anything you'd reconstruct from memory.
When you can't verify
Say so, and mark the call as unverified: "I used client.search(...) from memory — confirm this matches your installed version, as I couldn't check the docs." An honest flag beats a confident hallucination.
Why this matters
Hallucinated API calls are the classic agent failure: confident, plausible, and completely wrong — array.removeWhere(), a timeout option that doesn't exist, a renamed method from three versions ago. They cost a debugging session to track down. Thirty seconds of checking prevents them.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: buildmoonshot
- Source: buildmoonshot/skillpacks
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.