agentleFS
Sign inStart free
itseffiitseffi/agentic-os/.agents/skills/verification/SKILL.md

verification

Skill114 starsChanged 10 months agoMITView on GitHub

Verify before claiming completion. No claims without fresh verification evidence. Use before marking work done.

47 other projects use a version of this, 1 of them edited.

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

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

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 8

    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:

    Use when about to claim work is complete, fixed, or passing.

    line 8
  2. Distinctive:

    If you haven't run the verification command in this message, you cannot claim it passes.

    line 16
  3. Distinctive:

    Before claiming any status or completion:

    line 20
  4. Distinctive:

    If NO: State actual status with evidence

    line 26
  5. Distinctive:

    If YES: State claim WITH evidence

    line 27
  6. Distinctive:

    Run the command. Read the output.

    line 82
  7. Distinctive:

    Use this skill when the task directly matches the workflow described above.

    line 88
  8. Distinctive:

    Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

    line 92

“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

Verification Before Completion

Use when about to claim work is complete, fixed, or passing.

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you haven't run the verification command in this message, you cannot claim it passes.

The Gate Function

Before claiming any status or completion:

  1. IDENTIFY - What command proves this claim?
  2. RUN - Execute the FULL command (fresh, complete)
  3. READ - Full output, check exit code, count failures
  4. VERIFY - Does output confirm the claim?
    • If NO: State actual status with evidence
    • If YES: State claim WITH evidence
  5. ONLY THEN - Make the claim

Skip any step = lying, not verifying.

What Requires Verification

ClaimRequiresNot Sufficient
Tests passTest command output: 0 failuresPrevious run, "should pass"
Linter cleanLinter output: 0 errorsPartial check
Build succeedsBuild command: exit 0Linter passing
Bug fixedTest original symptom: passesCode changed
Phase completeAll objectives verifiedTests passing
Task doneChecklist items verified"I did everything"

Red Flags - STOP

  • Using "should", "probably", "seems to"
  • Expressing satisfaction before verification ("Great!", "Done!")
  • About to commit/push without verification
  • Relying on partial verification
  • ANY wording implying success without having run verification

Patterns

Tests:

OK: [Run test] [See: 34/34 pass] "All tests pass"
BAD: "Should pass now"

Build:

OK: [Run build] [See: exit 0] "Build passes"
BAD: "Linter passed" (linter != compiler)

Task completion:

OK: Re-read requirements -> checklist -> verify each -> report
BAD: "Tests pass, task complete"

Common Rationalizations

ExcuseReality
"Should work now"Run the verification
"I'm confident"Confidence != evidence
"Just this once"No exceptions
"Partial check is enough"Partial proves nothing

The Bottom Line

Run the command. Read the output. Then claim the result.

No shortcuts. Non-negotiable.

When to Use

Use this skill when the task directly matches the workflow described above.

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

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