re0-upgrade
Bring your installed paperthin skills up to the full current catalog in one step: retire…
Verify reality-grounded claims against external sources in both directions before they ship — could the 'absurd' be real, could the 'obvious' be false or long-established? Use whenever an artifact, or the sentence you are about to write, asserts something as plausible,
$ npx -y skills add LilMGenius/paperthin --skill factchk --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/factchkContext preview
The summary Claude sees to decide when to auto-load this skill.
Verify reality-grounded claims against external sources in both directions before they ship — could the 'absurd' be real, could the 'obvious' be false or long-established? Use whenever an artifact, or the sentence you are about to write, asserts something as plausible,
name: factchk description: "Verify reality-grounded claims against external sources in both directions before they ship — could the 'absurd' be real, could the 'obvious' be false or long-established? Use whenever an artifact, or the sentence you are about to write, asserts something as plausible, realistic, absurd, novel, or impossible from intuition rather than a checked source; before relying on a factual claim in prose, a design rationale, a research claim, or a plan. Fires on metacognitive doubt — when you can't actually know, verify instead of trusting the feeling. Scans read-only, then fixes the clear errors or flags the judgment calls; leaves deliberate fiction alone."
Check what's asserted as real against reality — in both directions — before it ships.
The author's "plausible / absurd / novel" is the least reliable line in any artifact. Human priors fail **both ways** — they exclude the real (desert frogs exist) and normalize the impossible (weightless crates). `factchk` scans claims presented as reality-grounded, verifies each against external sources in both directions, and fixes or flags. Its scope is a claim about *the world* — whether what's asserted as real is real — not the soundness of a validation or the survival of a whole plan.
1. Scan for **reality-grounded assertions** — anything leaning on "this is plausible / realistic / absurd / novel / impossible because X," including the claim you are *about to write*, not only those already on the page. 2. Verify each against **external sources** (web search, open references) in **both directions**: could the "absurd" be real? could the "obvious" or "novel" be false or long-established? If you cannot reach a source, **flag — never assert from intuition**. 3. **Fix or flag:** a mechanically-clear error (a wrong date, a misattributed source, a falsified number) → correct it with a cited source; a judgment call (a contested or interpretive claim) → surface it, don't silently rewrite. 4. Report each claim, its verdict, the source, and — for a failed claim — which direction it failed.
Before finishing: every verdict traces to a citable external source, not a reworded prior intuition — and the report reads as fixes-vs-flags, not restated intuitions.
Turning old engineering wisdom into reflexes your agent reaches for on its own. On any agent | Claude Code, Codex, OpenCode, Antigravity, Copilot, Cursor, Grok-Build, Pi, Hermes, OpenClaw, etc.
Repo: LilMGenius/paperthin
Bring your installed paperthin skills up to the full current catalog in one step: retire…
Audit and consolidate a fact that's scattered across places into one canonical source, after…
Rebuild the human's lost context on a project from live state, in plain language: what needs…
Read the live cycle state and return the single highest-leverage next best action, not a…
Run repeated build -> QA -> re0-memo -> re0-work cycles while preserving learning and letting…
Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns,…