snappy-resume

One job: flip a paused agent's status back to running so the 10-min cron tick starts firing for it again.

Usage

/snappy-resume                 # resumes "default"
/snappy-resume content-miner   # resumes the named agent

Steps

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

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

1. Confirm state/agents/<name>.json has status=running.
2. Tell the operator the agent is running again, quote ticks/max_ticks

so they know how much headroom remains.

Why

Paired with /snappy-pause. Keeps the agent file + prompt + tick count intact across the halt.

Eval

Shape-gate:

• state/agents/<name>.json has status=running after invocation.
• state/log/agents.ndjson gained a {action:"resume", id:<name>} row.

Score = 1 if both pass; else 0.

Gotchas

• Idempotent: resuming an already-running agent is a no-op pass.
• If the agent has already hit max_ticks, resuming alone will not

restart ticks - use /snappy-go <name> <prompt> <new_max_ticks> to bump the cap.

Rubric

criteria:
  - name: agent_status_updated
    kind: deterministic
    check: "The 'status' field in 'state/agents/<name>.json' is 'running' after skill execution."
  - name: log_entry_created
    kind: deterministic
    check: "A log entry with 'action:\"resume\"' and 'id:<name>' is present in 'state/log/agents.ndjson' after skill execution."
  - name: correct_tick_headroom_quoted
    kind: judge
    check: "The operator message correctly quotes the 'ticks/max_ticks' value for the agent as per 'state/agents/<name>.json'."

snappy-resume - loader

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

Critical Rules

• Idempotent: resuming an already-running agent is a no-op pass.

Commands

| ui dashboard | state/skills/snappy-resume/resources/ui.openui | |invoke: see state/skills/snappy-resume/SKILL.md Steps section |eval log: state/log/evals.ndjson (skill: "snappy-resume")

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)] snappy-resume: <what was missing>" >> state/log/loader-feedback.log

<!-- kernel-ok: historical attribution for the PID-loader pattern. -->

Self-correcting loader (PID feedback)

This is the rule that makes loaders learn. Ported from snappy-kernel, where it demonstrably worked: the snappy-dom-cartographer skill mapped Skool admin UI once, every later ship-agent inherited the full map for free.

Before you finish, do two things:

1. Fix gaps (P - proportional). MANDATORY. If this loader didn't cover your case - if you had to read another file, run an undocumented command, work around a wrong selector, or discover a quirk - you MUST attempt an Edit to this AGENTS.md before you log.

• Default action: edit this file. Surgical. Add the missing line, table

row, or code example where it belongs. No restructuring.

• Only LOGGED is allowed when: the fix needs >10 lines, spans multiple

files, or requires a structural rewrite. In that case the state/regen/drain.sh queue picks it up asynchronously.

• "I didn't have time" / "it's minor" / "the next agent will figure it out"

are NOT valid reasons. Minor gaps compound - that's the whole point of this loop.

• Concrete example of a valid P-fix: discover agent-browser screenshot

takes path positionally not as --output <path>. One line in a table. Edit it in. Do not just log it.

• The goal: the next agent never has to leave the loader.

2. Log the result.

echo "[$(date -u +%FT%TZ)] snappy-resume: <what was missing or fixed> [FIXED|LOGGED]" >> state/log/loader-feedback.log

• FIXED = you patched this loader inline (P-fix).
• LOGGED = too large for inline; the PostToolUse enqueue + Stop-hook drain

will rewrite the loader from scratch on next session-end.

Do not skip this. Every agent run must leave the system better than it found it. The loader is the setpoint; you are the sensor; the gap is the error signal; closing the gap is the correction.

OpenUI Resource

• Skill-owned OpenUI Lang resource: state/skills/snappy-resume/resources/ui.openui. Read it before rendering or editing this skill's generated component surface.
• Treat this resource as a first-class artifact of the skill, not a generic chat response. Improve it when the skill's user-facing output needs to become richer.
• System resources compose OpenUI primitives and inherit SnappyChat tokens. Use ui_contract: branded in SKILL.md only for deliberate platform or client visuals.