Statvs
Front door to STATVS (said status), the one append-only record of what happened across...
Install
npx skills add danielmiessler/LifeOS --skill Statvs -g -a claude-code -y- Repository
- danielmiessler/LifeOS19.7k
- Category
- Writing
- Updated
- 8d ago
- License
- MIT
- Context cost
- Mediumabout 1,627 tokens
- Runs scripts
- No, instructions only
What it does
Front door to STATVS (said status), the one append-only record of what happened across LifeOS and every app it runs: checks the record's health, says whether a system, app or site reports into it, writes rows, answers what happened, rebuilds and drills views, rewinds and replays past turns, and onboards a system through the five-step migration. USE WHEN statvs, status logging, status record, the record, is X logging to status, is my site reporting into status, full status logging, log this to status, write a status row, what happened, status tail, verify the record, status counters, drill, restore drill, rebuild a view, compare a view, rewind a turn, replay a miss, onboard X into status, migrate X to statvs, dual-write, register a stream. NOT FOR session status or why is this slow (the s shortcut), posting Vigil events or deciding what to text the principal (Vigil), complaints (Errata), memory recall (Cortex).
Statvs
STATVS (Roman spelling, said "status") is the one record of what happened across LifeOS and every app it runs. Things that happened are appended once as rows and never rewritten; every other piece of state is a view folded from those rows that can be deleted and rebuilt. When the principal says "status logging", "the record" or "is X reporting into status", this skill is what they mean, and every intent here answers from the record and its CLI, never from a system's private log. Shared facts the intents rely on:
