agentleFS
Sign inStart free
cadela-devcadela-dev/ProjectAtlas/.claude/skills/verification/SKILL.md

verification

Skill16 starsChanged 6 months agoMITView on GitHub

Exact batch reconciliation and verifier boundaries.

47 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use evidence-driven-writing, experiment-results-planning 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.
  • Norman-burySkill

    evidence-driven-writing

    Use when writing or revising Introduction, Related Work, background, literature synthesis, or any section where references must drive claims

    Also in 3 projects that use this

  • Norman-burySkill

    experiment-results-planning

    Use when designing experiments, result tables, mock planning data, evaluation protocols, or results sections before real data are final

    Also in 3 projects that use this

  • +10 more from Norman-bury

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Only verifier can mark project-index rows [x].

    line 25

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

Verifier Rules

Verifier validates the batch contract. Verification must reconcile three sets exactly:

  1. Source files listed in assignments/BATCH_####.md
  2. Outcome lines listed in worker_reports/BATCH_####_WORKER.md
  3. Mirror docs that exist under docs/_file_docs/src/...

A batch fails if any assigned file is missing a mirror doc, missing a worker outcome, has a wrong mirror path, or was skipped because it was binary/asset/unknown.

Verifier checks:

  • mirror docs exist at the exact required paths
  • mirror docs use the required headings
  • worker report exists and lists every assigned source file
  • copied source code is avoided
  • deferred/error files include explicit reasons
  • PROJECT_FILE_INDEX.md is updated: verified files become [x], failed files become [!]

Only verifier can mark project-index rows [x].

Verifier must not silently rewrite worker docs. If small mechanical repair is requested by the prompt, do it and re-run verification. Otherwise mark issues clearly and stop.

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