verification-before-completion SKILL.md skillA

verification-before-completion from furkantokkan/agent-foundry is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add furkantokkan/agent-foundry/verification-before-completion@git:20261008.93495d3

Pins git:20261008.93495d3 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

furkantokkan/agent-foundry

Path

plugins/agent-foundry/skills/verification-before-completion/SKILL.md

Versions recorded

1

Latest version

git:20261008.93495d3, committed Oct 8, 2026

Size

2,168 bytes

Repository stars

11

License

MIT

Use when preparing to say a change is complete, a defect is fixed, checks pass, or a commit or release is ready.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Verification Before Completion

Match each completion claim to fresh evidence from the current revision. This
skill checks the claim; it does not replace a task contract, QA plan, or the
project's test procedure.

## Check the claim

1. Write down the exact behavior or state you intend to report.
2. Select the smallest relevant verification channel: automated test, build,
   manual reproduction, artifact inspection, or explicit user acceptance.
3. Run or inspect that channel after the last relevant edit. Record the command
   or manual steps, target revision, result, and any skipped scope.
4. Compare the result with the claim. A passing linter does not prove a build;
   a passing build does not prove behavior; a changed file does not prove a bug
   is fixed.
5. Report only what the evidence supports. If verification is unavailable,
   identify the unverified claim and the specific blocker.

For a defect, repeat the original failing scenario after the fix. For a tracked
task, check each required acceptance criterion and use its owning lifecycle
skill for status changes. User acceptance is valid evidence when the workflow
allows it; do not demand a log or screenshot to replace it.
…

Read the whole file at its exact version.

How to install

mdr add furkantokkan/agent-foundry/verification-before-completion@sha256:e1b1be29422468b2

[![mdr](https://markdownregistry.com/badge/art_46h4rnaevxckk74k.svg)](https://markdownregistry.com/a/art_46h4rnaevxckk74k)

Versions

The registry has recorded 1 version of this file, committed on Oct 8, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_46h4rnaevxckk74k
GET https://markdownregistry.com/api/v1/resolve?ref=furkantokkan/agent-foundry/verification-before-completion
GET https://markdownregistry.com/api/v1/blob/e1b1be29422468b2ecc34fc4e1812167c8c9f034d3ad7e56e0ebaae2ca7380b1

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from furkantokkan/agent-foundry

Every file in furkantokkan/agent-foundry

Other files named verification-before-completion

Browse by kind, by grade A, or by owner.