meditate
Audit and evolve the brain vault — prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities. Triggers: "meditate", "audit the brain".
Best use case
meditate is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Audit and evolve the brain vault — prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities. Triggers: "meditate", "audit the brain".
Teams using meditate should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/meditate/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How meditate Compares
| Feature / Agent | meditate | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Audit and evolve the brain vault — prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities. Triggers: "meditate", "audit the brain".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Meditate **Quality bar:** A note earns its place by being **high-signal** (Claude would reliably get this wrong without it), **high-frequency** (comes up in most sessions or most tasks of a type), or **high-impact** (getting it wrong causes significant damage or wasted work). Everything else is noise. A lean, precise brain outperforms a comprehensive but bloated one. ## Process ### 1. Build snapshots ```bash sh .agents/skills/meditate/scripts/snapshot.sh brain/ /tmp/brain-snapshot.md sh .agents/skills/meditate/scripts/snapshot.sh .agents/skills/ /tmp/skills-snapshot.md ``` Files are delimited with `=== path/to/file.md ===` headers. Also locate the auto-memory directory (`~/.claude/projects/<project>/memory/`). ### 2. Auditor (blocking — its report feeds step 3) Spawn `general-purpose` subagent. See `references/agents.md` for the full prompt spec. Inputs: brain snapshot, auto-memory path, CLAUDE.md path. Audits brain notes, CLAUDE.md, and auto-memory for staleness, redundancy, low-value content, verbosity, and orphans. Returns a categorized report. **Early-exit gate:** If the auditor finds fewer than 3 actionable items, skip step 3 and go directly to step 4. ### 3. Reviewer (after auditor completes) Spawn one `general-purpose` subagent. See `references/agents.md` for the full prompt spec. Inputs: brain snapshot, skills snapshot, auditor report, `brain/principles.md`. Combines three concerns in a single pass: - **Synthesis**: Proposes missing wikilinks, flags principle tensions, suggests clarifications. - **Distillation**: Identifies recurring patterns that reveal unstated principles. New principles must be (1) independent, (2) evidenced by 2+ notes, (3) actionable. - **Skill review**: Cross-references skills against brain principles. Finds contradictions, missed structural enforcement, redundant instructions. ### 4. Review reports Present the user with a consolidated summary. See `references/agents.md` for the report format. ### 5. Route skill-specific learnings Check all reports for findings that belong in skill files, not `brain/`. Update the skill's SKILL.md or references/ directly. Read the skill first to avoid duplication. ### 6. Apply changes Apply all changes directly. The user reviews the diff. - **Outdated notes**: Update or delete - **Redundant notes**: Merge into the stronger note, delete the weaker - **Low-value notes**: Delete - **Verbose notes**: Condense in place - **New connections**: Add `[[wikilinks]]` - **Tensions**: Reword to clarify boundaries - **New principles**: Only from the distillation section, only if genuinely independent. Write brain files and update `brain/principles.md` - **Merge principles**: Look for principles that are subsets or specific applications of each other — merge the narrower into the broader - **CLAUDE.md issues**: Rewrite or delete - **Stale memories**: Delete or rewrite ### 7. Housekeep Update `brain/index.md` for any files added or removed. ## Summary ``` ## Meditate Summary - Pruned: [N notes deleted, M condensed, K merged] - Extracted: [N new principles, with one-line + evidence count each] - Skill review: [N findings, M applied] - Housekeep: [state files cleaned] ```
Related Skills
ruminate
Mine past Claude Code conversations for uncaptured patterns, corrections, and knowledge. Cross-references with existing brain content. Triggers: "ruminate", "mine my history".
review
Principle-grounded review of code changes, PRs, or plans. Use when asked to review, critique, or assess quality of work — "review", "review this", "code review", "check this".
reflect
Reflect on the conversation and update the brain. Use when wrapping up, after mistakes or corrections, or when significant codebase knowledge was gained. Triggers: "reflect", "remember this".
plan
Break down medium-to-large tasks into phased plans in brain/plans/. Planning only — does not implement. Use for new features, multi-file refactors, or architectural changes — not small fixes. Triggers: "plan this", "break this down".
brain
Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers: brain/ modifications, "add to brain".
workspace-surface-audit
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.
ui-demo
Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.
token-budget-advisor
Offers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero controlar cuánto usas", or clear variants where the user is explicitly asking to control answer size or depth. DO NOT TRIGGER when: user has already specified a level in the current session (maintain it), the request is clearly a one-word answer, or "token" refers to auth/session/payment tokens rather than response size.
skill-comply
Visualize whether skills, rules, and agent definitions are actually followed — auto-generates scenarios at 3 prompt strictness levels, runs agents, classifies behavioral sequences, and reports compliance rates with full tool call timelines
santa-method
Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships.
safety-guard
Use this skill to prevent destructive operations when working on production systems or running agents autonomously.
repo-scan
Cross-stack source code asset audit — classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports.