Methodology

Same brief, same model. Published either way.

A proof shows what a skill changes when Claude does the same job with it and without it. These are the rules every proof follows, including the ones authors pay for.

The rules

Five rules, no exceptions.

We write the brief

The brief is written from the skill's own SKILL.md, so it tests what the skill says it does, and then it is fixed. Authors can suggest a task, but they cannot write or edit the brief. It is shown on every proof page so anyone can repeat the run.

Three runs on each side

Claude builds the brief three times without the skill and three times with it, on the same model and settings. All six results are published, so you see the spread and not one lucky draw. Outputs are never edited.

The exact version is recorded

Every proof records the skill's repository, the exact commit it ran against and the date. If the skill changes later, the proof still describes the version it tested.

Paying buys the run, not the result

Authors can pay to have a skill proven. Those proofs are marked Author-proven. A paid proof is published whatever it shows, under the same rules as every other proof, and an unflattering result is not refunded. We refund only when a proof cannot be completed for a technical reason.

Badges expire after 12 months

The README badge links to the proof. Twelve months after the proof date it changes to Re-run due, until the skill is proven again on a current commit.

What a proof is not

Evidence, not a guarantee.

A proof is one brief on one model. It shows how a skill changed that result, not that it will do the same for your task. It also says nothing about safety; that is the separate safety scan, which checks each skill folder for specific patterns on a specific date.

Think a proof is wrong, or want a skill re-run on a newer commit? Write to hello@usethisskill.com.