Skip to content
Get packs

Guide · Agent skill

How to use the STATVS Status Record agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

Statvs is an agent skill for working with STATVS, the append-only record of what happened across LifeOS and the apps it runs. It lets an AI agent check the record's health, confirm whether a system is reporting into it, write rows, answer what happened, and walk a system through migration. This guide explains what the skill does, how to install it, how to phrase requests so it triggers, and what it needs to run.

STATVS Status Recorddanielmiessler/LifeOS · MIT

Quick start

  1. 1Download and unzip. Download the Statvs ZIP from this page and unzip it. Keep the folder name Statvs.
  2. 2Place the skill. Move the Statvs folder into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder.
  3. 3Confirm the engine exists. Check that LIFEOS/STATVS/ contains Statvs.ts, Rewind.ts and streams.ts, and that Bun is installed.
  4. 4Make a request. Ask in plain words that mention STATVS, the record or status logging, such as whether your site reports into it.
  5. 5Read the verdict. Check the per-stream yes, partial or no answer and the evidence the agent cites from the command output.
  6. 6Verify or reconcile. Run verify to confirm row integrity, or reconcile to find missing rows in a time window.

What is an agent skill, and what does Statvs make the agent do?

An agent skill is a folder of instructions and optional scripts that an AI agent loads when a request matches the skill's trigger phrases. Statvs covers STATVS (said "status"), the one record where things that happened are appended once as rows and never rewritten. Other state is a view built from those rows and can be deleted and rebuilt.

When you ask about the record, 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 editing past rows, and that posting notice-worthy events belongs to a separate skill called Vigil.

  • Checks the record's health with the verify command
  • Says whether a system, app or site reports into the record
  • Writes rows, answers what happened, and reads recent rows
  • Rebuilds and drills views, and rewinds and replays past turns
  • Onboards a system through the five-step migration

How do you install the Statvs skill?

Download the Statvs ZIP from this page and unzip it. For a personal install, place the unzipped Statvs folder in ~/.claude/skills/. For a single project, place it in that project's .claude/skills/ folder instead.

If you use the Claude apps, you can upload the skill instead. Open Settings, go to Capabilities, then Skills, and upload the skill there.

  • Personal install: ~/.claude/skills/Statvs
  • Project install: .claude/skills/Statvs inside your project
  • Claude apps: Settings → Capabilities → Skills

What does the skill need before it works?

The skill depends on the LifeOS STATVS engine and cannot answer from the record alone. The engine lives in LIFEOS/STATVS/ and includes Statvs.ts, Rewind.ts and streams.ts. Without it, the commands the skill calls do not exist.

The skill also needs the Bun runtime to run Statvs.ts and Rewind.ts, and Cloudflare access for the cloud record. Cloud reads go through lib/cloudRead.ts unless you pass --local, which reads this machine's local segment files. Those local files are used by some search contracts until they are retired.

  • Bun runtime
  • The LifeOS STATVS engine in LIFEOS/STATVS/
  • Cloudflare access for the cloud record, or --local for local segments
  • Local segment files for the rg-based tool contracts, until retired
bun LIFEOS/STATVS/Statvs.ts verify --json

How do you trigger the skill with a natural request?

You do not need to name a command. Ask in plain words that match the skill's triggers, such as asking whether a site is reporting into status, asking to log a row, or asking what happened. Mention STATVS, the record or status logging so the request is not mistaken for a session-status question.

A bare word like "status" with no mention of logging, a record or a system reporting in is read as session status, which is a different thing.

  • "Is my site reporting into status?"
  • "Log this to status."
  • "Verify the record."
  • "What happened in the last day?"
  • "Onboard the billing app into status."

What are the safety rules and network behaviour?

The skill runs scripts and uses the network. Its default reads go to the Cloudflare cloud record, so expect network calls unless you use --local. Writers refuse secret-shaped values, and tenant content is kept out of the record. Titles should not hold restricted content because titles survive redaction.

The skill will not edit a segment, prune a forever-retained stream, or delete an old store before its view compares equal and the restore drill has passed.

  • Runs scripts: yes
  • Uses network: yes, Cloudflare reads by default
  • Never rewrites past rows
  • Never appends to the event stream with append; use Statvs.ts event so validation runs
  • Secret-shaped values are refused at the writer

What tips help you read the output correctly?

Start with reconcile, not verify, when asking whether things are working. Verify proves that existing rows are intact. Only reconcile finds rows that should exist and do not, such as missed turns or an unshipped backlog. Add --hours 24 to widen the window. Without --emit it only reads.

Read drill loss carefully: a large number mostly counts unclaimed STATE files, which measures migration distance rather than lost data. Treat counters.refused as a running total since the counters file was created, not today's refusals.

  • Use reconcile for "is it working" questions; use verify for integrity
  • Use compare-cloud --days N to check that cloud and local agree
  • Cloud tail widens its window until it returns --n rows
  • Rows from observe streams exist only on the machine that wrote them
  • A view marked unmaterialized compares unequal until rebuild runs once
bun LIFEOS/STATVS/Statvs.ts reconcile --hours 24

What people use it for

  • Checking that a live app sends deploy and app-health rows to the record
  • Auditing whether a site is actually sending deploy and health rows
  • Migrating an app's logging onto STATVS through the five-step dual-write process
  • Looking up what happened for a system over the last day
  • Rebuilding or comparing a view after a change to its data

Frequently asked questions

How do I install the Statvs agent skill?

Download the Statvs ZIP from this page and unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. In the Claude apps you can instead upload it under Settings, Capabilities, Skills.

What do I need to run the Statvs skill?

You need the Bun runtime, the LifeOS STATVS engine in LIFEOS/STATVS/ with Statvs.ts, Rewind.ts and streams.ts, and Cloudflare access for the cloud record. Local segment files are needed for some search contracts until they are retired. The skill cannot answer from the record alone.

Is the Statvs skill free?

The source does not state pricing or licence terms beyond the listed licence, which is MIT. Check the repository's licence file for the full terms.

Is the Statvs skill safe to run?

It runs scripts and uses the network, with cloud reads by default. Its rules forbid rewriting past rows, pruning forever-retained streams and deleting old stores early, and the writer refuses secret-shaped values. Review the scripts before installing if you need to.

Why does Statvs say my site is not reporting in?

A system only counts as reporting in when its rows land in the record under its own writer on registered streams. A system that only writes its own log, or reaches Vigil through an adapter, is not reporting in. The skill checks each required stream, such as deploy and app-health, and reports the gap.

How is Statvs different from Vigil or Cortex?

Statvs is the record of what happened. Vigil reads the record and decides what to tell the principal, and posting notice-worthy events stays Vigil's job. Cortex curates what is worth remembering. Session status, the bare s shortcut, is also separate from STATVS.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use Statvs if you maintain LifeOS or migrate an app's logging onto STATVS and need answers grounded in the record's command output. Pick another tool if you want session status, a slow-performance check, posting notice-worthy events, or memory recall, since those belong to other skills.

Download the skill