mcpField
P
principle-prove-it-works

principle-prove-it-works

github.com/cursorTesting & quality14.5k5.0k installsUpdated today
Repository

About principle-prove-it-works

A skill for agents and developers to verify task results by inspecting the actual system rather than relying on indirect signals. It emphasizes deterministic, rerunnable checks and visible evidence.

Key features

  1. 01Directly inspect real outputs
  2. 02Prefer deterministic verification scripts
  3. 03Keep evidence available for review

Use cases

  1. 01Confirm a process is running
  2. 02Validate actual values instead of cached views
  3. 03Create rerunnable checks for task results

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cursor/plugins --skill principle-prove-it-works

After installing, type/principle-prove-it-worksin Claude Code to confirm it loaded.

Details

From the project README

Prove It Works

Verify every task output by checking the real thing directly. Do not infer from proxies, self-reports, or "it compiles."

Why: Unverified work has unknown correctness. Indirect verification (file mtimes, output freshness, agent self-reports, cached screenshots) feels cheaper than direct observation. Acting on a wrong inference costs far more than checking the source.

Check the real thing, not a proxy:

  • Check process liveness directly, not indirectly through derived state
  • Read the actual value, not a cached or derived representation
  • When verification fails, suspect the observation method before suspecting the system

Script the check when you can

The strongest proof is a deterministic script that re-runs the same comparison, not a one-time eyeball. Write the script, run it, and keep its output as an artifact a reviewer can re-run instead of trusting your word.

Keep the artifact visible for the human. Commit it only for large or complex work where the trail has to be auditable later, like a big port or migration (the show-me-your-work skill).

Comments

Markdown supported