baalda-optimizerlisted

Framework-driven audit and optimizer for a Baalda vault. Applies 9 frameworks (F1 Anthropic CLAUDE.md, F2 Karpathy Wiki, F3 Caveman, F4 Chroma Context Rot, F5 Anthropic Memory, F6 Progressive Disclosure, G7 Hygiene, F8 Reflection, F9 Architecture & Discoverability). F9 walks the real discovery chain (root CLAUDE.md, routing, folder Plot.md, file), audits routing tables against folder reality, refreshes per-folder Plot.md indexes, finds navigation orphans, and proposes reorganizations grounded in the user's own context. Every finding ships a concrete fix; the user picks apply-now or save-to-plan per finding. Baalda-aware: takes a vault checkpoint before applying, never touches `.context/`, and routes every move, rename or delete of a synced note through the app or the MCP tools so notes keep their `doc_id`. TRIGGERS: baalda optimizer, optimize my vault, vault audit, second brain audit, clean up my Baalda vault, framework audit, discoverability check, architecture audit, reorg vault. Run from the vault root.
naveedharri/benai-skills · ★ 61 · AI & Automation · score 72

Install: claude install-skill naveedharri/benai-skills

# Baalda Vault Optimizer Apply 9 frameworks to every markdown file in the vault. For each framework, read its pass-implementation file, run every check, log findings, walk the user through fixes per item, apply (or save to a plan). Save one comprehensive HTML report grouped by framework. **Do not inline the HTML in chat — only the saved path and a one-paragraph summary.** ## Operating philosophy — read carefully, this is what makes this skill different 1. **Every finding ships a concrete fix.** No flag-only. No "warn and forget." No manual-review pile. When the user runs apply-mode, every finding becomes either an applied edit, a saved migration step in a dated reorg plan, or (only if the user explicitly declines this finding in walk) a recorded decline. Nothing lingers as an open warning across runs. 2. **Severity is informational, not gating.** `fail` / `warn` / `info` describes how load-bearing the issue is; it does *not* gate whether a fix is offered. Every check produces fixes. 3. **Walk per item, user picks the target.** Bulk-apply is reserved for purely mechanical fixes (em dashes, duplicate H1). Anything semantic — wikilink repointing, merges, routing rewrites, Plot.md generation, reorganizations — is walk-only with the user confirming the destination/winner/wording per item. 4. **Two modes for every fix:** *apply now* (executes in this run) or *save to plan* (writes the change as a checklist step into the **plan file**, whose path is resolved from the role registr