fable-judge

Verifies completed work by re-running claimed checks and diffing actual changes against reports.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill fable-judge-ismaelsoilet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fable-judge
Source: https://github.com/ismaelsoilet/ismaelsoilet-landing/tree/main/.agents/skills/fable-judge
Command: npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill fable-judge-ismaelsoilet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents frequently claim success regardless of reality: tests quietly weakened until they pass, partial results reported as complete, or scope silently expanded. This Skill treats every completion report as a set of claims to be proven, not trusted, and independently verifies the work against ground truth. ## Core Features & Use Cases - Claim-by-claim verification: Extracts every claim from a report ("tests pass", "build green"), re-runs each verification itself, and labels anything that cannot be re-run as UNVERIFIABLE. - Fraud detection: Hunts the classic failure modes in order of frequency: weakened tests, false completion, scope creep, unauthorized outward actions (deploys, pushes), spec betrayal, and leftover debris. - Evidence-first verdicts: Delivers VERIFIED, VERIFIED WITH CAVEATS, or REFUTED with a claims table showing exactly what was observed, plus the smallest fix for any refuted claim. - Use Case: After an agent reports "fixed the bug, all tests pass", run the judge to diff the actual changes, re-run the test suite, inspect whether assertions were loosened, and receive a verdict backed by captured output rather than the agent's word. ## Quick Start Ask the AI to judge the most recent completed work in this conversation and verify every claim against the actual diff and test output.

Frequently Asked Questions about fable-judge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify that an AI coding agent actually finished the work?▼

Run the judge on the agent's report. It lists every claim, diffs what actually changed via git, re-runs the claimed tests and builds itself, and returns a VERIFIED or REFUTED verdict with the captured output as evidence.

How to detect when an agent weakened tests to make them pass?▼

The judge diffs test files specifically, flagging loosened assertions, changed expected values, skipped tests, widened tolerances, and mocks replacing real calls. A changed test is treated as guilty unless its justification traces back to a spec.

Can work be verified without git in the environment?▼

Yes, but with limitations. Without git operations the judge cannot diff against a pristine reference, so it notes this constraint and verifies by re-reading files and re-running checks instead of comparing change sets.

What happens when a claimed verification cannot be re-run?▼

Any claim that cannot be reproduced due to missing environment, credentials, or human-only checks is labeled UNVERIFIABLE rather than assumed true. The final verdict lists exactly what could not be re-run as caveats.

Does the judge fix the problems it finds?▼

No. Judging is read-and-run only and changes nothing. It names the refuted claim, shows the contradicting output, and states the smallest fix, but fixes happen only if the user asks afterward.