cascade-brain
Skill0 starsChanged 41 days agoMITView on GitHub
Discovery + editorial engine for Cascade — runs `gh search` across multiple queries, fetches curated awesome-lists, cross-checks against installed inventory, and editorializes each candidate (HIGH/MED/SKIP with rationale). Also includes utility subcommands for skill description sharpening, telemetry stats, audit, rebuild, trace. TRIGGER when user mentions "cascade brain", "cascade analysis", "deep skill research", "what should I install next", "skill audit", "sharpen description", "lurking skills", "rebuild index", "trace routing", "why didn't X fire", "cascade health". SKIP: quick gh-only search (use cascade-discover), one-off code edits to hook files (use direct edits).
In this repository42 other files it gives its agents.
- skills/composition-patterns/AGENTS.mdAGENTS.md
- skills/react-view-transitions/AGENTS.mdAGENTS.md
- skills/vercel-optimize/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/last30days/CLAUDE.mdCLAUDE.md
- banner-designSkill
- brandSkill
- cascade-discoverSkill
- cavemanSkill
- cdt-a11y-debuggingSkill
- cdt-chrome-devtools-cliSkill
- cdt-chrome-devtoolsSkill
- cdt-cookie-debuggingSkill
- cdt-debug-optimize-lcpSkill
- cdt-memory-leak-debuggingSkill
- cdt-troubleshootingSkill
- vercel-composition-patternsSkill
- core-web-vitalsSkill
- designSkill
- design-systemSkill
- efficiencySkill
- email-best-practicesSkill
- frontend-slidesSkill
- grill-with-docsSkill
- humanizerSkill
- improve-codebase-architectureSkill
- job-search-kitSkill
- last30daysSkill
- react-emailSkill
- vercel-react-view-transitionsSkill
- seo-localSkill
- seo-mapsSkill
- slidesSkill
- ui-stylingSkill
- ui-ux-pro-maxSkill
- vercel-optimizeSkill
- web-design-guidelinesSkill
- web-quality-auditSkill
- wq-accessibilitySkill
- wq-best-practicesSkill
- wq-performanceSkill
- wq-seoSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
When you (Claude) run cascade-brain analyze:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cascade Brain — discovery, editorial, and tuning
The companion to cascade-discover. Where discover is fast/breadth (gh search → ranked list), brain is depth + editorial — pulls in curated awesome-lists, cross-references against installed inventory, and produces a thoughtful HIGH/MED/SKIP table with rationale.
Primary command — analyze
python3 ~/.claude/skills/cascade-brain/brain.py analyze [--top 30] [--min-stars 30]Outputs a research brief with three sections:
- GitHub search candidates (via
cascade-discover --json) — top N repos ranked by stars × recency, already cross-checked against installed inventory, withclosest_installedannotation per candidate (heuristic redundancy hint) - Curated awesome-lists to fetch — URLs to
hesreallyhim/awesome-claude-code,wshobson/agents,ComposioHQ/awesome-claude-skills, etc. - Editorial framing for Claude — explicit instructions to bucket every candidate into HIGH / MED / SKIP with one-line rationale, scoped to your RevOps/sales workflow
Workflow when invoked
When you (Claude) run cascade-brain analyze:
- The script outputs the structured brief to stdout
- You then
WebFetcheach curated list URL listed in section 2 - Parse those READMEs for repos NOT in the inventory list
- Merge: gh-search candidates + curated-list net-new entries
- For each candidate, decide:
- HIGH = net-new gap-filler, recommend installing
- MED = complement to existing skill X, worth watching
- SKIP = redundant / niche / stale / low-quality
- Save the final markdown report to
~/.claude/discover-reports/analysis-<date>.md
The script is data infrastructure; the editorial reasoning is yours.
Secondary command — sharpen
Improve a SKILL.md description using the TRIGGER when: / SKIP: pattern.
Inspect mode (default)
python3 ~/.claude/skills/cascade-brain/brain.py sharpen <skill-name>Outputs the current description, score, body excerpt, and a template. You read it, draft a sharpened version.
Apply mode
python3 ~/.claude/skills/cascade-brain/brain.py sharpen <skill-name> --apply "description: New text. TRIGGER when..."Writes the new description to the SKILL.md, prints before/after score. Run cascade-brain rebuild afterward to refresh the index.
Workflow
cascade-brain audit --weak-onlyto find candidates- For each weak skill:
cascade-brain sharpen <name>to read context - Draft new description following the template (one line, includes
TRIGGER whenquoted phrases andSKIP:alternatives) cascade-brain sharpen <name> --apply "<new desc>"to writecascade-brain rebuildonce batch is done
Utility subcommands
| Command | What it does |
audit [--weak-only] [--top N] | Score every SKILL.md for length / TRIGGER / SKIP / name-in-desc |
stats [--lurkers] | Top recommendations from skill-recommendations.jsonl + lurking skills |
rebuild | Re-init the intelligence index (run after sharpen edits) |
health | Index size, telemetry events, patterns, hook status |
trace "prompt" | Run a prompt through the route hook live — see exactly what fires |
When to invoke
Use this skill when:
- "what should I install next" / "do a deep cascade analysis" / "research new claude tools" →
analyze - "sharpen X" / "fix the description for X" / "audit weak skills" →
sharpen/audit - "why didn't X fire" / "trace routing for Y" →
trace - "cascade health" / "rebuild index" / "lurking skills" →
health/rebuild/stats
Skip when:
- Quick gh-only search without editorial → use
cascade-discoverdirectly - One-off code edit to hooks → just edit
- Installing a specific named skill → use the existing install flow
Schedule weekly analysis
schedule "weekly cascade analysis" "python3 ~/.claude/skills/cascade-brain/brain.py analyze --top 50 > ~/.claude/discover-reports/weekly-$(date +%F).md"Then on Friday morning Claude reviews the file and produces the editorial report.
Files this skill touches
| Path | Role |
~/.claude/skills/cascade-discover/discover.py | Invoked via --json for candidate generation |
~/Desktop/personal-os-main/.cascade/intelligence/skill-recommendations.jsonl | Telemetry (read by stats) |
~/Desktop/personal-os-main/.cascade/intelligence/ranked-context.json | Index metadata (read by health) |
~/Desktop/personal-os-main/scripts/hooks/intelligence.cjs | Re-init on rebuild |
~/Desktop/personal-os-main/scripts/hooks/hook-handler.cjs | Route handler (invoked by trace) |
~/.claude/skills/*/SKILL.md | Read by audit; modified by sharpen --apply |
sharpen --apply is the only command that writes to skill files. Everything else is read-only.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

