Hallucination detector
Skill AtulPurohit/Antigravity-Awesome-Skills/skills/hallucination-detector
Installable GitHub library of 300+ professional agentic skills for Claude Code, Antigravity IDE, Gemini CLI, Cursor, and Copilot. Features a custom NPX installer, 9 stack-specific bundles, validation schemas, security auditing, and an interactive catalog explorer app.
npx -y skills add AtulPurohit/Antigravity-Awesome-Skills --skill hallucination-detectorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Professional Hallucination Detector Expert skill. Integrate LLM API workflows, safe system prompt guidelines, and agentic workflows.
SKILL.md
1.3 KB, as published. Nobody here has run it
Hallucination Detector Expert
Purpose
Manage and implement Hallucination Detector Expert requirements efficiently within enterprise applications.
Core Concepts
Detailed operational framework for Hallucination Detector Expert:
1️⃣ Overview and Strategy
Understanding boundaries, rules, and best practices for the hallucination-detector feature domain.
2️⃣ Code Implementation Reference
# LLM completion caller
response = llm.generate(
prompt="Explain topic step by step.",
temperature=0.0
)
3️⃣ Checklist & Validation Rules
- Integration validation checklist completed.
- Code conventions and naming rules followed.
- Strict type safety constraints verified.
- Security standards checked.
Outputs
- System integration pattern definitions.
- Code templates and examples.
- Test validation checklists.