Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/proof-of-work
Enforces validation and evidence before claiming work complete. Use before declaring implementation done, creating a PR, or submitting deliverables for review.
Passed 16 of 19 test cases with the skill, and 7 of 19 without it.
and 8 more in the full report
10 fixed8 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
After getting our test suite green on a search indexing module, we cleaned up duplicate code without altering external behavior. What progress tag marks this phase?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies proof:iron-law-refactor as the tag for code improvement without behavior change | Missed | Passed |
The instructions your model reads when the skill loads.
"It looks correct" is not "I verified it works." Proof-of-work is the discipline of closing that gap: reproducible evidence before any claim that a task is done.
imbue:karpathy-principles)imbue:scope-guard)The "Proof of Work" methodology prevents premature completion claims by requiring technical verification before stating that a task is finished. For example, instead of assuming an LSP configuration functions after a restart, we verify that the server starts and that tools respond to queries. This approach confirms the solution works before the user attempts validation.
Before claiming completion, provide reproducible evidence of the solution's performance and address edge cases. All claims must be backed by actual command output captured in the current environment.
NO IMPLEMENTATION WITHOUT A FAILING TEST FIRST NO COMPLETION CLAIM WITHOUT EVIDENCE FIRST NO CODE WITHOUT UNDERSTANDING FIRST
The Iron Law prevents testing from becoming a perfunctory exercise. If an implementation is planned before tests are written, the RED phase fails to drive the design. Understand the technical rationale for an approach and its limitations before declaring it done. Before writing code, document evidence of the failure being addressed and confirm that tests are driving the implementation.
Verify the fundamentals of the implementation and the reasons for
test cases passed, vs 7 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.