메뉴
Keep the computer awake for a set duration or while a command runs, using `caffeinate` on macOS. Use when the user wants to prevent sleep during a long-running task, download, or presentation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | caffeinate |
| description | Keep the computer awake for a set duration or while a command runs, using `caffeinate` on macOS. Use when the user wants to prevent sleep during a long-running task, download, or presentation. |
Prevent the machine from going to sleep. On macOS this wraps the
built-in caffeinate command; on Linux it falls back to
systemd-inhibit (or a sleep loop if neither is available).
For anything trivial that finishes on its own quickly, there's no need to bother.
The relevant flags:
-d prevent the display from sleeping-i prevent the system from idle sleeping-m prevent the disk from idle sleeping-s prevent sleep while on AC power-u declare the user is active (asserts for -t seconds)-t <seconds> assert for a fixed duration, then exit-w <pid> wait for a process to finish, then stop assertingKeep the system (and display) awake for one hour, then let it sleep:
caffeinate -dimsu -t 3600
Run it in the background so the shell stays free:
caffeinate -dimsu -t 3600 &
caffeinate keeps the assertion until the wrapped command exits:
caffeinate -dimsu ./long-build.sh
Wait on a PID that's already running:
caffeinate -dimsu -w 12345 &
If launched in the background, note the PID it prints (or use
jobs -l) and kill it:
kill %1 # by job number
kill <pid> # by PID
A -t invocation also stops on its own once the timer elapses.
macOS caffeinate doesn't exist here. Prefer systemd-inhibit:
# Fixed duration (1 hour)
systemd-inhibit --what=idle:sleep --why="Keep awake" sleep 3600
# For the lifetime of a command
systemd-inhibit --what=idle:sleep --why="Keep awake" ./long-build.sh
If systemd-inhibit isn't available, tools like caffeine,
xdotool, or a simple background sleep loop are options, but they
vary by desktop environment — check what's installed first.
-t with a wrapped command sparingly: -t and a command
argument together will assert for the duration or until the
command exits, whichever the version supports — prefer one or the
other.-u without -t defaults to a short (~5s) assertion, so pair
-u with -t when you want a specific window.& is the usual pattern so the agent can keep
working while the machine stays awake.Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Spin up throwaway service/database stacks for tests, migrations, and ingest without touching the user's real dev stack or live data. Use when a task runs `docker compose`, database migrations, ingest jobs, or any destructive command that could hit a shared or live service. Triggers on "run the migrations", "ingest the data", "spin up the stack", "run the integration tests", or any plan step that starts containers or writes to a database.
Run the `pi` coding agent as a headless subagent (--mode json) inside a visible tmux pane so the user can watch it stream while the agent still captures and verifies its structured output. Use when asked to "run pi in a pane", "let me watch pi work", "run pi where I can see it", or to delegate to pi with a live view. Requires running inside tmux. For a fully headless run with no pane, use use-pi-subagent instead.
Invoke the `pi` coding agent as a non-interactive subagent from the shell — delegate a self-contained coding or analysis task to a fresh pi process and read its structured JSON output. Use when asked to "run pi", "use pi as a subagent", "delegate this to pi", or to orchestrate pi coder/reviewer agents (see prompt.md).
Writes a self-contained handoff document that briefs another agent or person to execute a scoped task without the originating context. Triggers when the user asks to "write a handoff", "hand this off", "brief another agent", "create a delegation doc", or prep work for a sub-agent / worktree agent to pick up. Emits a markdown file following a fixed template.
Produce a self-contained, styled HTML report answering a question about the codebase. Use when the user asks for a report, a written summary, or a shareable write-up of how part of the codebase works. Triggers on 'write a report', 'make me a report', 'generate an HTML report'. Researches the codebase (delegating to a subagent for broad topics), then writes a single styled HTML file that links back to the source with GitHub permalinks.