Skip to content
Agentmart
Submit a tool

verification-harness

Verify whether a built feature, automation, app, or AI workflow actually works under realistic buyer-facing conditions.

Skill by az9713

IndexedMIT★ 1
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/az9713-verification-harness

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

Verify whether a built feature, automation, app, or AI workflow actually works under realistic buyer-facing conditions.

Use cases: productivity

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

What's inside

Skill name
verification-harness
Description
Verify whether a built feature, automation, app, or AI workflow actually works under realistic buyer-facing conditions.
License
MIT
Instructions
47 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • name: missing

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Verification Harness Skill

Use this after implementation or before claiming a project is complete.

Input/context:

```text
$ARGUMENTS
```

## Mission

Prove whether the artifact works. Do not equate "code exists" with "product works."

## Required procedure

1. Restate the claimed functionality.
2. Identify buyer-visible success criteria.
3. Inspect relevant files and README instructions.
4. Identify available test commands.
5. Run available tests when safe.
6. Launch or execute the app/workflow when feasible.
7. Check edge cases.
8. Check failure behavior.
9. Check logs, error messages, and hidden assumptions.
10. Produce a verification report.

## Verification report format

- **Claimed functionality**
- **Verified functionality**
- **Evidence observed**
- **Failed checks**
- **Unverified assumptions**
- **Required fixes**
- **Demo path**
- **Final verdict**: `WORKING`, `PARTIAL`, or `NOT WORKING`

## Durable output

If working in a repo, create or update:

```text
docs/profit/verification-report.md
```

From az9713/idea-to-capital, MIT.

More from az9713/idea-to-capital

Signals

Stars
1
Forks
0
Open issues
0
Last commit (this folder)
Jun 26, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

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

More from az9713

Cite this page

verification-harness skill. Agent Mart. https://agentmart.dev/skills/az9713-verification-harness (last updated 2026-10-24)