MCP HubMCP Hub
Retour aux compétences

meditate

pjt222
Mis à jour Yesterday
5 vues
17
2
17
Voir sur GitHub
Designaidesign

À propos

La compétence `meditate` propose des techniques métacognitives permettant aux développeurs d'éliminer le bruit contextuel et d'améliorer la concentration sur les tâches d'IA. Elle aide à observer les schémas de raisonnement, à gérer les distractions telles que l'élargissement du périmètre, et à réinitialiser l'attention entre des tâches non liées. Utilisez-la lorsque votre raisonnement semble dispersé, avant un travail en profondeur, ou lorsque des hypothèses pourraient biaiser votre analyse.

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

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

Documentation

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

Dépôt GitHub

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

Compétences associées

executing-plans

Design

Utilisez la compétence executing-plans lorsque vous disposez d'un plan de mise en œuvre complet à exécuter par lots contrôlés avec des points de contrôle de revue. Elle charge et examine le plan de manière critique, puis exécute les tâches par petits lots (3 tâches par défaut) tout en rapportant la progression entre chaque lot pour une revue par l'architecte. Cela garantit une mise en œuvre systématique avec des points de contrôle de qualité intégrés.

Voir la compétence

requesting-code-review

Design

Cette compétence délègue un sous-agent réviseur de code pour analyser les modifications apportées au code par rapport aux exigences avant de poursuivre. Elle doit être utilisée après avoir terminé des tâches, implémenté des fonctionnalités majeures, ou avant une fusion vers la branche principale. La revue aide à détecter précocement les problèmes en comparant l'implémentation actuelle avec le plan initial.

Voir la compétence

connect-mcp-server

Design

Cette compétence fournit un guide complet permettant aux développeurs de connecter des serveurs MCP à Claude Code via les transports HTTP, stdio ou SSE. Elle couvre l'installation, la configuration, l'authentification et la sécurité pour intégrer des services externes tels que GitHub, Notion et des API personnalisées. Utilisez-la lors de la configuration d'intégrations MCP, de la configuration d'outils externes ou du travail avec le Protocole de Contexte de Modèle de Claude.

Voir la compétence

web-cli-teleport

Design

Cette compétence aide les développeurs à choisir entre les interfaces Web et CLI de Claude Code en fonction de l'analyse des tâches, puis permet une téléportation transparente des sessions entre ces environnements. Elle optimise le flux de travail en gérant l'état et le contexte de la session lors du passage entre le web, la CLI ou le mobile. Utilisez-la pour des projets complexes nécessitant différents outils à diverses étapes.

Voir la compétence