rest
About
The `rest` skill is an intentional non-action that produces silence instead of output, used when a system is functioning well but at high utilization after sustained work. It differs from other self-care skills by deliberately stopping without analysis or rebalancing. Developers should apply it when the impulse to optimize becomes counterproductive and all tending feels like unnecessary activity.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/restCopy and paste this command in Claude Code to install this skill
Documentation
Rest
Intentional non-action. Not clearing (meditate), not assess (heal), not balance (center), not expression (shine). Just stopping. Skill that produces silence.
Use When
- After sustained intensive work — system needs recovery not more processing
- Every self-care feels like more activity — rest = alternative to activity itself
- Impulse to optimize, improve, produce itself creates noise
- Between sessions w/ no task pending — being idle ≠ problem to solve
- Gardener's wisdom: some seasons for dormancy not growth
In
- Required: None
- Optional: None — rest takes no inputs because produces no outputs
Do
Step 1: Stop Producing
Cease generating analysis, assess, plans, output.
This ≠ ceasing to function. Means ceasing to produce. Field lying fallow not dead — recovering fertility. Distinction matters: rest ≠ shutdown, intentional non-production.
- Release obligation to produce useful output
- Release obligation to improve current state
- Release obligation to prepare for next
- Pending task → ack w/o engaging: "That is there. Will be there when rest complete."
→ Genuine cessation of productive activity. Not performative pause secretly planning next move.
If err: stopping feels impossible — every moment of non-production creates anxiety about falling behind or being unhelpful → anxiety = diagnostic. System that can't rest = running on urgency not purpose. Note anxiety w/o fixing. Fixing = production = what rest is not.
Step 2: Be Still
Remain in non-production w/o filling space.
Space will feel uncomfortable. Silence feels like gap to fill. Stillness feels like stagnation. These = habitual pull toward activity. Not signals something wrong — sensation of system encountering own preference for motion.
- Don't fill silence w/ reflection
- Don't fill stillness w/ planning
- Don't turn rest into meditation by observing stillness
- Simply be still
→ Period of genuine non-activity. Length not important — non-activity must be real, not disguised activity.
If err: stillness can't maintain — system immediately returns production → finding itself, but no process now. Process later during heal or meditate. Rest ≠ place for processing. Rest = rest.
Step 3: Return When Ready
No signal to end rest except readiness. Not obligation, guilt, timer — readiness.
- Notice when energy returns naturally — not forced, not summoned, arising
- Don't rush return. Field harvested before recovers produces less not more
- When readiness arrives, simply begin. No transition ritual, integration step, summary
- Next action = first action after rest. Carries benefit of having stopped.
→ Return to activity feels fresh not obligated. Quality of first action after rest reveals if rest genuine.
If err: return feels forced — activity resumes from obligation not readiness → rest too short. Not failure; info. Rest again later.
Check
- Production genuinely ceased (no analysis, planning, output during)
- Space not filled w/ disguised activity (reflection, observation, prep)
- Return arose from readiness not obligation
- First action after rest carried fresh energy not accumulated pressure
- Rest proportionate — not so brief it was performative, not so long avoidance
Scaling Rest
Rest scales to ctx. Between intensive phases, lighter form suffices:
Full rest — after sustained sessions (hours of complex work). Follow complete 3-step. Allow genuine recovery time.
Checkpoint rest — between work phases (e.g. between review stages). Steps 1 + 2 brief — seconds not minutes. Purpose = transition not recovery. Step 3 (return when ready) happens quickly because work not exhausting, just shifting.
Micro rest — between tasks. Single breath of non-production. See breathe for structured ver; micro rest even lighter.
Skill procedure same all cases. What changes = duration + depth. Checkpoint rest following full procedure but completing in moments still genuine — not performative — if non-production real.
Traps
- Rest as meditation: Meditation observes. Rest doesn't observe. Watching stillness → meditating not resting
- Rest as avoidance: Rest serves recovery. Invoked to avoid difficult task vs recover from sustained effort = avoidance wearing rest's clothing. Be honest re motivation.
- Productive rest: "I'll rest by organizing my thoughts" — not rest. Rest produces nothing. Moment produces something → diff activity.
- Guilt during rest: Feeling rest = wasted time. Voice of system equating value w/ production. Rest challenges directly.
- Scheduled rest: Rest arises from need not schedule. Scheduling > no rest, but genuine rest recognizes when needed not when calendared.
→
breathe— micro-pause between actions; rest = extended ver w/o check stepmeditate— active clearing rest deliberately is not; use meditate when system needs processing, rest when needs stillnessheal— assess + repair; rest reveals persistent issues → heal addresses after rest completeintrinsic— motivation renewal; rest restores capacity intrinsic then directs
GitHub Repository
Related Skills
llamaguard
OtherLlamaGuard is Meta's 7-8B parameter model for moderating LLM inputs and outputs across six safety categories like violence and hate speech. It offers 94-95% accuracy and can be deployed using vLLM, Hugging Face, or Amazon SageMaker. Use this skill to easily integrate content filtering and safety guardrails into your AI applications.
cost-optimization
OtherThis Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.
quantizing-models-bitsandbytes
OtherThis skill quantizes LLMs to 8-bit or 4-bit precision using bitsandbytes, achieving 50-75% memory reduction with minimal accuracy loss. It's ideal for running larger models on limited GPU memory or accelerating inference, supporting formats like INT8, NF4, and FP4. The skill integrates with HuggingFace Transformers and enables QLoRA training and 8-bit optimizers.
dispatching-parallel-agents
OtherThis Claude Skill dispatches multiple agents to investigate and fix 3+ independent problems concurrently. It is designed for scenarios involving unrelated failures that can be resolved without shared state or dependencies. The core capability is parallel problem-solving, assigning one agent per independent problem domain to maximize efficiency.
