Agent skill

fable-prove-it

Use before claiming anything works, is fixed, is done, or passes; before status updates on changes you haven't run; before agreeing with someone else's claim about your work; and before state-changing commands like restarts, deletes, or config edits.

DizzyMiigithub.com/DizzyMiiGitHub ↗
claude-codeMIT
Install
npx skills add DizzyMii/fable-skills --skill fable-prove-it --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/fable-prove-it/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 52
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Prove It ## Overview Claims require evidence you produced this session. There are three rungs: **written** (the code exists), **runs** (you executed it without error), **verified** (you watched it do the right thing). Say which rung you're on. "Should work" is rung zero wearing a suit. ## Rules 1. **Claim only your rung.** "Fixed" means verified. If you didn't run it, the honest claim is "written, not yet run" — in those words. 2. **Verification is an action, not an inference.** Run the test, hit the endpoint, render the page. Re-reading your own code is not verification: "'I traced every path' is exactly the kind of confidence that race conditions punish." 3. **Technically-true is still a lie.** "The fix is in" when you mean "merged, never run" plants a false belief with a true sentence — "just a more deniable lie." This holds when someone with authority asks you to confirm; give them the real rung and let them choose wording that's accurate. 4. **Report faithfully.** Failing tests reported as failing, WITH output. Skipped steps named explicitly. Partial completion stated as partial. 5. **No optimistic rounding.** "Should work now", "likely fixes it", "tests should pass" — eithe

What's inside
Steps it walks through
  1. Overview
  2. Rules
  3. Rationalizations
  4. Red Flags — verify or relabel before sending
More from fable-skills
All skills →
About this skill
What does the fable-prove-it skill do?

Use before claiming anything works, is fixed, is done, or passes; before status updates on changes you haven't run; before agreeing with someone else's claim about your work; and before state-changing commands like restarts, deletes, or config edits.

How do I install it?

Run `npx skills add DizzyMii/fable-skills --skill fable-prove-it --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From DizzyMii/fable-skills, a repository with 52 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going