Skip to content

STATVS Status Record

Checks, queries and writes LifeOS's append-only status record and onboards systems into it

Stars
19,682
Licence
MIT
Files
8 files

What it does

This skill lets an AI agent work with STATVS, an append-only record of what happened across the LifeOS system and its apps. When you ask whether a system is reporting into the record, to log a row, to see what happened, or to rebuild or migrate a view, the agent runs the STATVS command-line tools and reports answers based on that output rather than guessing. It also knows the rules, such as never rewriting past rows and that some events belong to a separate advocate skill (Vigil).

Great for

  • Developers maintaining LifeOS who need to verify the status record and check which systems report into it
  • Operators migrating an app's logging onto STATVS in the five-step dual-write process
  • Anyone auditing whether a site or app is actually sending deploy and health rows

Skip it if

  • Checking your computer's session status or why something is slow (the 's' shortcut refers to a different thing); the skill is not for that
  • Deciding what to text the principal or posting notice-worthy events, which belongs to Vigil; using this skill for that can bypass validation
  • Installs without the LIFEOS/STATVS engine, since the skill depends on the CLI and cloud record it calls; it cannot answer from the record alone

Try asking

  • “Verify the status record and tell me whether its hash chains are intact”
  • “Is my site reporting into STATVS? Give me a yes, partial or no per required stream”
  • “Show the last rows for the deploy stream and when each writer last reported”
  • “Onboard my billing service into STATVS using the five-step dual-write migration”
Step-by-step guide: how to use STATVS Status RecordInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 8 original files, the MIT licence and an attribution note.

    Statvs.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip Statvs.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip Statvs.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Start health questions with reconcile rather than verify, since verify only proves existing rows are intact and cannot find missing ones
  • Read unclaimed_by_dir and per-view equal flags before treating a large drill loss as a real problem
  • Ask for a named command in the answer so you can check the output yourself

What's inside

  • Intents/Append.md
  • Intents/Coverage.md
  • Intents/Onboard.md
  • Intents/Query.md
  • Intents/Rebuild.md
  • Intents/Rewind.md
  • Intents/Status.md
  • SKILL.md

Redistributed unmodified from danielmiessler/LifeOS under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.