Principle Prove It Works

by cursorccb5507cec15No license10K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'

Instructions onlyAI & Agents
AI-generated overview

Guides an agent to verify completed work against the real artifact instead of proxies or self-reports.

What it does
This skill provides instructions for verifying a task's output by inspecting the actual artifact directly, such as running the feature, reading the real value, or examining the diff. It warns against indirect evidence like file timestamps, cached representations, or agent self-reports. It also recommends writing a deterministic script that repeats the same comparison and keeping its output as a re-runnable artifact for a reviewer.
When to use it
Use it after finishing a task and before declaring the work done. It fits situations where correctness must be confirmed against the real system rather than assumed from compilation or indirect signals.
Requirements
No scripts or tools are required; it is an instructions-only skill. It assumes the agent can run checks and inspect artifacts in its environment.

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).

Source and attribution

Source:cursor/pluginsinpstack/skills/principle-prove-it-worksat commitccb5507

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal