agentleFS
Sign inStart free
AmethystLunaAmethystLuna/embedded-workbench/skills/fact-check/SKILL.md

fact-check

Skill32 starsChanged 7 days agoMITView on GitHub

Use when reviewing design documents, architecture specs, technical proposals, or plans that make claims about API names, file paths, enum values, counts, or mechanism feasibility — a lightweight claim-by-claim check against the codebase with evidence. Built into embedded-workbench as the fallback when the full dsh-model-everything plugin (or its predecessor logicprobe) is not installed. NOT for state machines, protocol/retry logic, or 'always'/'never' behavioral claims that need executable model verification — those require dsh-model-everything (or logicprobe).

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

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

  • 0

    Common

    Most of the 31 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:

    Verify each against the codebase with evidence (file:line + excerpt).

    line 32

“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 (fallback)

Lightweight claim verification built into this plugin. Use it when the full dsh-model-everything plugin — or its predecessor logicprobe — is not installed. It checks every verifiable claim in a document/plan against the codebase with evidence, without model escalation.

When to use

  • Design docs, architecture specs, technical proposals, refactoring plans that name APIs, types, files, enums, counts, or mechanisms.
  • Proactively when a plan will be approved (plan-mode gate) and logicprobe is unavailable.

What to verify (per claim)

Claim typeMethod
Numeric claims (counts, sizes, frequencies)grep -c / grep -rn
API/type/enum namesExtract actual signatures/values from headers
File paths and line numbersConfirm existence and content
Mechanism feasibilityCheck language standard / compiler support

Process

  1. Enumerate every verifiable claim (quote it verbatim).
  2. Verify each against the codebase with evidence (file:line + excerpt).
  3. Output per claim: claim → evidence → verdict.

Output format

  • Claim: <verbatim quote>
  • Evidence: <file:line + grep/read excerpt>
  • Verdict: confirmed | refuted | unverifiable
  • Correction direction (when refuted) — never fix inline.

Append a ## Plan Verification block:

## Plan Verification
- **Mode**: fact-check (fallback — logicprobe plugin not installed)
- **Claims checked**: [N] confirmed, [M] refuted, [K] unverifiable
- **Escalation**: model verification NOT run (requires logicprobe plugin)

Boundaries

  • No executable model verification — no state-space exploration, no harness.
  • State machines (≥3 states), ACK/NACK/retry/timeout logic, lock/unlock ordering, and "always"/"never"/"guaranteed" claims require the logicprobe plugin: install it (see .dsh/INSTALL.md) or tell the user verification is degraded to manual mode for those claims.
  • Checking a claim is not a security audit; being checked ≠ being safe.

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