MCP HubMCP Hub
Retour aux compétences

rest

pjt222
Mis à jour 2 days ago
6 vues
17
2
17
Voir sur GitHub
Métaaiapi

À propos

La compétence "repos" permet une non-action intentionnelle en arrêtant délibérément tout traitement sans effacement, évaluation ou rééquilibrage. Elle produit du silence plutôt qu'une sortie et est conçue pour être utilisée lorsque le système est à haut taux d'utilisation, après un travail soutenu, ou lorsque l'impulsion d'optimiser devient contre-productive.

Installation rapide

Claude Code

Recommandé
Principal
npx skills add pjt222/agent-almanac -a claude-code
Commande PluginAlternatif
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternatif
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/rest

Copiez et collez cette commande dans Claude Code pour installer cette compétence

Documentation

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.

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

  1. Do not fill silence with reflection
  2. Do not fill stillness with planning
  3. Do not turn rest into meditation by observing the stillness
  4. 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.

  1. Notice when energy returns natural — not forced, not summoned, but arising
  2. Do not rush the return. Field 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. 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 step
  • meditate — active clearing that rest is deliberately not; use meditate when system needs processing, rest when it needs stillness
  • heal — assessment and repair; if rest reveals persistent issues, heal addresses them after rest complete
  • intrinsic — motivation renewal; rest restores capacity that intrinsic then directs

Dépôt GitHub

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

Compétences associées

content-collections

Méta

Cette compétence propose une configuration éprouvée en production pour Content Collections, un outil axé sur TypeScript qui transforme des fichiers Markdown/MDX en collections de données typées de manière sûre avec une validation Zod. Utilisez-la lors de la création de blogs, de sites de documentation ou d'applications Vite + React riches en contenu pour garantir la sécurité de typage et la validation automatique du contenu. Elle couvre tout, de la configuration du plugin Vite et de la compilation MDX à l'optimisation des déploiements et la validation des schémas.

Voir la compétence

polymarket

Méta

Cette compétence permet aux développeurs de créer des applications avec la plateforme de marchés prédictifs Polymarket, incluant l'intégration d'API pour le trading et les données de marché. Elle fournit également une diffusion de données en temps réel via WebSocket pour surveiller les transactions en direct et l'activité du marché. Utilisez-la pour mettre en œuvre des stratégies de trading ou pour créer des outils traitant les mises à jour de marché en direct.

Voir la compétence

creating-opencode-plugins

Méta

Cette compétence aide les développeurs à créer des plugins OpenCode qui s'interconnectent avec plus de 25 types d'événements tels que les commandes, les fichiers et les opérations LSP. Elle fournit la structure du plugin, les spécifications de l'API événementielle et les modèles d'implémentation pour les modules JavaScript/TypeScript. Utilisez-la lorsque vous avez besoin d'intercepter, de surveiller ou d'étendre le cycle de vie de l'assistant IA OpenCode avec une logique personnalisée pilotée par les événements.

Voir la compétence

sglang

Méta

SGLang est un framework de service LLM haute performance spécialisé dans la génération rapide et structurée pour les workflows JSON, regex et agentiques grâce à son cache de préfixe RadixAttention. Il offre une inférence nettement plus rapide, particulièrement pour les tâches avec des préfixes répétés, ce qui le rend idéal pour les sorties complexes et structurées ainsi que les conversations multi-tours. Choisissez SGLang plutôt que des alternatives comme vLLM lorsque vous avez besoin d'un décodage contraint ou que vous construisez des applications avec un partage étendu de préfixes.

Voir la compétence