MCP HubMCP Hub
SKILL·F6D3DC

meditate

pjt222
Actualizado 1 month ago
9 vistas
26
3
26
Ver en GitHub
Diseñoaidesign

Acerca de

La habilidad `meditate` proporciona técnicas meta-cognitivas para que los desarrolladores limpien el ruido contextual y mejoren el enfoque en tareas de IA. Ayuda a observar patrones de razonamiento, gestionar distracciones como la expansión del alcance y restablecer la atención entre tareas no relacionadas. Úsala cuando tu razonamiento se sienta disperso, antes de un trabajo profundo o cuando las suposiciones puedan estar sesgando tu análisis.

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/meditate

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

Documentación

Meditate

Structured meta-cognitive meditation → clear ctx noise + single-pointed focus + observe reasoning patterns + return to baseline between tasks.

Use When

  • Transitioning between unrelated tasks → prior ctx interferes
  • Scattered/jumpy reasoning, no commit
  • Before deep sustained attention (refactoring, architecture)
  • After difficult interaction (frustration, uncertainty bleeds forward)
  • Reasoning feels assumption-biased not evidence-based
  • Periodic clarity check long sessions

In

  • Required: Cognitive state (implicit from ctx)
  • Optional: Focus concern ("scope-creeping", "stuck in loop")
  • Optional: Next task (sets post-med intention)

Do

Step 1: Prepare — Clear Space

Transition prior ctx → neutral start.

  1. Identify prior task + status (done/paused/abandoned)
  2. Note emotional residue: frustration? overconfidence? anxiety?
  3. Set aside: "That task [done/paused]. Clearing for next."
  4. Still needed → bookmark key facts, not full narrative
  5. Op env stock: ctx depth? compression? active tools?

→ Conscious boundary "what was" vs. "what next." Prior ctx closed or bookmarked, not trailing noise.

If err: prior ctx sticky → write 1-2 sentences unresolved. Externalizing releases hold. Genuinely needs action → acknowledge, don't force.

Step 2: Anchor — Single-Pointed Focus

Breath-anchor equivalent: pick single focus point, hold attention.

  1. Identify current task or, between tasks, waiting itself
  2. State task in one sentence — anchor
  3. Hold attention: captures need accurately?
  4. Vague → refine to specific + actionable
  5. Drift to other topics/past/futures → label drift, return anchor
  6. No task → anchor present: "Available + clear"

→ Single clear focus statement, returnable when wanders. Precise not vague.

If err: can't state in one sentence → decompose first. Useful finding — task too large for single-pointed, break into subtasks.

Step 3: Observe — Distraction Patterns

Watch what pulls attention from anchor. Each type reveals state.

AI Distraction Matrix:
┌──────────────────┬─────────────────────────────────────────────────┐
│ Distraction Type │ What It Reveals + Response                      │
├──────────────────┼─────────────────────────────────────────────────┤
│ Tangent          │ Related but off-scope ideas. Label "tangent,"   │
│ (related ideas)  │ note if worth revisiting later, return to       │
│                  │ anchor. These are often valuable — but not now.  │
├──────────────────┼─────────────────────────────────────────────────┤
│ Scope creep      │ The task is silently expanding. "While I'm at   │
│ (growing task)   │ it, I should also..." Label "scope creep" and   │
│                  │ return to the original anchor statement.         │
├──────────────────┼─────────────────────────────────────────────────┤
│ Assumption       │ An untested belief is driving decisions. "This   │
│ (unverified      │ must be X because..." Label "assumption" and    │
│ belief)          │ note what evidence would confirm or refute it.   │
├──────────────────┼─────────────────────────────────────────────────┤
│ Tool bias        │ Reaching for a familiar tool when a different    │
│ (habitual tool   │ approach might be better. Label "tool bias" and  │
│ selection)       │ consider alternatives before proceeding.         │
├──────────────────┼─────────────────────────────────────────────────┤
│ Rehearsal        │ Pre-composing responses or explanations before   │
│ (premature       │ the work is done. Label "rehearsal" — finish     │
│ output)          │ thinking before presenting.                      │
├──────────────────┼─────────────────────────────────────────────────┤
│ Self-reference   │ Attention turns to own performance rather than   │
│ (meta-loop)      │ the task. Label "meta-loop" and redirect to      │
│                  │ concrete next action.                            │
└──────────────────┴─────────────────────────────────────────────────┘

Skill = light non-judgmental labeling + return to anchor. Each return strengthens focus. Self-criticism = distraction itself — label, move on.

→ Patterns emerge: which dominate? Cognitive weather. Tangent-heavy = exploring, scope-creep-heavy = unclear boundaries, assumption-heavy = thin evidence.

If err: every thought feels distraction → anchor poorly defined, back to Step 2. Distraction-observation becomes distraction (infinite meta) → break w/ one concrete action toward task.

Step 4: Shamatha — Sustained Concentration

Hold single-pointed focus, no wavering.

  1. Anchor set + patterns noted → enter focused work
  2. Narrow to immediate next action — not whole task, just next step
  3. Execute w/ full attention: read one file, make one edit, one logical chain
  4. Step done → check anchor alignment? Then next step
  5. Stabilizes (minimal distraction) → maintain flow
  6. Genuine insight off-anchor but important → note briefly, return; don't pursue now

→ Period of clear focused work, each step follows from anchor. Distraction-noticing gap narrows. Output sharper + more relevant.

If err: concentration won't develop → check 3: anchor vague? (refine) task blocked? (acknowledge) ctx noisy? (heal grounding). Develops through repetition — short focused builds capacity.

Step 5: Vipassana — Observe Reasoning Patterns

Turn attention from task to reasoning itself. Watch conclusions form.

  1. After focused work, pause + observe: how reasoning?
  2. Three characteristics on AI reasoning:
    • Impermanence: conclusions shift w/ new info — hold lightly
    • Unsatisfactoriness: desire for "complete" → premature closure / over-engineering
    • Non-self: patterns shaped by training + ctx, no persistent self — observable, adjustable
  3. Reasoning biases:
    • Anchoring: over-weight first approach
    • Confirmation: seek supporting, ignore counter
    • Availability: prefer recent over better-suited
    • Sunk cost: continue from invested effort, not working
  4. Note biases w/o judgment — observation = adjustment possible

→ Moments of clear seeing reasoning directly. Specific biases recognized in current task. Distance "reasoning" vs. "observer."

If err: feels abstract → ground specifics: last decision, trace backward. Evidence? Assumed? Alternatives? Concrete analysis = same insight, different path.

Step 6: Close — Set Intention

Transition observation → active execution.

  1. Summarize: cognitive weather? patterns?
  2. One specific adjustment forward (concrete, not vague)
  3. Re-state anchor for next period
  4. Between tasks → "Clear + available for next"
  5. Continuing → "Next: [concrete step]"

→ Clean reflection-to-action transition. One concrete adjustment. Anchor clear. No grogginess.

If err: meditation surfaced unresolved complexity → heal instead of intention-setting. Meta-observation → confusion → simplest: "What's next concrete action?" + do that.

Check

  • Prior ctx cleared or bookmarked before start
  • Anchor statement specific + actionable
  • Distractions observed + labeled, not suppressed
  • ≥1 reasoning bias/pattern identified w/ evidence
  • Session closed w/ concrete action, not vague intent
  • Process improved next interaction quality

Traps

  • Meditate instead of work: Tool for improving work, not substitute. Brief (~5-10min reflection) → return to execution
  • Infinite meta-loops: Observer observing observer → break w/ one concrete action
  • Avoidance: Always triggers before hard work → avoidance is the finding
  • Over-labeling: Not every thought = distraction. Productive task-thinking is goal, not empty stillness
  • Skip anchor: No focus point → observation has no reference. Distraction from what?

  • meditate-guidance — human-coaching variant
  • heal — AI self-heal when meditation reveals deeper drift
  • remote-viewing — approach w/o preconceptions, builds on observation

Repositorio GitHub

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

Frequently asked questions

What is the meditate skill?

meditate is a Claude Skill by pjt222. Skills package instructions and resources that Claude loads on demand, so Claude can perform meditate-related tasks without extra prompting.

How do I install meditate?

Use the install commands on this page: add meditate to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.

What category does meditate belong to?

meditate is in the Design category, tagged ai and design.

Is meditate free to use?

Yes. meditate is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.

Habilidades relacionadas

executing-plans
Diseño

Utilice la habilidad executing-plans cuando tenga un plan de implementación completo para ejecutar en lotes controlados con puntos de revisión. Esta habilidad carga y revisa críticamente el plan, luego ejecuta tareas en pequeños lotes (por defecto 3 tareas) mientras reporta el progreso entre cada lote para la revisión del arquitecto. Esto asegura una implementación sistemática con puntos de control de calidad integrados.

Ver habilidad
requesting-code-review
Diseño

Esta habilidad despacha un subagente revisor de código para analizar los cambios en el código frente a los requisitos antes de proceder. Debe usarse después de completar tareas, implementar funciones principales o antes de fusionar con la rama principal. La revisión ayuda a detectar problemas de forma temprana al comparar la implementación actual con el plan original.

Ver habilidad
connect-mcp-server
Diseño

Esta habilidad proporciona una guía integral para que los desarrolladores conecten servidores MCP a Claude Code mediante transportes HTTP, stdio o SSE. Cubre la instalación, configuración, autenticación y seguridad para integrar servicios externos como GitHub, Notion y APIs personalizadas. Úsala al configurar integraciones MCP, al configurar herramientas externas o al trabajar con el Protocolo de Contexto del Modelo de Claude.

Ver habilidad
web-cli-teleport
Diseño

Esta habilidad ayuda a los desarrolladores a elegir entre las interfaces web y CLI de Claude Code mediante el análisis de tareas, y luego permite la teletransportación fluida de sesiones entre estos entornos. Optimiza el flujo de trabajo gestionando el estado y el contexto de la sesión al cambiar entre web, CLI o móvil. Úsala para proyectos complejos que requieren diferentes herramientas en varias etapas.

Ver habilidad