← ClaudeAtlas

veri-healthlisted

The periodic inspection: the decay `veri check`'s hard rules cannot catch, swept and filed so two sweeps months apart compare. Use it when the question is the record's condition rather than its content: "how healthy is this project? anything rotting?", "it has been a quarter — sweep the record for decisions whose revisit conditions have arrived and claims nobody ever finished", "tell me what we left behind after three hard weeks". It reports first and triaged — stale documents, arrived revisit conditions, abandoned claims, untested bets, orphans, the age of your stamp queue — then asks only which you want to act on, and files a health-report source with a fixed shape so the next sweep is a comparison, not a fresh impression. It proposes; it repairs nothing. Not for running the stamp queue itself: "what is waiting on me?", "walk me through everything that needs my stamp before we plan the next batch" are veri:approval-session's, which needs you present document by document. Not for "run the test suite", "why i
danielyayla/veri · ★ 0 · Data & Documents · score 64
Install: claude install-skill danielyayla/veri
<!-- generated by `veri skills install` — do not edit; edit the method document instead --> This file is a pointer, not the method. The method is the Veri document **MET-009**, at `veri/methods/health.md`. Before doing anything else, read it: fetch `MET-009` with the `get_document` MCP tool, or open the file. Follow what it says; nothing in this file substitutes for it. This gate cannot run without these MCP tools: `run_check`, `list_documents`, `get_queue`, `get_receipts`, `file_source`. If any is missing from the connected Veri server, stop and say which one — never interview a user and then have nowhere to file the result. Everything filed here is `draft`/`proposed`. Promotion is the user's act (REQ-008).