replayable-audit-trail
Skill0 starsChanged 14 days agoNo licenceView on GitHub
Audit trail that can rebuild what it records — one append-only event per write, staged in the same transaction; name-based payloads (codes and names, never ids, no foreign keys) so a restore script replays a wiped record and its children onto reference data reseeded with new ids; deletions that take a required reason and a snapshot of what went; and a Deletion log read back from those events. Use when adding an audit trail, audit log or change history to a backend, recording who did what, making deletes, wipes or reseeds recoverable ("restore the batch from the audit log"), requiring a reason to delete, or building a "what was deleted, by whom and why" page.
In this repository21 other files it gives its agents.
- agent-pipelineSkill
- bilingual-copy-storeSkill
- console-app-shellSkill
- focused-task-flowSkill
- guided-placementSkill
- guided-product-tourSkill
- harvest-skillSkill
- image-to-3d-blenderSkill
- interactive-3d-objectSkill
- keyboard-first-hotkeysSkill
- network-diagramSkill
- r3f-hero-cameraSkill
- r3f-scene-worldSkill
- request-error-loggingSkill
- smart-task-guideSkill
- socketio-realtime-hooksSkill
- system-status-popoverSkill
- threejs-glb-viewerSkill
- threejs-realismSkill
- toast-notification-historySkill
- ui-motion-systemSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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 364,980 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.

