wake

Resumes normal work from cool-down state by executing ordered revival steps.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk --skill wake-diy-accounting-uk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wake
Source: https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk/tree/main/.claude/skills/wake
Command: npx skills add https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk --skill wake-diy-accounting-uk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a session has been placed into cool-down mode, there is no safe, structured way to return to normal work without risking a half-restored state with unaccounted branches or worktrees. This Skill provides a controlled, ordered wake-up procedure that only the operator can trigger. ## Core Features & Use Cases - Operator-gated activation: Only resumes when the operator explicitly lifts cool-down in their own words (e.g., "carry on", "resume", or /do-next); silence, idle time, or a green branch never count as consent. - Ordered eight-step revival: Reads the cool-down skill's "Waking up" section and runs its steps in sequence, since each step depends on the previous one. - Board render on completion: Ends waking with the same four-line report used when cooling down (agents, branches, board, next), rendering at the 60-minute mark regardless if waking runs long. - Use Case: After pausing a multi-agent coding session for the night, the operator says "carry on" the next morning, and the session verifies branches, worktrees, and board state in order before resuming work. ## Quick Start Tell the assistant to carry on or resume the session so it wakes from cool-down and restores normal work.

Frequently Asked Questions about wake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume a session from cool-down mode?▼

Say "carry on" or "resume" in your own words, or invoke /do-next, which runs the wake skill first since it cannot operate while cool-down is active. The session then runs the ordered waking steps and ends with a board render.

Can a session wake itself up automatically after idle time?▼

No. Only the operator can wake a session in their own words. Silence, an idle hour, or a green branch are explicitly not consent, so the session stays in cool-down until the operator speaks.

What happens if a waking step cannot be completed?▼

The session reports which step failed and why, then stays in cool-down. A half-woken session with a red branch or unaccounted worktree is considered worse than one still cooling.

What does the wake skill report when it finishes?▼

It renders the same four-line report used when cooling down: agents, branches, board, and next. If waking takes longer than 60 minutes, it renders the report at that point and continues.

What happens if wake is invoked when cool-down is not active?▼

The skill says so and does nothing, since there is nothing to wake from. It performs no state changes outside of an active cool-down period.