Proof of production lite

Skill Johnny-Martinez/fleet-of-one-free/skills/proof-of-production-lite

Free starter kit for running AI coding agents with proof gates, status badges, and lane discipline. MIT.

Install

npx -y skills add Johnny-Martinez/fleet-of-one-free --skill proof-of-production-lite

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Lightweight proof gate for production-facing changes. Use when an agent is about to call work fixed, done, launched, or verified.

SKILL.md

1.6 KB, as published. Nobody here has run it

Proof of Production Lite

Use this skill when a task affects a real user, public route, payment path, email, background job, integration, or launch workflow.

Rule

"Done" means the affected workflow was exercised in the environment that matters.

If you cannot verify there, say:

Change applied. Verification still missing: <specific proof>.

Proof Checklist

Name the original claim or failure.
Identify the exact environment that matters: local, staging, production, platform dashboard, inbox, payment provider, or public URL.
Run a check that could fail if the change is wrong.
Capture the evidence: command output, URL, screenshot path, log line, row id, receipt id, or test name.
Report the boundary honestly.

Good Proof

Production HTTP response from the affected route.
Real provider readback for a payment, email, or scheduled post.
Database row for the affected account or job.
Screenshot of the exact public page after deploy.
Test that reproduces the original bug input.

Weak Proof

"Build passed."
"Deploy succeeded."
"Dashboard looked fine."
"Another agent said it works."
"I checked a similar happy path."

Output Format

🟢 **DONE**

Claim: checkout receipt email sends after purchase.
Proof: provider readback shows receipt `<id>` delivered to `<test-recipient>` at `<timestamp>`.
Boundary: verified in test mode only; live-mode sale still needs first-sale proof.