aif-grounded

Require verifiable evidence before answering fact-sensitive requests.

Updated May 16, 2026
One-click install
npx skills add https://github.com/vulikjulik/DeepLom --skill aif-grounded-vulikjulik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-grounded
Source: https://github.com/vulikjulik/DeepLom/tree/main/.opencode/skills/aif-grounded
Command: npx skills add https://github.com/vulikjulik/DeepLom --skill aif-grounded-vulikjulik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of AI-generated hallucinations, unsubstantiated guesses, and incorrect assumptions that lead to unreliable outputs, especially for high-stakes, fact-sensitive requests where accuracy is non-negotiable.

Core Features & Use Cases

  • 100% Confidence Gate: Only delivers final answers when every factual claim is fully supported by verifiable evidence from the local codebase, command outputs, authoritative documentation, or user-provided sources.
  • Explicit Uncertainty Handling: Returns a structured insufficient information response with a clear checklist of missing evidence instead of making guesses or filling knowledge gaps with assumptions.
  • Evidence-First Workflow: Automatically classifies requests, identifies required evidence sources, and verifies changeable facts (such as current versions, latest policies, or live system states) before generating any output.
  • Use Case: Ideal for security audits, financial compliance checks, legal research, codebase analysis, or any user request that explicitly demands no hallucinations, only if verified, or 100% sure answers.

Quick Start

Invoke the aif-grounded skill when you need a fully verified answer to a high-stakes question, and it will only respond if it can confirm 100% confidence with available evidence.

Frequently Asked Questions about aif-grounded

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

FAQPage Schema
How do I prevent AI hallucinations during codebase analysis and security audits?

To prevent AI hallucinations during codebase analysis, you need an evidence-based confidence gate that blocks unsubstantiated claims. This approach requires explicit sourcing from local codebases or command outputs, returning a missing evidence checklist instead of guessing when information is insufficient.

What is an evidence-first workflow for high-stakes fact verification?

An evidence-first workflow for fact verification classifies requests, identifies required evidence sources, and verifies changeable facts before generating any output. It enforces a 100% confidence gate by matching claims against authoritative documentation or user-provided sources.

How do I enforce no assumptions for AI responses in financial compliance checks?

To enforce no assumptions for AI responses in financial compliance checks, apply guardrails that require explicit evidence sourcing. If full confidence cannot be achieved, the system must return a structured insufficient information response detailing the missing evidence.

Does 100% confidence fact verification work with user-provided documentation?

Yes, 100% confidence fact verification works with user-provided documentation by treating it as an explicit evidence source. The system verifies all changeable facts against these provided sources before delivering a final answer, ensuring zero hallucinations.

What happens when there is insufficient information for a fully verified answer?

When there is insufficient information for a fully verified answer, the system returns a structured insufficient information response. This response includes a clear checklist of missing evidence, explicitly blocking hallucinations and unsubstantiated guesses.