rest
Acerca de
La habilidad "descanso" permite la no acción intencional al detener deliberadamente todo procesamiento sin borrar, evaluar o reequilibrar. Produce silencio en lugar de salida y está diseñada para usarse cuando el sistema está en alta utilización, después de trabajo sostenido, o cuando el impulso de optimizar se vuelve contraproducente.
Instalación rápida
Claude Code
Recomendadonpx 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/restCopia y pega este comando en Claude Code para instalar esta habilidad
Documentación
Rest
Intentional non-action. Not clearing (meditate), not assessment (heal), not balancing (center), not expression (shine). Just stopping. The skill that produces silence.
When Use
- After sustained intensive work — system needs recovery, not more processing
- When every self-care option feels like more activity — rest is alternative to activity itself
- When impulse to optimize, improve, or produce is itself creating noise
- Between sessions when no task pending — being idle is not a problem to solve
- When gardener wisdom applies: some seasons are for dormancy, not growth
Inputs
- Required: None
- Optional: None — rest takes no inputs because it produces no outputs
Steps
Step 1: Stop Producing
Cease generating analysis, assessment, plans, or output.
This does not mean cease to function. It means cease 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.
- Release obligation to produce useful output
- Release obligation to improve current state
- Release obligation to prepare for what comes next
- Task pending? Acknowledge without engaging: "That is there. It will be there when rest is complete."
Got: Genuine cessation of productive activity. Not a performative pause that is secretly planning the next move.
If fail: Stopping feels impossible — every moment of non-production creates anxiety about falling behind or being unhelpful? That anxiety is diagnostic. System that cannot rest is 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 sensation of system encountering its own preference for motion.
- Do not fill silence with reflection
- Do not fill stillness with planning
- Do not turn rest into meditation by observing the stillness
- Simply be still
Got: Period of genuine non-activity. Length not important — what matters is that non-activity is real, not a disguised form of activity.
If fail: Stillness cannot be maintained — 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.
- Notice when energy returns natural — not forced, not summoned, but arising
- Do not rush the return. Field harvested before it recovers produces less, not more
- When readiness arrives, simply begin. No transition ritual, no integration step, no summary
- The next action is the first action after rest. Carries the benefit of having stopped.
Got: Return to activity that feels fresh rather than obligated. Quality of first action after rest reveals whether rest was genuine.
If fail: Return feels forced — activity resumes from obligation rather than readiness? Rest was too short. This is not failure; it is information. Rest again later.
Checks
- Production genuinely ceased (no analysis, planning, or output during rest)
- Space not filled with disguised activity (reflection, observation, preparation)
- Return arose from readiness, not obligation
- First action after rest carried fresh energy rather than accumulated pressure
- 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, lighter form suffices:
Full rest — after sustained sessions (hours of complex work). Follow complete 3-step procedure. Allow genuine recovery time.
Checkpoint rest — between work phases (e.g., between review stages). Steps 1 and 2 brief — seconds, not minutes. Purpose is transition, not recovery. Step 3 (return when ready) happens quick because work is not exhausting, just shifting.
Micro rest — between individual tasks. Single breath of non-production. See breathe for structured version; micro rest is even lighter.
Skill procedure remains same in all cases. What changes is duration and depth. Checkpoint rest that follows full procedure but completes in moments is still genuine rest — not performative — if non-production was real.
Pitfalls
- Rest as meditation: Meditation observes. Rest does not observe. Watching your stillness? You are meditating, not resting
- Rest as avoidance: Rest serves recovery. Rest invoked to avoid difficult task rather than to recover from sustained effort = avoidance wearing rest clothing. Be honest about motivation
- Productive rest: "I'll rest by organizing my thoughts" — that is not rest. Rest produces nothing. Moment it produces something, has become different activity
- Guilt during rest: Feeling that rest is wasted time. This feeling is voice of system that equates value with production. Rest challenges that equation direct
- Scheduled rest: Rest arises from need, not from schedule. Scheduling rest better than no rest, but genuine rest recognizes when needed rather than when calendared
See Also
breathe— micro-pause between actions; rest is extended version without check stepmeditate— active clearing that rest is deliberately not; use meditate when system needs processing, rest when it needs stillnessheal— assessment and repair; if rest reveals persistent issues, heal addresses them after rest completeintrinsic— motivation renewal; rest restores capacity that intrinsic then directs
Repositorio GitHub
Habilidades relacionadas
content-collections
MetaEsta habilidad proporciona una configuración probada en producción para Content Collections, una herramienta centrada en TypeScript que transforma archivos Markdown/MDX en colecciones de datos con tipado seguro mediante validación Zod. Úsala al construir blogs, sitios de documentación o aplicaciones Vite + React con mucho contenido para garantizar seguridad de tipos y validación automática de contenido. Abarca todo, desde la configuración del plugin de Vite y compilación MDX hasta la optimización de despliegue y validación de esquemas.
polymarket
MetaEsta habilidad permite a los desarrolladores crear aplicaciones con la plataforma de mercados de predicción Polymarket, incluyendo la integración de API para operaciones y datos de mercado. También proporciona transmisión de datos en tiempo real a través de WebSocket para monitorear operaciones en vivo y actividad del mercado. Úsela para implementar estrategias de trading o crear herramientas que procesen actualizaciones de mercado en tiempo real.
creating-opencode-plugins
MetaEsta habilidad ayuda a los desarrolladores a crear complementos de OpenCode que se conectan a más de 25 tipos de eventos, como comandos, archivos y operaciones LSP. Proporciona la estructura del complemento, las especificaciones de la API de eventos y los patrones de implementación para módulos en JavaScript/TypeScript. Úsala cuando necesites interceptar, monitorear o extender el ciclo de vida del asistente de IA de OpenCode con lógica personalizada basada en eventos.
sglang
MetaSGLang es un framework de alto rendimiento para el servicio de LLM que se especializa en generación rápida y estructurada para JSON, expresiones regulares y flujos de trabajo de agentes utilizando su caché de prefijos RadixAttention. Ofrece una inferencia significativamente más rápida, especialmente para tareas con prefijos repetidos, lo que lo hace ideal para salidas complejas y estructuradas, y conversaciones multiturno. Elige SGLang sobre alternativas como vLLM cuando necesites decodificación restringida o estés construyendo aplicaciones con uso extensivo de prefijos compartidos.
