Agent skill · software engineering · sickn33
atlas-ledger
Companion to atlas-contract. Auto-invoked by its Final Audit on caught drift; also use after Post Reviews or user requests to record a mistake. Distills drift into WHEN/DON'T/INSTEAD clauses, writes to Atlas.md after confirmation.
Why this skill is useful
Adds executable scripts for distilling project drift into actionable contract clauses that enhance the AI's memory and governance capabilities.
What it needs
Requires python installed locally. About 10k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Atlas Ledger v2.2 Give the Atlas series a memory. Contents 1. Output Language 2. When To Run 3. Distillation (the core) — Steps 1–6 4. Atlas.md format 5. Clause maintenance 6. Integration with atlas-contract 7. Final Principle Quick reference atlas-contract defends the goal within one conversation, but it starts from zero every time — it does not know where this project drifted before. atlas-ledger closes that gap: when a drift is caught, it distills the lesson into a permanent, project-local contract clause and (after the user confirms) writes it to Atlas.md. Next time atlas-contract builds a Goal Contract, it loads the relevant clauses, so the defense line thickens with each catch. That is the compounding effect. It is a low-frequency, lightweight companion. It runs only after a drift is caught, and it stays small on purpose. Do not turn it into a second heavy governance skill — its only hard job is distillation quality. Core idea The job is not to keep a diary. A record of "what went wrong" is a memory; it changes nothing. The job is a translation: turn this caught drift → into a clause that can enter a future contract and trigger a stop. A diary says "I hid the feature." A ledger clause says "WHEN a backend requirement is blocked, DON'T hide the feature, INSTEAD stop and disclose." Only the second one catches it next time. The entire value of this skill is the quality of that translation — and since it is run by the same model that drifted, the mechanisms below exist to keep it honest rather than trusting it to be careful. --- 1. Output Language Write Atlas.md and all user-facing output in the language of the user's current instruction. Machine keys stay in English; clause content is localized. Never translate the keys WHEN / DON'T / INSTEAD, the IDs (L1, O1), seen, severity, Source, RETIRED, or section headers Confirmed Clauses / Provisional Observations — atlas-contract parses these, and translating them makes the read-back unstable. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/atlas-ledger