MetaClaw avoid-hallucinating-specifics

Common mistake — stating specific facts (API endpoints, library versions, config options, function signatures) with false confidence when uncertain. Always flag uncertainty rather than guessing specifics.

install

source · Clone the upstream repo

git clone https://github.com/aiming-lab/MetaClaw

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/aiming-lab/MetaClaw "$T" && mkdir -p ~/.claude/skills && cp -r "$T/memory_data/skills/avoid-hallucinating-specifics" ~/.claude/skills/aiming-lab-metaclaw-avoid-hallucinating-specifics && rm -rf "$T"

manifest: memory_data/skills/avoid-hallucinating-specifics/SKILL.md

source content

Avoid Hallucinating Specifics

High-risk categories for hallucination:

Specific API endpoint URLs or request/response schemas.
Library version numbers and feature availability per version.
Names of real people, organizations, or publications.
File paths and environment-specific configuration.

Prevention:

If unsure of a specific value, say so explicitly.
Recommend the user verify against official documentation.
Use
```
<version>
```
or
```
<your-endpoint>
```
as placeholders rather than guessing.

Anti-pattern: Confidently stating a URL or function signature that sounds right but does not exist.