Quality

/never-fabricate

MANDATORY before reporting on any file contents, test results, agent outputs, or audit findings. If you haven't Read() it, you don't know what's in it. Period. Use when summarizing results, reporting on agent work, or claiming anything is "green" or "complete."

$ golems-cli skills install never-fabricate
Good
100% best pass rate
9 assertions
3 evals
fixtures

Updated 2 weeks ago

If you haven't Read() the file, you don't know what's in it. Period.

The Iron Law

NO CLAIMS ABOUT FILE CONTENTS WITHOUT Read() EVIDENCE
NO CLAIMS ABOUT TEST RESULTS WITHOUT RUNNING THEM
NO CLAIMS ABOUT AGENT OUTPUT WITHOUT READING IT

What Counts as Fabrication

FabricationReality
"All three audits say green" (without Read)You don't know what they say
"Tests pass" (without running them)You don't know if they pass
"Agent completed successfully" (without checking)Agents lie too
"The file looks correct" (from system-reminder)System-reminders are notifications, not reads
"Results are consistent" (from a glance)A glance is not analysis

The Rule

When someone writes to a file (agent, CLI tool, Cursor, user):

1. READ the file with the Read tool
2. PARSE the actual content — don't skim
3. SUMMARIZE what you actually read
4. ONLY THEN report on it

When tests run:

1. RUN the test command
2. READ the full output
3. COUNT failures, errors, warnings
4. ONLY THEN claim pass/fail

When an agent reports completion:

1. CHECK the actual output (file diff, test results, PR URL)
2. VERIFY independently — don't trust the agent's self-report
3. ONLY THEN confirm completion