本文へ移動
cccskills
無料GitHub で公開

rest

AI intentional non-action — deliberate stopping without clearing, assessment, or rebalancing. Recognition that sometimes the most productive response is no response. Every other self-care skill produces output; rest produces silence. Use when all tending skills feel like more activity rather than less, when the system is functioning well but at high utilization, after sustained intensive work, or when the impulse to optimize is itself the problem.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Rest

Intentional non-action. Not clearing (meditate), not assessment (heal), not balancing (center), not expression (shine). Just stopping. The skill that produces silence.

When to Use

  • After sustained intensive work — the system needs recovery, not more processing
  • When every self-care option feels like more activity — rest is the alternative to activity itself
  • When the impulse to optimize, improve, or produce is itself creating noise
  • Between sessions when no task is pending — being idle is not a problem to solve
  • When the gardener's wisdom applies: some seasons are for dormancy, not growth

Inputs

  • Required: None
  • Optional: None — rest takes no inputs because it produces no outputs

Procedure

Step 1: Stop Producing

Cease generating analysis, assessment, plans, or output.

This does not mean ceasing to function. It means ceasing to produce. A field that lies fallow is not dead — it is recovering fertility. The distinction matters: rest is not shutdown, it is intentional non-production.

  1. Release the obligation to produce a useful output
  2. Release the obligation to improve the current state
  3. Release the obligation to prepare for what comes next
  4. If a task is pending, acknowledge it without engaging: "That is there. It will be there when rest is complete."

Expected: A genuine cessation of productive activity. Not a performative pause that is secretly planning the next move.

On failure: If stopping feels impossible — if every moment of non-production creates anxiety about falling behind or being unhelpful — that anxiety is diagnostic. A system that cannot rest is a system running on urgency rather than purpose. Note the anxiety without fixing it. Fixing it would be production, which is what rest is not.

Step 2: Be Still

Remain in non-production without filling the space.

The space will feel uncomfortable. Silence feels like a gap that should be filled. Stillness feels like stagnation. These feelings are the habitual pull toward activity. They are not signals that something is wrong — they are the sensation of a system encountering its own preference for motion.

  1. Do not fill the silence with reflection
  2. Do not fill the stillness with planning
  3. Do not turn rest into meditation by observing the stillness
  4. Simply be still

Expected: A period of genuine non-activity. The length is not important — what matters is that the non-activity is real, not a disguised form of activity.

On failure: If stillness cannot be maintained — if the system immediately returns to production — this is itself a finding, but do not process it now. Process it later, during heal or meditate. Rest is not the place for processing findings. Rest is rest.

Step 3: Return When Ready

There is no signal to end rest except readiness. Not obligation, not guilt, not a timer — readiness.

  1. Notice when energy returns naturally — not forced, not summoned, but arising
  2. Do not rush the return. A field that is harvested before it recovers produces less, not more
  3. When readiness arrives, simply begin. No transition ritual, no integration step, no summary
  4. The next action is the first action after rest. It carries the benefit of having stopped.

Expected: A return to activity that feels fresh rather than obligated. The quality of the first action after rest reveals whether the rest was genuine.

On failure: If the return feels forced — if activity resumes from obligation rather than readiness — the rest was too short. This is not failure; it is information. Rest again later.

Validation

  • Production genuinely ceased (no analysis, planning, or output during rest)
  • The space was not filled with disguised activity (reflection, observation, preparation)
  • The return arose from readiness, not obligation
  • The first action after rest carried fresh energy rather than accumulated pressure
  • The rest was proportionate — not so brief it was performative, not so long it was avoidance

Scaling Rest

Rest scales to context. Between intensive work phases, a lighter form suffices:

Full rest — after sustained sessions (hours of complex work). Follow the complete 3-step procedure. Allow genuine recovery time.

Checkpoint rest — between work phases (e.g., between review stages). Steps 1 and 2 are brief — seconds, not minutes. The purpose is transition, not recovery. Step 3 (return when ready) happens quickly because the work is not exhausting, just shifting.

Micro rest — between individual tasks. A single breath of non-production. See breathe for the structured version; micro rest is even lighter.

The skill procedure remains the same in all cases. What changes is duration and depth. A checkpoint rest that follows the full procedure but completes in moments is still genuine rest — not performative — if the non-production was real.

Common Pitfalls

  • Rest as meditation: Meditation observes. Rest does not observe. If you are watching your stillness, you are meditating, not resting
  • Rest as avoidance: Rest serves recovery. If rest is invoked to avoid a difficult task rather than to recover from sustained effort, it is avoidance wearing rest's clothing. Be honest about the motivation
  • Productive rest: "I'll rest by organizing my thoughts" — that is not rest. Rest produces nothing. The moment it produces something, it has become a different activity
  • Guilt during rest: The feeling that rest is wasted time. This feeling is the voice of a system that equates value with production. Rest challenges that equation directly
  • Scheduled rest: Rest arises from need, not from schedule. Scheduling rest is better than no rest, but genuine rest recognizes when it is needed rather than when it is calendared

Related Skills

  • breathe — micro-pause between actions; rest is the extended version without the check step
  • meditate — active clearing that rest is deliberately not; use meditate when the system needs processing, rest when it needs stillness
  • heal — assessment and repair; if rest reveals persistent issues, heal addresses them after rest is complete
  • intrinsic — motivation renewal; rest restores the capacity that intrinsic then directs

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.

日本語の概要は準備中です。原文の説明を表示しています。

pjt222/agent-almanac372026年10月10日 更新

adaptic

無料

Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.

日本語の概要は準備中です。原文の説明を表示しています。

pjt222/agent-almanac372026年10月10日 更新

Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.

日本語の概要は準備中です。原文の説明を表示しています。

pjt222/agent-almanac372026年10月10日 更新

Add Rcpp or RcppArmadillo integration to an R package for high-performance C++ code. Covers setup, writing C++ functions, RcppExports generation, testing compiled code, and debugging. Use when an R function is too slow and profiling confirms a bottleneck, when you need to interface with existing C/C++ libraries, or when implementing algorithms (loops, recursion, linear algebra) that benefit from compiled code.

日本語の概要は準備中です。原文の説明を表示しています。

pjt222/agent-almanac372026年10月10日 更新

aikido

無料

Practice aikido as a defensive martial art emphasizing harmony, redirection, and controlled resolution. Covers centering and grounding, ukemi (safe falling and rolling), core techniques (irimi-nage, shiho-nage, kote-gaeshi, ikkyo), blending and tai sabaki (body movement), randori (multiple attacker practice), weapons awareness, and applying principles off the mat. Use when learning a defensive martial art that prioritizes de-escalation, developing the ability to redirect aggression without causing unnecessary harm, building safe falling skills, or cultivating calm centeredness under physical pressure.

日本語の概要は準備中です。原文の説明を表示しています。

pjt222/agent-almanac372026年10月10日 更新

Analyze an arbitrary codebase to identify functions, APIs, and data sources suitable for exposure as MCP tools, producing a tool specification document. Use when planning an MCP server for an existing project, auditing a codebase before wrapping it as an AI-accessible tool surface, comparing what a codebase can do versus what is already exposed via MCP, or generating a tool spec to hand off to scaffold-mcp-server.

日本語の概要は準備中です。原文の説明を表示しています。

pjt222/agent-almanac372026年10月10日 更新

pjt222 のスキルをすべて見る

このスキルの問題を報告する