Menu
The day-one first-run flow and the everyday home screen. On first launch, greet, run setup, then carry the operator into a real first win. On return, give a short briefing and action menu.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
The capsule verb, invoked explicitly — reconcile from the live memory, write a resume-ready capsule, then stop. Mid-session checkpoint or completion capsule; a rolling best-effort version of the same write also runs automatically on every Stop event via daemons/stop-capsule-writer.mjs.
The resume verb, invoked explicitly — load the newest valid capsule by created_at, re-ground against live memory, then ACT on waiting_on. Mid-session or on explicit ask; the post-clear boot fires the same procedure automatically via daemons/resume-verb.mjs.
Run the volunteering ledger before declaring work done. Forces surfacing of what changed/didn't, what was noticed-but-not-fixed, what was guessed, and what tradeoffs were made on the principal's behalf. The standard - the principal should never be surprised later by something the agent knew at the time.
Capture a confident agent claim (Phase 1) or resolve one as right/wrong (Phase 2) in vault/memory/TRUST_DECAY.md. Builds the longitudinal record of agent calibration over time. Pairs with /honesty-check (which should reduce Phase 1 frequency) and /diagnose (which surfaces causes that often reveal Phase 2 events).
One evidence-gated pass that sequences /dream, /reconcile, /sweep-now, and /digest over your own vault, with a /system-check gate and a ledger-review pass over the measurement layer (Honesty Ledger, Trust Decay, Failure Modes). Stays exactly as human-gated as the legs it calls -- stages, never auto-applies. Skips a leg gracefully when there is nothing to do; every leg that runs leaves an evidence line.
Dispatch Hestia to run all 3 vault sweeps (DELEGATION_TRACKER stale items, HEAT_INDEX dormant flips, broken wikilinks) and append the result to HESTIA_SWEEP_LOG.
| name | start |
| description | The day-one first-run flow and the everyday home screen. On first launch, greet, run setup, then carry the operator into a real first win. On return, give a short briefing and action menu. |
| trigger | /start |
Use this skill on first launch and whenever the operator asks for the home screen, start menu, or orientation.
The canonical first-run state is .aigent/state.json:
{
"schemaVersion": 1,
"status": "uninitialized | setup-in-progress | ready",
"completedAt": null
}
For compatibility with installations before v0.9, .aigent/first-run-done is also recognized.
status: ready or a legacy first-run marker means returning operator.ready silently.status: setup-in-progress before asking questions, so an interrupted setup can resume.I'm your AIgent operator. Let's get you one real win in the next few minutes.
/operator-setup, one question at a time./first-win and produce a usable artifact.Later sessions pick up on their own via
/resume. When you are done, say "close up" or run/context-capsuleso the work is banked (it also autosaves as you go). Run/statuslineonce in Claude Code to show context usage.
.aigent/state.json to status: ready with an ISO-8601 completedAt value..aigent/first-run-done for backward compatibility.Do not mark setup ready before the durable writes succeed.
memory/about-you.md and recent session memory.Present a short numbered list and accept either the number or a plain-language request:
On first run, lead with zero-dependency actions so the first win never waits on a connector.
status: setup-in-progress indefinitely after a successful setup.