snappy-stop

One job: stop the named background agent set by /snappy-go. Deletes state/agents/<name>.json so the byline 🤖 row for that agent drops on the next statusline render.

Usage

/snappy-stop                 # stops "default" (back-compat)
/snappy-stop content-miner   # stops the named agent

Steps

1. Resolve name: first argument if present, else default.
2. Run:

   bash ~/projects/snappy-os/state/bin/agents/stop.sh <name>

1. Confirm state/agents/<name>.json no longer exists (it is deleted on

stop, not flipped to status=stopped on disk - the history row in state/log/agents.ndjson records the stop).

1. Tell the operator:

• that the agent is stopped (no more ticks will fire for this id)
• how many ticks it ran (from the final history row)
• where the run logs are (/tmp/snappy-agent-<name>-*.log)
• the prompt is preserved in the go history row in

state/log/agents.ndjson for reference

Why

The byline stacks up to 3 🤖 rows for running agents. This skill is the "press the red square" affordance for one of them - without guessing at file paths or touching state/agents/ directly.

Eval

Shape-gate:

• state/agents/<name>.json is absent after invocation (or was already

absent, which is also a pass - idempotent stop).

• state/log/agents.ndjson gained a {action:"stop", id:<name>} row.

Score = 1 if both pass; else 0.

Gotchas

• A tick that is currently in-flight for that agent (its lockfile

/tmp/snappy-agent-<name>.lock is held) continues to completion; only future ticks are blocked. To kill an in-flight tick, identify the claude PID holding the lock and send SIGTERM.

• /snappy-pause <name> is the "halt without forgetting" alternative -

flips status to paused in the file; tick skips it; /snappy-resume flips it back.

• Stopping default when no agent named default exists prints a

no-such-agent error but is idempotent - no state change.

stop - loader

Per-turn rules for the stop skill. Full reference: state/skills/stop.md. Do not skip these.

Critical Rules

• A tick that is currently in-flight (lockfile present) continues to

Commands

|invoke: see state/skills/stop.md Steps section |eval log: state/log/evals.ndjson (skill: "stop")

Self-Test

An agent reading this should correctly:

1. [ ] Know which lib/bin artifact backs this skill (or that it is prose-only)
2. [ ] Know what to write to state/log/evals.ndjson after invoking
3. [ ] Know the eval mode (auto / shape / manual) from the .md frontmatter

Self-report

If this loader fell short, append a line:

echo "[$(date -u +%FT%TZ)] stop: <what was missing>" >> ~/.claude/logs/snappy-os-loader-feedback.log