verification

Validates whether generated answers are supported by retrieved evidence or computed values.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/lakshya4568/DeepContext --skill verification-lakshya4568
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/lakshya4568/DeepContext/tree/main/.agents/skills/verification
Command: npx skills add https://github.com/lakshya4568/DeepContext --skill verification-lakshya4568

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? LLM-generated answers often sound confident while containing claims that are not backed by any retrieved evidence, and documents frequently cite third-party benchmarks or library behaviors that were never checked against primary sources. This Skill provides a shared evidence-sufficiency gate that scores answer grounding before responses are returned, plus a repeatable methodology for fact-checking claims before they are written down. ## Core Features & Use Cases - Evidence-Sufficiency Gate: Extracts claims from a draft answer, links each claim to retrieved evidence, computed values, or flagged inference, and fails the answer when unsupported claims or low confidence are detected. - Aggregation Coverage Check: For aggregation-style queries, verifies that evidence spans the full retrieved set rather than a sampled subset, using a configurable coverage threshold. - Primary-Source Fact-Checking: Applies a confirmed/corrected/not-verified three-way classification when checking third-party claims against original sources like GitHub repos and arXiv papers. - Use Case: A RAG pipeline generates an answer about hybrid retrieval; the gate detects that one sentence has no supporting chunk, triggers a single retry, and returns an honest insufficient-evidence response if the retry also fails. ## Quick Start Run the verification skill to check whether this draft answer is supported by the retrieved evidence chunks before returning it to the user.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I check if an LLM answer is grounded in retrieved evidence?

Use the check_answer_support function, which extracts claims from the draft answer, links each claim to evidence chunks, and returns a pass/fail result with confidence scores. Claims are classified as retrieved, computed, inference, or unsupported.

How to fact-check third-party benchmark claims before citing them?

Fetch the primary source directly, such as the actual GitHub repo or arXiv paper, rather than relying on aggregators. Classify each claim as confirmed, corrected, or not verified, and cite only at the abstraction level you personally verified.

What happens when the evidence-sufficiency gate fails?

The calling pipeline rewrites the query and retries exactly once. On a second failure, the system returns an honest insufficient-evidence response instead of silently answering, which prevents ungrounded answers from reaching users.

Does the verification gate handle aggregation queries differently?

Yes. For aggregation-shaped queries, the gate requires evidence coverage of at least 95 percent of the total candidate set, ensuring answers span the full retrieved data rather than a sampled subset.

What are the limitations of the reference check_answer_support implementation?

The included script uses naive sentence splitting and keyword-overlap matching as runnable stubs, which are not adequate for production. Real deployments should replace them with LLM-based claim extraction and NLI or LLM-as-judge entailment checks.