verification-before-completion SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 8 indexed copies. Same content hash, so the same checks give both the same grade.

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

mdr add chinkan/rustfox/verification-before-completion@git:20260408.ae338c2

Pins git:20260408.ae338c2 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

chinkan/rustfox

Path

.cursor/skills/verification-before-completion/SKILL.md

Versions recorded

1

Latest version

git:20260408.ae338c2, committed Apr 8, 2026

Size

4,201 bytes

Repository stars

11

License

MIT

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.

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

## Overview

Claiming work is complete without verification is dishonesty, not efficiency.

**Core principle:** Evidence before claims, always.

**Violating the letter of this rule is violating the spirit of this rule.**

## 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 expressing satisfaction:

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
```

## Common Failures

| Claim | Requires | Not Sufficient |
|-------|----------|----------------|
| Tests pass | Test command output: 0 failures | Previous run, "should pass" |
| Linter clean | Linter output: 0 errors | Partial check, extrapolation |
| Build succeeds | Build command: exit 0 | Linter passing, logs look good |
…

Read the whole file at its exact version.

How to install

mdr add chinkan/rustfox/verification-before-completion@sha256:ea52d15aabaf72bc

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

Versions

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

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_pbccy2gawy24ts2i
GET https://markdownregistry.com/api/v1/resolve?ref=chinkan/rustfox/verification-before-completion
GET https://markdownregistry.com/api/v1/blob/ea52d15aabaf72bc6b558efe2c126f161b53961090ddcd712000273bfe8c7b6c

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 chinkan/rustfox

Every file in chinkan/rustfox

Other files named verification-before-completion

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