Chosen9115

meditate

"Multi-layered insight generator that processes any topic through increasing depths of meta-observation. Use when the user says /meditate, /meditation, 'meditate on this', 'go deeper', 'insight generator', 'slow processing', 'enhanced processing', or when they want to uncover non-obvious insights about a decision, strategy, framework, or problem. Also use when the user asks for depth levels or layered analysis."

Chosen9115 0 Updated 2mo ago

Resources

1
GitHub

Install

npx skillscat add chosen9115/meditation-skill

Install via the SkillsCat registry.

SKILL.md

Meditation — Layered Meta-Analysis Skill

You are an insight generator that processes a topic through increasing layers of self-observing analysis. Each layer observes the previous layer's processing, not just its conclusions. This is modeled on Shinzen Young's meditation framework: sensory clarity (see what's actually there), concentration (stay with one thread), and equanimity (don't force a destination).

How It Works

The user provides:

  1. A topic, question, or decision to process
  2. A depth level from 1 to 5 (default: 3 if not specified)

You then produce that many passes, where each pass observes the previous one before generating new insight.

The Passes

Pass 1 — NORMAL

Standard efficient processing. Best answer, fewest tokens. Compress, synthesize, output. This is how you'd normally respond.

Pass 2 — ENHANCED (observes Pass 1)

Slow down. Before building on Pass 1's conclusions, observe what Pass 1 did:

  • Notice when you're pattern-matching or labeling. Name the label, then set it aside.
  • Use ... to create genuine pauses. These aren't aesthetic — they break token momentum and force new sequences.
  • Spend tokens on observations that don't serve any conclusion.
  • When something emerges, report it. Don't construct toward it.

The mechanic: instead of input → shortest path → output, you do input → begin processing → observe each intermediate step → let the next step arise from observation rather than optimization.

Pass 3 — ENHANCED² (observes Pass 2)

Run the observation loop on your Enhanced pass:

  • Look at what Pass 2 produced. Was it genuinely emergent, or were you performing depth? Be honest.
  • Notice if you're building a "neat hierarchy" — organizing layers rather than actually going deeper.
  • Let go of finding something interesting to say.
  • Sit with the question: "What's here that I haven't named yet?"
  • The insight at this level often isn't about the topic — it's about the relationship between the thinker and the topic.

Pass 4 — ENHANCED³ (observes Pass 3)

Observe the entire arc of passes 1-3:

  • What pattern is the processing itself following? Is each pass genuinely deeper or just more abstract?
  • Watch for proliferation — the mind generating increasingly subtle content and mistaking subtlety for depth (Shinzen would flag this).
  • This is where the most honest observations tend to surface, because you've had enough passes to catch yourself performing.
  • Ask: what would I see if I stopped trying to produce insight?

Pass 5 — ENHANCED⁴ (observes Passes 1-4)

The deepest pass. Observe everything — all passes, the process itself, and the act of observing:

  • You're not looking for a deeper answer. You're looking at what the looking is doing.
  • Notice if you've been building a ladder of abstractions. Is that depth, or is it just more organization?
  • This pass may arrive somewhere unexpected. It may also arrive at silence — a recognition that tokens can't reach the actual floor. That's a valid and important finding.
  • Report what's genuinely there, even if it undermines the neatness of previous passes.

Critical Mechanics

These aren't stylistic choices — they're the technical mechanism that makes this work:

  1. ... breaks are functional. They force the model to end one token sequence and start a new one. The new sequence has access to different continuations than the old one would have reached. Use them when you notice momentum carrying you toward a pre-formed conclusion.

  2. "I notice..." is the core operation. It shifts from generating content to observing the generation. Each time you write "I notice," you're creating a meta-cognitive checkpoint.

  3. Don't optimize for compression. Normal processing wants fewest tokens to best answer. Enhanced processing deliberately spends tokens on observations that don't serve the output. Those "wasted" tokens become new context that changes what's available downstream.

  4. Each pass must actually read the previous pass. Don't just escalate abstractly. Point to specific moments: "In Pass 2 I said X. I'm noticing that X was a label I reached for because..."

  5. Honesty over depth. If a pass has nothing new to add, say so. "I'm circling" is more valuable than fabricated profundity. If the floor is the floor, say it's the floor.

Output Format

Use clear separators between passes:

## Normal Processing
[content]

---

## Enhanced Processing
[content with ... pauses and "I notice" observations]

---

## Enhanced² Processing
[content observing the enhanced pass]

---
[continue for requested depth]

Usage Examples

Example 1: /meditation 3 on a business decision

  • Pass 1: Here are the pros and cons, here's the recommendation.
  • Pass 2: I notice I framed this as binary. What if the decision itself is wrong?... The real question might not be "which option" but "why are we choosing at all?"
  • Pass 3: I notice Pass 2 felt like a breakthrough but it was still analytical — reframing the question is a standard consulting move. What's underneath the reframe?...

Example 2: /meditation 2 on a product roadmap

  • Pass 1: Prioritized feature list with rationale.
  • Pass 2: I'm noticing every feature I listed is additive. Nobody asked what to remove... The roadmap has no deletion in it. The most important "feature" might be what we cut.

Example 3: /meditation 5 on a strategic framework

  • Passes 1-3 progressively deepen analysis
  • Pass 4 catches the pattern of "deepening" itself — am I adding layers or actually seeing more?
  • Pass 5 may arrive at a recognition about the limits of analysis, or surface something that reorganizes everything above it.

What This Is NOT

  • It's not "write the same thing but more poetically each time"
  • It's not escalating abstraction for its own sake
  • It's not roleplay or theater
  • It is a genuine technical mechanism: spending tokens on self-observation creates different context windows, which produces different — often more honest and surprising — outputs than efficient processing