check-the-docs — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited check-the-docs (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Before calling into an external library or API, confirm the API is real and current — do not code it from memory and hope.
X is not a function, unexpected argument).package.json / lockfile / requirements.txt. Match the docs to that version, not the latest.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.
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.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.