MCP HubMCP Hub
Volver a habilidades

rest

pjt222
Actualizado 2 days ago
3 vistas
17
2
17
Ver en GitHub
Otroaiapi

Acerca de

La habilidad `rest` es una no-acción intencional que produce silencio en lugar de generar resultados, utilizada cuando un sistema funciona correctamente pero con una alta utilización tras un trabajo sostenido. Se diferencia de otras habilidades de autocuidado al detenerse deliberadamente sin análisis o reequilibrio. Los desarrolladores deben aplicarla cuando el impulso de optimizar se vuelve contraproducente y todo mantenimiento parece una actividad innecesaria.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add pjt222/agent-almanac -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternativo
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/rest

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

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.

  1. Release obligation to produce useful output
  2. Release obligation to improve current state
  3. Release obligation to prepare for next
  4. 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.

  1. Don't fill silence w/ reflection
  2. Don't fill stillness w/ planning
  3. Don't turn rest into meditation by observing stillness
  4. 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.

  1. Notice when energy returns naturally — not forced, not summoned, arising
  2. Don't rush return. Field harvested before recovers produces less not more
  3. When readiness arrives, simply begin. No transition ritual, integration step, summary
  4. 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 step
  • meditate — active clearing rest deliberately is not; use meditate when system needs processing, rest when needs stillness
  • heal — assess + repair; rest reveals persistent issues → heal addresses after rest complete
  • intrinsic — motivation renewal; rest restores capacity intrinsic then directs

Repositorio GitHub

pjt222/agent-almanac
Ruta: i18n/caveman-ultra/skills/rest
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

Habilidades relacionadas

llamaguard

Otro

LlamaGuard es el modelo de Meta de 7-8B parámetros para moderar las entradas y salidas de LLM en seis categorías de seguridad como violencia y discurso de odio. Ofrece una precisión del 94-95% y puede implementarse usando vLLM, Hugging Face o Amazon SageMaker. Utiliza esta skill para integrar fácilmente filtrado de contenido y barreras de seguridad en tus aplicaciones de IA.

Ver habilidad

cost-optimization

Otro

Esta Skill de Claude ayuda a los desarrolladores a optimizar los costes en la nube mediante el ajuste de tamaño de recursos, estrategias de etiquetado y análisis de gastos. Proporciona un marco para reducir los gastos en la nube e implementar una gobernanza de costes en AWS, Azure y GCP. Úsala cuando necesites analizar los costes de infraestructura, ajustar el tamaño de los recursos o cumplir con restricciones presupuestarias.

Ver habilidad

quantizing-models-bitsandbytes

Otro

Esta habilidad cuantiza LLMs a precisión de 8 o 4 bits utilizando bitsandbytes, logrando una reducción de memoria del 50-75% con pérdida mínima de precisión. Es ideal para ejecutar modelos más grandes en memoria GPU limitada o para acelerar la inferencia, admitiendo formatos como INT8, NF4 y FP4. La habilidad se integra con HuggingFace Transformers y permite entrenamiento QLoRA y optimizadores de 8 bits.

Ver habilidad

dispatching-parallel-agents

Otro

Esta Skill de Claude despliega múltiples agentes para investigar y solucionar 3 o más problemas independientes de forma concurrente. Está diseñada para escenarios que involucran fallos no relacionados que pueden resolverse sin estado compartido o dependencias. Su capacidad principal es la resolución paralela de problemas, asignando un agente por cada dominio problemático independiente para maximizar la eficiencia.

Ver habilidad