rest
について
`rest`スキルは、持続的な作業後の高負荷状態において、システムが正常に機能している場合に出力の代わりに沈黙を生み出す意図的な非アクションです。他のセルフケアスキルとの違いは、分析や再調整を行わずに意図的に停止する点にあります。開発者は、最適化への衝動が逆効果となり、すべての調整作業が不必要な活動に感じられる場合にこのスキルを適用すべきです。
クイックインストール
Claude Code
推奨npx 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/restこのコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします
ドキュメント
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 リポジトリ
関連スキル
llamaguard
その他LlamaGuardは、暴力やヘイトスピーチなど6つの安全性カテゴリーにおいて、LLMの入力と出力をモデレートするMetaの70-80億パラメータモデルです。94〜95%の精度を提供し、vLLM、Hugging Face、Amazon SageMakerを使用してデプロイ可能です。このスキルを使用して、AIアプリケーションにコンテンツフィルタリングと安全策を簡単に統合できます。
cost-optimization
その他このClaudeスキルは、リソースの適正サイジング、タグ付け戦略、支出分析を通じて、開発者がクラウドコストを最適化することを支援します。AWS、Azure、GCPにわたるクラウド支出の削減とコストガバナンスの実施のためのフレームワークを提供します。インフラコストの分析、リソースの適正サイジング、または予算制約への対応が必要な際にご利用ください。
quantizing-models-bitsandbytes
その他このスキルは、bitsandbytesを使用してLLMを8ビットまたは4ビット精度に量子化し、精度の低下を最小限に抑えつつ50〜75%のメモリ削減を実現します。限られたGPUメモリでより大規模なモデルを実行したり、推論を高速化するのに理想的で、INT8、NF4、FP4などのフォーマットをサポートしています。HuggingFace Transformersと統合され、QLoRAトレーニングや8ビットオプティマイザーを可能にします。
dispatching-parallel-agents
その他このClaudeスキルは、複数のエージェントを配備し、3つ以上の独立した問題を並行して調査・修正します。共有状態や依存関係がなく解決可能な、無関係な障害が発生するシナリオ向けに設計されています。中核となる機能は並列問題解決であり、効率を最大化するために独立した問題領域ごとに1つのエージェントを割り当てます。
