Lifecycle skills for durable, verifiable, cross-agent repository memory.
This repository also configures its own agents. See what SSOT-SKILL tells them →
Skill Codex
Audit or catch up repository SSOT against commits, conversation sessions, or SSOT protocol versions. Use when the user asks to sync/catch up/audit SSOT, when trackedcommit/trackedsession/trackedskillversion is behind, or when ssot-preflight detects protocol-version lag. Do not use for routine per-change closeout.
Skill Codex
Bootstrap or continue repository SSOT creation. Use when SSOT/ is missing, SSOT/.bootstrap/ exists, SSOT/STATUS.md coverageresult is bootstrap, or the user asks to create a repository SSOT. Do not use for normal code-task preflight or routine closeout in an already bootstrapped repo.
Skill Codex
SSOT closeout before final response, claimdone, or commit after substantive repository changes. Use to absorb code/diff/conversation/test changes into SSOT, resolve in-task SSOT deltas, and decide whether no-op, status updates, audit, or doctor are needed. Do not use for initial task preflight, full historical…
Skill Codex
Verify SSOT health, run deterministic lint checks, perform scoped stop review, CORE-REF startup/reference doc review, ADAPTER checks, CONSUMPTION checks, or coverage/converged validation. Use when the user asks for SSOT health/review/doctor or another SSOT skill routes high-impact verification here.
Skill Codex
Repository SSOT preflight before substantive code, config, docs, review, debugging, refactoring, or planning work. Use to check SSOT/STATUS.md, open adjudications, documentation language, protocol version, minimal SSOT read routing, and in-task SSOT write triggers. Do not use for pure operations, trivial format-only…
Skill Codex
Legacy compatibility shim for the split SSOT Skill bundle. Use only when old prompts or docs explicitly request ssot-skill; route to ssot-preflight, ssot-bootstrap, ssot-closeout, ssot-audit, or ssot-doctor. Do not treat this shim as the protocol owner.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: