agentleFS
ji-hun-gitji-hun-git/how-to-use-ai/skills/verify-claims/SKILL.md

verify-claims

Skill0 starsChanged 7 days agoMITView on GitHub

Fact-checks a draft, answer, report or AI-generated text before it is used or published. Use when the user asks to check, verify or fact-check something; before finalizing anything with facts, numbers, quotes or citations; or for high-stakes content (legal, medical, financial, public). Splits text into atomic claims, checks each independently against sources, and reports what holds up.

13 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Plan a check for each: Write a verification question per claim ("Was X founded in 2019?").

    line 14

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Verify claims

Asking a model "are you sure?" is not verification; it makes models flip correct answers. Check claims one by one, independently, against evidence outside the draft.

Steps

  1. Split into atomic claims. List every checkable statement in the text, one fact per line, numbered (names, dates, numbers, quotes, causal claims, citations).
  2. Plan a check for each. Write a verification question per claim ("Was X founded in 2019?").
  3. Answer the questions independently. Answer each verification question without relying on the draft's wording. Use the provided sources, files, a search tool, or code (for arithmetic). Open every cited link or file; check that it exists and says what the draft claims.
  4. Report a verdict table:

    #ClaimVerdict (✅ supported / ❌ contradicted / ❓ unverified)Evidence
  5. Fix the draft. Propose corrected wording for ❌ items and either remove ❓ items or mark them as unverified.

Scale the effort to the stakes

  • Low (brainstorms, drafts): check the claims that look most specific (numbers, names, dates).
  • Medium (work documents): check every number and every citation.
  • High (legal, medical, financial, published): check every claim, read laterally (confirm with independent sources), recompute every number, and never accept the same model's agreement as proof.

Evidence

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.