verification-gauntlet

Runs signal-gated verification probes and anti-greenwash checks before completion claims.

3|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/marcmarti9/agentit --skill verification-gauntlet-marcmarti9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-gauntlet
Source: https://github.com/marcmarti9/agentit/tree/main/skills/verification-gauntlet
Command: npx skills add https://github.com/marcmarti9/agentit --skill verification-gauntlet-marcmarti9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents often claim work is done based only on self-written tests passing, which is weak evidence. This Skill surrounds agent work with external, signal-gated verification probes and anti-greenwash rules so done/fixed/shipping claims are backed by receipts and observed evidence. ## Core Features & Use Cases - Layered Verification: Combines the project's native test suite, change-contract red-to-green checks, stack-specific probes from a catalog, anti-greenwash rules, and human gates for high-risk work. - CLI-Driven Probes: The agentit verify command plans probes, runs runnable checks with --apply, and writes a timestamped receipt to .agentit/verify/. - Evidence-Based Checklists: Checklist probes such as acceptance criteria, Postgres RLS discipline, and auth boundaries stay pending until the agent supplies concrete evidence. - Use Case: After implementing an authentication change, run agentit verify "add login endpoint" --apply, fill in the auth-boundary checklist with observed behavior, and cite the receipt path before claiming the feature is done. ## Quick Start Ask the agent to run agentit verify with a short task description and the --apply flag, then cite the receipt before claiming the task is done.

Frequently Asked Questions about verification-gauntlet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify agent-implemented code before claiming it is done?▼

Run `agentit verify "task description" --project .` to plan probes, then add `--apply` to execute runnable checks and write a receipt. Fill pending checklist probes with concrete evidence such as commands, paths, or observed behavior before making any done claim.

What is the difference between verification-gauntlet and test-driven-development?▼

Test-driven development produces the red-to-green cycle for behavior, while the gauntlet checks that you actually observed it and adds external probes. Green self-tests alone are not treated as proof of completion.

When should I not use the verification gauntlet?▼

Skip it for pure explanation tasks with no working-tree claim. It is designed for non-trivial implementations, RISK_2+ work, and any situation where test results look too easy or confidence is low.

Why did my checklist probe stay pending after running agentit verify?▼

Checklist probes remain in `pending_agent_evidence` state until you supply evidence in the close-out. Each item needs a command, file path, or observed behavior; marking pass without evidence violates the anti-greenwash rules.

Does the gauntlet run stack-specific checks like Postgres RLS?▼

Yes, probes from `probes/catalog.yaml` activate only when matching signals are detected, such as postgres/supabase signals triggering the RLS discipline checklist or auth signals triggering the auth-boundary checklist.