CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

66

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

Repository

aiming-lab/MetaClaw

Path

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

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.