How do I install the Shutdown skill?

Run npx skillmds@latest add zapgun-ai/shutdown in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Shutdown safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Shutdown?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Shutdown free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Shutdown?

zapgun-ai (@zapgun-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Shutdown by zapgun-ai — Agent Skill

Name: Shutdown
Author: zapgun-ai

Shutdown

Shut down the clawback proxy stack. By default stops ONLY the detached proxy started via run_monitor.sh --detach (graceful SIGTERM, then SIGKILL after ~5s) and removes its pidfile, letting the monitor go quiet — interactive `clawback claude` sessions are left running on purpose. Pass --sessions for a full teardown that also SIGTERMs every clawback claude wrapper, listing each before signaling. Use to cleanly stop the proxy, or to tear the whole stack down.

zapgun-ai ce030ed 2 files · 5.0 KB Updated Sep 17, 2026

File contents

clawback shutdown

Run .skills/shutdown/scripts/shutdown.sh from the project root.

.skills/shutdown/scripts/shutdown.sh              # stop the proxy + let the monitor go quiet
.skills/shutdown/scripts/shutdown.sh --sessions   # also SIGTERM clawback claude sessions

Default: proxy + monitor only

With no flags this is identical to run_monitor.sh --stop: it stops the detached proxy via its pidfile (SIGTERM first so it flushes state and closes its logger, escalating to SIGKILL only if it does not exit within ~5s) and removes the pidfile. A foreground --attach follower then prints the synthetic "process exited" line and can be Ctrl-C'd; an agent's Monitor tool simply stops seeing new lines.

Why interactive sessions are left alone by default

Under probe-then-decide, clawback claude sessions ATTACH to an already-listening proxy rather than spawning their own, so stopping the proxy already cuts their upstream. But the session processes — and any unsaved in-flight edit inside Claude Code — are yours to end deliberately, not something this script should kill out from under you. This is the soft-default (stop the proxy) plus an explicit escape knob (--sessions), not a hard teardown.

`--sessions`: full teardown

Adds a pass that sends SIGTERM to every clawback claude wrapper process. It lists each match (pid + full command) before signaling, so nothing dies silently. Specifics:

The match is pgrep -f 'clawback claude', which hits only the wrappers — the bare proxy is node …/bin/clawback.js (no "claude"), and neither this script nor run_monitor.sh contains the phrase.
The spawned claude CLI child is NOT signaled; if it lingers after its wrapper exits, end it yourself.

Options

--log-file PATH / --pid-file PATH are forwarded to run_monitor.sh --stop so a non-default proxy can be targeted. To bring the proxy back, use the restart skill (or run_monitor.sh --detach).

---name: shutdowndescription: Shut down the clawback proxy stack. By default stops ONLY the detached proxy started via run_monitor.sh --detach (graceful SIGTERM, then SIGKILL after ~5s) and removes its pidfile, letting the monitor go quiet — interactive `clawback claude` sessions are left running on purpose. Pass --sessions for a full teardown that also SIGTERMs every clawback claude wrapper, listing each before signaling. Use to cleanly stop the proxy, or to tear the whole stack down.---# clawback shutdownRun `.skills/shutdown/scripts/shutdown.sh` from the project root.```bash.skills/shutdown/scripts/shutdown.sh # stop the proxy + let the monitor go quiet.skills/shutdown/scripts/shutdown.sh --sessions # also SIGTERM clawback claude sessions```## Default: proxy + monitor onlyWith no flags this is identical to `run_monitor.sh --stop`: it stops thedetached proxy via its pidfile (SIGTERM first so it flushes state and closesits logger, escalating to SIGKILL only if it does not exit within ~5s) andremoves the pidfile. A foreground `--attach` follower then prints thesynthetic "process exited" line and can be Ctrl-C'd; an agent's Monitor toolsimply stops seeing new lines.## Why interactive sessions are left alone by defaultUnder probe-then-decide, `clawback claude` sessions ATTACH to analready-listening proxy rather than spawning their own, so stopping the proxyalready cuts their upstream. But the session processes — and any unsavedin-flight edit inside Claude Code — are yours to end deliberately, notsomething this script should kill out from under you. This is thesoft-default (stop the proxy) plus an explicit escape knob (`--sessions`),not a hard teardown.## `--sessions`: full teardownAdds a pass that sends SIGTERM to every `clawback claude` wrapper process. Itlists each match (pid + full command) before signaling, so nothing diessilently. Specifics:- The match is `pgrep -f 'clawback claude'`, which hits only the wrappers — the bare proxy is `node …/bin/clawback.js` (no "claude"), and neither this script nor `run_monitor.sh` contains the phrase.- The spawned `claude` CLI child is NOT signaled; if it lingers after its wrapper exits, end it yourself.## Options`--log-file PATH` / `--pid-file PATH` are forwarded to `run_monitor.sh--stop` so a non-default proxy can be targeted. To bring the proxy back, usethe [restart](../restart/SKILL.md) skill (or `run_monitor.sh --detach`).

Frequently asked questions