ground

Verify assistant-generated factual claims against local files and external sources.

3|1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/epologee/leclause-skills --skill ground-epologee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ground
Source: https://github.com/epologee/leclause-skills/tree/main/packages/ground/skills/ground
Command: npx skills add https://github.com/epologee/leclause-skills --skill ground-epologee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and verifies potentially incorrect or uncertain claims produced by the assistant by searching local project files and external sources so users can trust corrected outputs before acting on them.

Core Features & Use Cases

  • Identify verifiable claims: Re-reads recent assistant output and formulates sharp verification questions for claims that can be checked.
  • Local and external search: Prioritizes quick checks in the repository (code, tests, changelogs, configs) and escalates to external documentation, issue trackers, or trusted web sources when needed.
  • Synthesis with citations: Presents a clear result per claim (confirmed, nuanced, or incorrect) with supporting links or quotes and limits verification to up to three claims per invocation.
  • Use Case: A user says "dat klopt niet" after a version or API claim; run the workflow to confirm the exact version, behavior, or changelog entry and report findings with sources.

Quick Start

Invoke /ground to verify up to three concrete claims from the assistant's previous answer using local files and external sources and report a sourced confirmation, nuance, or correction.

Frequently Asked Questions about ground

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

FAQPage Schema
How do I verify assistant-generated claims against a codebase?

To verify assistant-generated claims against a codebase, you can identify and prioritize verifiable statements, search local repository files like code and changelogs, and fetch external sources to synthesize a sourced confirmation or correction.

What is the best way to fact-check API versions and code behavior in documentation?

Fact-checking API versions and code behavior involves searching local project files and escalating to external documentation or trusted web sources, then presenting a clear confirmation, nuance, or correction with supporting links and quotes.

How do I check recent chat output for factual accuracy using local files?

Checking recent chat output for factual accuracy requires re-reading recent assistant responses to formulate sharp verification questions, prioritizing quick checks in repository configs and tests, and limiting verification to up to three claims per invocation.

Can I use websearch to confirm uncertain claims from previous responses?

You can use websearch to confirm uncertain claims by escalating to external documentation, issue trackers, or trusted web sources when local repository checks are insufficient to validate the assistant's previous output.

Does claim-prioritization limit how many assertions I can verify at once?

Claim-prioritization limits verification to up to three concrete claims per invocation, identifying the most verifiable assertions from recent assistant output to ensure a clear, sourced confirmation, nuance, or correction.

When should I not use fact-checking for codebase and external source synthesis?

Fact-checking for codebase and external source synthesis should not be used when there is no recent assistant output to verify, as the workflow requires access to previous responses to identify and prioritize verifiable claims.