Recommend Prune
Recommends structural cleanups for the substacker section map — sections to retire, sections to merge, posts to reassign. Applies under-filled, stale, and overlapping heuristics. Writes proposals with reasons-to-reject (steelman counter). Does not execute. Use once per Curator run, after drift audit. Trigger keywords — prune, retire section, merge sections, reassign post, cleanup.
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill recommend-prunegit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/recommend-prune ~/.claude/skills/recommend-prunePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Recommend Prune ## Three cleanup categories 1. **Retire**: section with <2 posts added in 3 months AND no new cluster signal → candidate for retirement. 2. **Merge**: two sections whose promises overlap >60% semantically OR whose post-sets have >40% cross-fit → merge candidate. 3. **Reassign**: posts from `audit-drift` flagged as genuine-drift → suggest target section or move to `unassigned`. ## Workflow ``` Per Curator run: - [ ] Step 1: For each section, check retire conditions - [ ] Step 2: Cross-check section promises for merge candidates - [ ] Step 3: Collect reassignment candidates from drift audit - [ ] Step 4: For each proposal: write reasoning + reasons-to-reject - [ ] Step 5: Emit three lists (retire / merge / reassign) ``` ## Guardrails 1. Never delete. Only retire (mark status: retired, keep in map). 2. Never merge without the merge proposal fully visible in review artifact (both original promises preserved verbatim). 3. Never recommend pruning a provisional section in its first 2 cycles — give it probation time. 4. Reasons-to-reject are mandatory for every proposal. Writer needs the counter-argument pre-built.
Details
- Skill name
recommend-prune- Repository
- lyndonkl/claude
- Path
skills/recommend-prune/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Recommend Prune skill do?
Recommends structural cleanups for the substacker section map — sections to retire, sections to merge, posts to reassign. Applies under-filled, stale, and overlapping heuristics. Writes proposals with reasons-to-reject (steelman counter). Does not execute. Use once per Curator run, after drift audit. Trigger keywords — prune, retire section, merge sections, reassign post, cleanup.
How do I install the Recommend Prune skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Recommend Prune popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
Academic Letter Architect
200lyndonkl/claude
Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
Adr Architecture
200lyndonkl/claude
Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
Search Corpus
200lyndonkl/claude
Answers "what have I already thought about X?" by searching the substacker corpus (seeds, drafts, published) for seeds matching a topic, keyword, analogy, or author. Returns a ranked list of seeds with id, title, status, density score, and a one-line excerpt. Use when another agent (Intuition Builder, Editor) needs prior thinking before generating new material, or when the writer asks "have I written about X." Trigger keywords — search, find, what have I, already thought, prior work, precedent, have I written about.
Propose Section
200lyndonkl/claude
Converts one candidate cluster from cluster-corpus-by-theme into a named, promised section proposal ready for writer review. Calls write-section-promise for the one-sentence promise. Rates fit confidence (high / medium / low / provisional) and flags borderline posts. Use once per cluster that passes ≥3-post threshold. Trigger keywords — propose section, section proposal, new section candidate.
Section Break Check
200lyndonkl/claude
Verifies the section-break style in a substacker draft matches the post register — asterisks (* * *) for essayistic posts under 2500 words, H2 for methodology / how-to / technical posts. Flags mixed registers (H2 in a reflective essay, asterisks in a structured how-to). Per the style-guide rhythm rule. Use every draft. Trigger keywords — section break, asterisk, H2, headers, register, essayistic vs methodology.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.