aif-grounded

Enforces evidence-based answers with a confidence gate that blocks unverified claims.

31|2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/letuhao/lore-weave --skill aif-grounded-letuhao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-grounded
Source: https://github.com/letuhao/lore-weave/tree/main/.cursor/skills/aif-grounded
Command: npx skills add https://github.com/letuhao/lore-weave --skill aif-grounded-letuhao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI assistants often guess when information is missing, producing hallucinated answers about versions, APIs, or code behavior. This Skill acts as a reliability gate that forces evidence-based reasoning and returns "insufficient information" instead of fabricated answers. ## Core Features & Use Cases - Confidence Gate: Computes a 0-100 confidence score and only delivers a final answer at 100/100, when every claim is backed by repo files, command outputs, or provided docs. - Request Classification: Sorts requests into repo-grounded, doc-grounded, or external-facts categories, with mandatory verification for changeable facts like "latest" versions or current pricing. - Structured Output: Produces a strict answer format with evidence citations and verification checks, or a "what's missing" checklist telling you exactly what to provide to reach full confidence. - Use Case: Before applying a code change in an unfamiliar repo, ask the assistant to confirm the approach only if fully verified; it will either deliver an evidence-backed patch or list the exact commands and files needed to proceed safely. ## Quick Start Ask the assistant to answer your question using the grounded skill only if it is 100% sure based on verifiable evidence.

Frequently Asked Questions about aif-grounded

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

FAQPage Schema
How do I stop an AI assistant from hallucinating answers?

Use a reliability gate that requires every factual claim to be backed by evidence from repo files, command outputs, or provided docs. If any unknown remains, the assistant returns an insufficient-information response listing exactly what is missing instead of guessing.

How to verify AI answers about latest library versions?

Treat version and currency claims as changeable facts requiring mandatory verification against authoritative docs, release notes, or logs. If verification is impossible with available tools, the answer is refused and the needed source is requested.

When should I use a grounded-answer workflow instead of a normal chat?

Use it for high-stakes requests: security, finance, legal, or medical topics, questions containing words like "latest" or "current", and code changes where a wrong assumption is costly. It is also useful after context loss to avoid accidental assumptions.

Can the grounded gate apply code changes automatically?

It only applies patches once confidence reaches 100, meaning requirements are precise and build or test verification exists. If the repo lacks a verification path, it returns insufficient information and proposes the minimal validation needed.

What happens when confidence is below 100 in the grounded workflow?

The assistant does not answer or implement anything. It outputs the current confidence score, the top reasons it is not 100, the exact missing evidence, and one to three concrete commands or documents the user can provide to reach full confidence.