anti-hallucination

Verify external API existence and behavior before implementation.

1|Updated Jun 8, 2026

Search Tags:#developer workflow #coding best practices #api verification #tech stack detection #api reference accuracy

Ready to run

npx skills add https://github.com/JuanMS20/bundles-skills --skill anti-hallucination-juanms20

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: anti-hallucination
Source: https://github.com/JuanMS20/bundles-skills/tree/main/skills/general/anti-hallucination
Command: npx skills add https://github.com/JuanMS20/bundles-skills --skill anti-hallucination-juanms20

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents the creation of incorrect API references during coding, ensuring accurate implementation and documentation.

Core Features & Use Cases

Stack Detection: Identifies the tech stack dependencies for a project.
Verification: Verifies API existence and behavior through documentation and references.
Documentation Citing: Encourages citing sources before implementation.
Critical API Verification: Ensures verification for critical APIs like auth, payments, and data persistence.
Never Assume: Provides guidelines against assuming API existence without verification.
Use Case: A developer is about to implement a payment API. This Skill ensures the API exists, is correctly documented, and is compatible with the project's stack before implementation.

Quick Start

Trigger the anti-hallucination protocol before implementing an API by running 'anti-hallucination start'.

Frequently Asked Questions about anti-hallucination

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent API hallucinations when writing code?▼

To prevent API hallucinations, you can trigger a verification protocol that identifies your project's tech stack and cross-references API existence and behavior against official documentation before implementation.

How do I verify external API existence before integrating it into my application?▼

You can verify external API existence by running a protocol that detects your tech stack dependencies and requires manual checks against official documentation and references to ensure accurate behavior.

Why should I cite documentation sources before implementing payment APIs?▼

Citing documentation before implementing payment APIs ensures accurate references and prevents incorrect integration, which is critical for security-sensitive areas like auth, payments, and data persistence.

Can I use this verification protocol with any tech stack?▼

Yes, the protocol performs stack detection to identify your project's dependencies, making it applicable to coding tasks involving external APIs across various tech stacks.

What is the best way to ensure API reference accuracy for security-sensitive APIs?▼

The best way to ensure API reference accuracy is to enforce a never-assume guideline that requires manual verification and documentation checks specifically for critical APIs like auth and payments.

Do I need to manually check documentation to verify API behavior?▼

Yes, the protocol requires manual verification and documentation checks to confirm API existence and behavior, ensuring you do not assume an API exists without proper verification.