agentleFS
mementomori-comementomori-co/maker-mastery/.claude/skills/verify/SKILL.md

verify

Skill2 starsChanged 25 days agoMITView on GitHub

Use when a research inbox file or one quoted claim must be fact-checked independently before it is filed or told to you. Runs the fact-checker in a fresh context that sees only the claims, never the researcher's reasoning.

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use genie-hacks, workfly and 10 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.
  • automagik-devSkill

    genie-hacks

    Browse, search, and contribute community hacks — real-world patterns for provider switching, teams, skills, hooks, cost optimization, and more.

    Also in 3 projects that use this

  • automagik-devSkill

    workfly

    Discover a procedure and build its saved workflow — dynamic discovery, drafted script, adversarial verification, landed in the catalog.

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • AviadPSkill

    risk-assess

    Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 6 projects that use this

  • +2 more from automagik-dev
  • +1 more from TheKREATORS

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If $ARGUMENTS is a file path, read that file only and verify every row.

    line 11
  2. Very specific:

    After every researcher run, and before any number, setting, licence term or hardware fact reaches knowledge\ or you.

    line 14
  3. Very specific:

    Read the claims file (or the quoted claim).

    line 17
  4. Very specific:

    Write research\verified\<topic-slug>\<question-slug>.md (same slugs as the inbox file.

    line 20

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

Overview

Verify: $ARGUMENTS

If $ARGUMENTS is a file path, read that file only and verify every row. If it is a quoted claim, treat it as a one-row claims table with no source and find the primary source yourself.

When to use

After every researcher run, and before any number, setting, licence term or hardware fact reaches knowledge\ or you.

Steps

  1. Read the claims file (or the quoted claim). Do not open anything under research\inbox\ other than the given file.
  2. Fetch every cited URL yourself; on HTTP 402/403 use curl -sL -A "Mozilla/5.0" into a scratch file under work\ and read the text.
  3. Assign VERIFIED / CONTRADICTED / PARTIAL / UNVERIFIABLE per row with a short quote, URL and version dependence.
  4. Write research\verified\<topic-slug>\<question-slug>.md (same slugs as the inbox file; for a quoted claim use adhoc\<date>-<slug>.md).
  5. Return the path and counts.

Common rationalizations

RationalizationReality
"The URL looks official, skip fetching."Official-looking URLs can be dead or wrong. Fetch it.
"I'll peek at the inbox folder for context."Context is contamination. One file.

Red flags

  • A verdict without a fetched URL and quote.
  • Softened language on a CONTRADICTED row.

Verification

  • Every row has verdict, quote, fetched URL, version note.
  • Output file written and path returned.

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.