aii-prove-it

Verifies completed work by re-running checks against source artifacts before reporting done.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/maestroventures/aiintegrator --skill aii-prove-it-maestroventures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aii-prove-it
Source: https://github.com/maestroventures/aiintegrator/tree/main/plugins/aii-blueprint/skills/aii-prove-it
Command: npx skills add https://github.com/maestroventures/aiintegrator --skill aii-prove-it-maestroventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI assistants often report tasks as complete based on their own summary rather than actual verification, leading to false claims about file edits, calculations, data pulls, and integrations. This Skill enforces a verify-before-claiming discipline so every "done" is backed by a real check, not a claim. ## Core Features & Use Cases - Evidence-Based Verification: Runs concrete checks (grep for old/new values, recompute totals, re-count rows, re-open generated files) against the authoritative source before any completion claim. - False-Green Detection: Catches six categories of misleading passes, including wrong replacements, self-signed integration tests, proxy-context runs, and source-reads mistaken for behavior proof. - Self-Healing Loop: Auto-fixes caught failures, re-runs the same check, and escalates to a human with full context after two failed attempts instead of looping silently. - Use Case: After batch-updating a version string across five files, the Skill greps all files for the old value (expecting zero hits) and the new value (expecting one canonical form), then reports the proof before saying done. ## Quick Start Before telling me the task is finished, run the prove-it verification and show me the actual check results.

Frequently Asked Questions about aii-prove-it

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

FAQPage Schema
How do I verify AI-completed file edits before accepting them?

Grep the whole affected file set for the old value to confirm zero stragglers, then grep for the new value to confirm exactly one canonical form survives. A delete-only grep can miss a wrong replacement, so both directions must be checked.

What is the difference between a claim and proof in task verification?

A claim is a statement like "I changed X"; proof is a re-runnable check whose output demonstrates the change. This Skill requires running the actual check—re-read, re-grep, re-run, re-count—and reporting the evidence before declaring done.

Why do self-signed integration tests give false confidence?

A test you sign the way your own code expects always passes and proves nothing about the real provider. Verification requires a real provider event reaching the endpoint, with logs as proof—even a real error like a 401 proves the transport is live.

Can reading a file's source prove a visual asset is correct?

No. Reading text or markup proves the words, not the appearance. Visual assets must be rendered at a real URL and inspected through a rendered-view provider, checking typeface resolution, palette, and spacing against brand tokens.

When should the verification step be skipped?

Skip the formal check for pure conversation, opinions, or a single trivial answer where nothing concrete exists to verify. The moment there is a deliverable or a factual claim about completed work, the check is required.

What happens when a verification check fails repeatedly?

The Skill auto-fixes the specific caught issue and re-runs the same check, capped at about two attempts. If it still fails, it stops and hands the problem to a human with a description of what was tried, never looping silently or falsely reporting done.