Write a resume-ready capsule of the current session (objective, what it is waiting on, the next concrete action) so a /clear or an auto-compact can pick up exactly where this left off. Write it before compaction; nothing writes one for you at that point. Use for a checkpoint before risky work, before /clear, or when a thread ships.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
The whole job: reconcile, write the capsule, confirm it, then stop.
A capsule is a small markdown file with YAML frontmatter. A fresh session reads three fields from it and continues. It is state for the next session, not a transcript of this one.
Reconcile from live state. Look at what is actually true now: git status, git log -n 5, the files you changed, any task list. Budget: 2 to 4 reads. Record what happened, not what was said. A capsule that restates the conversation instead of the repo state is the failure this skill exists to prevent.
Write it with the helper, which stamps the date, validates the fields and writes into the configured capsule directory:
node "${CLAUDE_PLUGIN_ROOT}/scripts/capsule-lib.mjs" write \
--objective "<what this work is for, one sentence>" \
--waiting-on "<concrete items, owners, gates a fresh session must know>" \
--next-action "<the one next step, specific enough to act on cold>" \
--slug "<short-topic>" \
--dir '${user_config.capsuleDir}'
Run it from the project directory (do not cd elsewhere) and keep the --dir line exactly as written, single quotes included (they stop the shell expanding the placeholder when the option is unset). A configured path that itself contains a single quote is not supported. It carries the configured capsule directory. If the directory option is not set, that value is empty or still reads ${user_config.capsuleDir} literally; then drop the --dir line and the helper uses the project default.
Optional: --body-file <path> with your own body sections (see Format).
Confirm. The helper prints the path it wrote. Run node "${CLAUDE_PLUGIN_ROOT}/scripts/capsule-lib.mjs" validate <that path> and expect VALID. If it prints INVALID, fix the fields and write again.
Stop. Tell the user the capsule path in one line. If they asked for /refresh, tell them to run /clear next.
objective, waiting_on, next_valid_action are required and must be non-empty. waiting_on is the resume contract: write it so a fresh session can act from it alone.next_valid_action must be a real action, not "resume the session" or "re-read the state". The helper refuses ceremony text.Frontmatter fields: id, parent_capsule_id, status: active, objective, waiting_on, resume_trigger, expires, trigger, next_valid_action, success_criteria, tags, created_at (ISO-8601 with offset), resolved_at. Body sections: Done (don't redo), Historical-Errors -> Resolutions, Historical-Rejected-Approaches, Files-Read / Files-Modified, Operating-Facts, Pending-Gates, Claimed-Rows. The format is compatible with the full aigent-os install.
active then resumed (set automatically by the SessionStart hook when a /clear loads it) then done. Never edit status by hand. Capsules older than 14 days (plugin option maxAgeDays, or the CONTEXT_CAPSULE_MAX_AGE_DAYS env var, to change) are refused at resume with a message, not loaded.
Mid-thought (finish the thought first), or a trivial session a fresh start can rebuild from the repo.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Track and surface sub-agent dispatch calibration ratios. Extract from JSONL transcript or read existing ledger. Per-agent clean/blocked/errored/partial trends.
The English summary is being prepared. Showing the original description.
Compose the AIgent's body state by reading existing signals. Lazy compute. Never polled. Reports the five pressures + recommended reflex.
The English summary is being prepared. Showing the original description.
Generate a structured delegation brief for any task
The English summary is being prepared. Showing the original description.
Quarterly skill that walks the skill-index against the actual SKILL.md files on disk, reports drift (skills indexed that no longer exist, skills on disk that aren't enrolled, skills whose descriptions have changed since enrollment). Hardens the auto-enrollment pipeline against silent rot.
The English summary is being prepared. Showing the original description.
When a [CADDY] hint fires and the principal is confused why, /caddy-explain walks the scoring transparently — which trigger matched, what points it earned, what the threshold was, what other skills were close. Pairs with the legibility thesis. Caddy's decisions should be inspectable on demand.
The English summary is being prepared. Showing the original description.
Enroll a skill into Caddy's index so it can be surfaced when the right prompt arrives. Use when a new skill is created, copied in, or when a skill needs updated triggers. Usage — "/caddy-enroll <path to SKILL.md>".
The English summary is being prepared. Showing the original description.