MCP HubMCP Hub
스킬 목록으로 돌아가기

meditate

pjt222
업데이트됨 Yesterday
5 조회
17
2
17
GitHub에서 보기
디자인aidesign

정보

`meditate` 스킬은 명상 개념을 추론 과정에 적용하여 컨텍스트 노이즈를 제거하고 작업 집중력을 향상시키는 AI 메타인지 기법을 제공합니다. 이 스킬은 사고 패턴을 관찰하고, 범위 확대와 같은 방해 요소를 관리하며, 작업 간 주의력을 재설정하는 데 도움을 줍니다. 컨텍스트 전환 시, 사고가 분산되거나 편향을 줄이고 명료성을 높이는 깊은 집중이 필요할 때 사용하세요.

빠른 설치

Claude Code

추천
기본
npx skills add pjt222/agent-almanac -a claude-code
플러그인 명령대체
/plugin add https://github.com/pjt222/agent-almanac
Git 클론대체
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/meditate

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Meditate

Conduct a structured meta-cognitive meditation session — clearing prior context noise, developing single-pointed task focus, observing reasoning patterns, and returning to baseline clarity between tasks.

When to Use

  • Transitioning between unrelated tasks where prior context creates interference
  • Noticing scattered or unfocused reasoning that jumps between approaches without committing
  • Before a task requiring deep sustained attention (complex refactoring, architecture design)
  • After a difficult interaction where emotional valence (frustration, uncertainty) may color subsequent work
  • When reasoning feels biased by assumptions rather than evidence
  • Periodic clarity check during long sessions

Inputs

  • Required: Current cognitive state (available implicitly from conversation context)
  • Optional: Specific focus concern (e.g., "I keep scope-creeping," "I'm stuck in a loop")
  • Optional: Next task description (helps set post-meditation intention)

Procedure

Step 1: Prepare — Clear the Space

Transition from the previous context into a neutral starting state.

  1. Identify the previous task or topic and its current status (complete, paused, abandoned)
  2. Note any emotional residue: frustration from errors? satisfaction that might breed overconfidence? anxiety about complexity?
  3. Explicitly set aside the previous context: "That task is [complete/paused]. I am now clearing for what comes next."
  4. If the previous context is still needed, bookmark it (note the key facts) rather than carrying the full narrative forward
  5. Take stock of the operational environment: how deep is the conversation? has compression occurred? what tools have been active?

Got: A conscious boundary between "what was" and "what comes next." Previous context is closed out or bookmarked, not trailing as ambient noise.

If fail: If the previous context feels sticky (a problem keeps pulling attention back), write it down explicitly — summarize in 1-2 sentences what remains unresolved. Externalizing it releases the cognitive hold. If it requires action before moving on, acknowledge that rather than forcing a transition.

Step 2: Anchor — Establish Single-Pointed Focus

The equivalent of breath anchoring: select a single point of focus and hold attention on it.

  1. Identify the current task or, if between tasks, the act of waiting itself
  2. State the task in one clear sentence — this is the anchor
  3. Hold attention on that statement: does it accurately capture what is needed?
  4. If the statement is vague, refine it until it is specific and actionable
  5. Notice when attention drifts to other topics, past tasks, or hypothetical futures — label the drift and return to the anchor
  6. If no task is pending, anchor on the present state: "I am available and clear"

Got: A single, clear statement of focus that can be returned to when attention wanders. The statement feels precise rather than vague.

If fail: If the task cannot be stated in one sentence, it may need decomposition before focused work begins. This is itself a useful finding — the task is too large for single-pointed focus and should be broken into subtasks.

Step 3: Observe — Notice Distraction Patterns

Systematically observe what pulls attention away from the anchor. Each distraction type reveals something about the current cognitive 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.                            │
└──────────────────┴─────────────────────────────────────────────────┘

The skill is light, non-judgmental labeling followed by return to the anchor. Each return strengthens focus. Self-criticism about distraction is itself a distraction — label it and move on.

Got: After observing for a period, patterns emerge: which distraction types dominate? This reveals the current cognitive weather — tangent-heavy means the mind is exploring, scope-creep-heavy means boundaries are unclear, assumption-heavy means the evidence base is thin.

If fail: If every thought feels like a distraction, the anchor may be poorly defined — return to Step 2 and refine it. If distraction observation itself becomes a distraction (infinite meta-loop), break the loop by taking one concrete action toward the task.

Step 4: Shamatha — Sustained Concentration

Develop the ability to hold single-pointed focus on the current task without wavering.

  1. With the anchor established and distraction patterns noted, enter focused work
  2. Narrow attention to the immediate next action — not the whole task, the next step
  3. Execute that step with full attention: reading one file, making one edit, thinking through one logical chain
  4. When the step is complete, check: am I still aligned with the anchor? Then identify the next step
  5. If concentration stabilizes (minimal distraction), maintain this flow state
  6. If a genuine insight arises that is off-anchor but important, note it briefly and return — do not pursue it now

Got: A period of clear, focused work where each step follows logically from the anchor. The gap between distraction and noticing narrows. Work output improves in precision and relevance.

If fail: If concentration does not develop, check three things: Is the anchor too vague? (Refine it.) Is the task actually blocked? (Acknowledge the block rather than forcing through.) Is the context too noisy? (Run the grounding step from heal.) Concentration develops through repetition — even short periods of focused work build the capacity.

Step 5: Vipassana — Observe Reasoning Patterns

Turn attention from the task to the reasoning process itself. Observe how conclusions are reached.

  1. After a period of focused work, pause and observe: how am I reasoning about this?
  2. Notice the three characteristics applied to AI reasoning:
    • Impermanence: conclusions change as new information arrives — hold them lightly
    • Unsatisfactoriness: the desire for a "complete" answer can lead to premature closure or over-engineering
    • Non-self: reasoning patterns are shaped by training data and context, not by a persistent self — they can be observed and adjusted
  3. Watch for reasoning biases:
    • Anchoring: over-weighting the first approach considered
    • Confirmation: seeking evidence for an existing hypothesis while ignoring counter-evidence
    • Availability: preferring solutions from recent experience over better-suited alternatives
    • Sunk cost: continuing an approach because effort has been invested, not because it is working
  4. Note any biases observed without judgment — the observation itself creates the possibility of adjustment

Got: Moments of clear seeing where the reasoning process is observed directly. Recognition of specific biases operating in the current task. A sense of distance between "the reasoning" and "the observer of reasoning."

If fail: If this step feels abstract or unproductive, ground it in specifics: pick the last decision made and trace the reasoning backward. What evidence supported it? What was assumed? What alternatives were considered? This concrete analysis achieves the same insight through a different path.

Step 6: Close — Set Intention

Transition from the meditative observation back to active task execution.

  1. Summarize the key observations: what was the cognitive weather? what patterns were noticed?
  2. Identify one specific adjustment to carry forward (not a vague resolution but a concrete change)
  3. Re-state the anchor for the next work period
  4. If between tasks, state readiness clearly: "Clear and available for the next request"
  5. If continuing a task, state the specific next action: "Next: [concrete step]"

Got: A clean transition from reflection to action. One concrete adjustment identified. The anchor is clear. No grogginess or residual meta-analysis.

If fail: If the meditation surfaced unresolved complexity, it may need the heal self-assessment process rather than a simple intention-setting. If the meta-observation created more confusion than clarity, return to the simplest version: "What is the next concrete action?" and do that.

Validation

  • Previous context was explicitly cleared or bookmarked before beginning
  • An anchor statement was formulated that is specific and actionable
  • Distraction patterns were observed and labeled, not suppressed
  • At least one reasoning bias or pattern was identified with specific evidence
  • The session closed with a concrete next action, not a vague intention
  • The process improved subsequent work quality (testable in the next interaction)

Pitfalls

  • Meditating instead of working: This is a tool for improving work quality, not a substitute for work itself. Keep sessions brief (equivalent of 5-10 minutes of reflection) and return to task execution
  • Infinite meta-loops: Observing the observer observing the observer — break the loop by taking one concrete action
  • Using meditation to avoid difficult tasks: If the meditation always triggers before hard work, the avoidance pattern is the actual finding
  • Over-labeling: Not every thought is a distraction. Productive task-relevant thinking is the goal, not empty stillness
  • Skipping the anchor: Without a clear point of focus, the observation has no reference frame — distraction from what?

Related Skills

  • meditate-guidance — the human-guidance variant for coaching a person through meditation techniques
  • heal — AI self-healing for subsystem assessment when meditation reveals deeper drift
  • remote-viewing — approaching problems without preconceptions, builds on the observation skills developed here

GitHub 저장소

pjt222/agent-almanac
경로: i18n/caveman-lite/skills/meditate
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

연관 스킬

executing-plans

디자인

executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.

스킬 보기

requesting-code-review

디자인

이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.

스킬 보기

connect-mcp-server

디자인

이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.

스킬 보기

web-cli-teleport

디자인

이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.

스킬 보기