truth-audit
Skill2 starsChanged 10 days agoLicence not identifiedView on GitHub
Use when someone needs to know what is really running and what is really broken before anyone fixes it, and wants the answer as a spec a coder or agent can execute. Read-only live probes (processes, ports, scheduled jobs, launchers, imported source trees, git and remote state, content hashes), parallel read-only lanes, coordinator verification, an append-only gated ledger, root-cause classes, then a repair or uplift spec in waves of disjoint balls with red tests and native proofs, or one self-contained prompt for one coder. Trigger words: audit, truth audit, what is really running, is this the same as GitHub, full audit, find the bugs, repair spec, uplift spec, handoff spec, make a plan for codex, live truth, drift, which code is live.
In this repository62 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- absorbSkill
- agent-buildSkill
- architecture-engineerSkill
- backs-build-flowSkill
- backs-pack-syncSkill
- backs-session-rolloverSkill
- blind-evalSkill
- blind-tribunalSkill
- bounded-loopsSkill
- bughuntSkill
- building-with-backsSkill
- cam-iot-inventorySkill
- clean-code-gauntletSkill
- co-healthSkill
- conscientious-objectorSkill
- context-engineerSkill
- context-engineerSkill
- context-engineerSkill
- debugging-engineerSkill
- decision-barSkill
- design-critiqueSkill
- design-tasteSkill
- elite-buildSkill
- fix-shitSkill
- fleet-dispatchSkill
- fleet-ladderSkill
- gpu-dispatchSkill
- gradeSkill
- guided-stepsSkill
- harness-optimizerSkill
- human-calibrationSkill
- human-voiceSkill
- incident-closureSkill
- intent-compilerSkill
- invariant-floorSkill
- karpathySkill
- leap-protocolSkill
- live-researchSkill
- model-fusionSkill
- operator-essenceSkill
- operator-intent-deductionSkill
- operator-intent-deductionSkill
- optimusSkill
- osha-botSkill
- parallel-workSkill
- rea-investigationSkill
- red-firstSkill
- reload-vsc-and-verifySkill
- repair-loopSkill
- repo-mapSkill
- root-cause-firstSkill
- scrub-plugin-pack-literalsSkill
- seam-engineeringSkill
- secure-deliverySkill
- session-handoffSkill
- sniper-testingSkill
- tribunalSkill
- turn-and-burnSkill
- understanding-gatesSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.