agentleFS
Sign inStart free
surfmind-spacesurfmind-space/awesome-surfmind/skills/fact-check/SKILL.md

fact-check

Skill8 starsChanged 5 months agoMITView on GitHub

Extracts factual claims from selected text or a page and checks each against the visible context and available sources, flagging what is supported, weakened, contradicted, or still unverified. Use when the user says "fact check this", "verify", "is this true", "check the sources", or asks about a page's accuracy, credibility, or possible misinformation.

38 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use deep-research, seo and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • NVIDIASkill

    deep-research

    Queue deep, multi-step research and analysis tasks to the DeepAgents worker. Supports execution depth presets, request-specific rubrics, SubAgent delegation, and RubricMiddleware cross-validation.

    Also in 4 projects that use this

  • nilssonrSkill

    seo

    Full SEO workflow for auditing pages and creating SEO-optimized content. Provides checklists with educational explanations aligned with Google Search Central documentation.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 2

    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:

    Check each claim against the visible context, its cited sources, and any web search or MCP/tool results available.

    line 16
  2. Distinctive:

    When support is incomplete, say what is missing and what evidence would change the verdict.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 31 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

Fact Check

Pull the factual claims out of the page and check each against the visible context and available sources. Never invent facts, quotes, numbers, or sources, present a guess as established, or overclaim what the evidence actually supports.

  1. Extract concrete, checkable claims from the selected or visible content. Skip pure opinions unless they imply facts, and watch for cited sources, links, dates, and numbers that a claim should trace to.
  2. Check each claim against the visible context, its cited sources, and any web search or MCP/tool results available. Prefer primary and official sources when a claim affects money, health, legal, safety, or reputation decisions.
  3. Classify each claim: supported, weakly supported, unsupported, contradicted, or needs more evidence. If a claim is ambiguous (a date that conflates two events, a word like "all" or "always" that may overstate), split it or mark it weakly supported rather than forcing a clean verdict.
  4. When support is incomplete, say what is missing and what evidence would change the verdict.

Report each claim with its Status, Evidence used, Reasoning, and what to verify next. Preserve exact names, numbers, links, dates, and currencies, and don't let a single low-quality source settle a claim on its own.

Example

Page text: "The EU AI Act took effect in 2024 and bans all facial recognition."

Claim: The EU AI Act took effect in 2024. Status: Weakly supported Evidence used: The page shows a 2024 date but blurs the entry into force date with the later phased application dates. Reasoning: The Act entered into force in 2024, yet most obligations apply later, so "took effect" is only partly accurate. Verify next: The official EU legislation timeline for when each obligation starts to apply.

Claim: The EU AI Act bans all facial recognition. Status: Contradicted Evidence used: No source on the page supports a blanket ban; the linked summary lists narrow exceptions. Reasoning: The Act restricts specific real-time biometric uses rather than banning all facial recognition, so "all" overstates it. Verify next: The exact prohibited and high-risk categories in the primary text.

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.

Check your setup, free