Skip to content
Agentmart
Submit a tool

verification-before-completion

Internal meta skill for verifying work with fresh evidence before claiming success, committing, or pushing.

Skill by tykowale

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/tykowale-verification-before-completion

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Internal meta skill for verifying work with fresh evidence before claiming success, committing, or pushing.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/verification-before-completion

What's inside

Skill name
verification-before-completion
Description
Internal meta skill for verifying work with fresh evidence before claiming success, committing, or pushing.
License
MIT
Instructions
50 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Verification Before Completion

This is an internal meta skill. Humans should not need to reference it directly.

## Core Principle

Evidence before claims.

Do not say work is complete, fixed, or passing unless fresh verification output supports that exact claim.

## Apply Before

- saying something is done
- saying a fix works
- committing
- pushing
- moving to the next task

## Gate

1. Identify the command or check that proves the claim.
2. Run it fresh.
3. Read the actual output.
4. Match the output to the claim.
5. Only then state the result.

## Rules

- Confidence is not evidence.
- Partial verification is not completion.
- Old output is not fresh verification.
- A tool or agent claiming success is not enough on its own.

## Darwin Adaptation

Verification should match the scope of the change.

Examples:

- skill text changes: read the final files and verify structure
- behavioral changes: run the relevant tests
- repo operations: check git status, branch state, and remote state as needed

## Output

Report only what was actually verified.

If verification is incomplete, say exactly what was and was not checked.

From tykowale/darwin, MIT.

More from tykowale/darwin

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Apr 4, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from tykowale

Cite this page

verification-before-completion skill. Agent Mart. https://agentmart.dev/skills/tykowale-verification-before-completion (last updated 2026-10-24)