
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", "prune brain", "review skills", "consolidate notes", "prune notes".
- Installs
- 222
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/poteto/noodle --skill meditate- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads meditate automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Meditate
Autonomous Session Mode
When running non-interactively (Cook, Oops, Repair):
- Apply all high-confidence changes autonomously. For ambiguous or risky changes (brain file deletions, principle rewrites), file a todo instead.
- Commit all changes with the
/commitskill.
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
Use Tasks to track progress (TaskCreate per step, TaskUpdate to in_progress/completed).
1. Build snapshots
sh <skill-path>/scripts/snapshot.sh brain/ /tmp/brain-snapshot.md
sh <skill-path>/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 § Auditor 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 § Reviewer 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. Audits description frontmatters for context bloat.
4. Review reports
Present the user with a consolidated summary. See references/agents.md § Report Template for the 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 and pick a name that captures the combined insight
- Bloated skill descriptions: Tighten frontmatter descriptions — cut what Claude can infer, keep only distinctive triggers and purpose
- CLAUDE.md issues: Rewrite or delete
- Stale memories: Delete or rewrite
7. Housekeep
Clean stale .noodle/ state (old debates, completed sessions, stale plan artifacts). 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]
FAQ
What does the meditate 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", "prune brain", "review skills", "consolidate notes", "prune notes".
How do I install meditate?
Run npx skills add https://github.com/poteto/noodle --skill meditate in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/meditate/ (personal) or .claude/skills/meditate/ (project).
Which AI agents can use meditate?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is meditate safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains meditate?
It is published by poteto in poteto/noodle. It has 222 recorded installs.
More from poteto/noodle
adversarial-review
poteto/noodle
Adversarial code review using cross-model approach. Spawns reviewers on the opposing model (Claude uses Codex, Codex uses Claude) to challenge work from distinct critical lenses. Produces a synthesized verdict with findings and lead judgment. Triggers: "adversarial review".
unslop
poteto/noodle
Remove AI writing patterns from prose. Use for docs, READMEs, blog posts, any non-code text that should sound human. Triggers: "unslop", "humanize", "make this sound human", "clean up this writing", "edit for voice", "de-AI this text".
ts-best-practices
poteto/noodle
TypeScript type safety guidelines for writing maximally type-safe code. Apply these patterns when writing or reviewing any TypeScript: discriminated unions, type narrowing, type guards, exhaustiveness checks, avoiding as casts, preferring unknown over any, and making impossible states unrepresentable. Use this skill whenever writing TypeScript code, reviewing TypeScript for type safety issues, or when the user mentions type safety, type narrowing, discriminated unions, or asks to make types stricter/more explicit.
debugging
poteto/noodle
Systematic root-cause debugging methodology. Use for any technical problem — errors, failures, unexpected behavior, or when stuck. Triggers: "debug", "fix this", "what's wrong", "investigate".
quality
poteto/noodle
Post-cook quality gate. Reviews completed cook work for correctness, scope discipline, and principle compliance. Emits stagemessage events with findings. Triggers after execute stages, on '/quality', 'review this', 'check the work', 'assess quality'.
commit
poteto/noodle
Create conventional commit messages. Use when the user says "commit this", "save changes", "git commit", asks to commit code, write a commit message, or format git history. Follows conventional commits specification.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.