Identify Kill List
Names what the substacker writer should stop doing — habits with no evidence of use, goals that became theatre, sections with 2 consecutive dormant quarters, and agents in the team whose output the writer ignores. Produces a bulleted list, each item with one sentence of why. Max 4 items. Ordered by ease (easiest first). Used once per Growth Strategist review. Trigger keywords — kill list, stop doing, what to cut, dead habits, dormant, ignored output.
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 identify-kill-listgit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/identify-kill-list ~/.claude/skills/identify-kill-listPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Identify Kill List
## Workflow
```
Per quarterly review:
- [ ] Step 1: Candidate sources:
- Sections classed "candidate-for-prune" in section-portfolio-assessment
- Goals unchanged 2 quarters in a row with no progression
- Agents in the team whose output the writer has not referenced in any decision this quarter
- Habits writer flagged in audience-notes as guilt-producing but unused
- [ ] Step 2: Filter to max 4 items (ruthless)
- [ ] Step 3: Order by ease: easiest kills first
- [ ] Step 4: Each item: one-sentence why
```
## Rules
- **Max 4 items**. More than 4 and the writer won't stop any of them.
- **First kill** should be something the writer will actually do within a week.
- **Last kill** can be harder (a habit, a section) — but still named.
## Worked example
```markdown
- Drop the daily trend-scout digest. You haven't acted on any item from it in 12 weeks.
- Kill the "book reviews" section. One post in two quarters; it's guilt scaffolding, not a section.
- Stop writing the weekly "state of the publication" note to yourself. The Growth Analyst's report is doing that job now.
- Remove the "get on Hacker News front page" goal. It's not a goal, it's an outcome, and chasing it warps the writing.
```
## Guardrails
1. Never exceed 4 items.
2. Order by ease. First item should be actionable this week.
3. One-sentence rationale each. No paragraphs.
4. Pull from multiple candidate sources — don't have all 4 be sections.Details
- Skill name
identify-kill-list- Repository
- lyndonkl/claude
- Path
skills/identify-kill-list/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Identify Kill List skill do?
Names what the substacker writer should stop doing — habits with no evidence of use, goals that became theatre, sections with 2 consecutive dormant quarters, and agents in the team whose output the writer ignores. Produces a bulleted list, each item with one sentence of why. Max 4 items. Ordered by ease (easiest first). Used once per Growth Strategist review. Trigger keywords — kill list, stop doing, what to cut, dead habits, dormant, ignored output.
How do I install the Identify Kill List 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 Identify Kill List 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.
Layered Reasoning
200lyndonkl/claude
Structures thinking across multiple abstraction levels (30,000 ft strategic, 3,000 ft tactical, 300 ft operational) while maintaining consistency between layers. Guides through top-down decomposition, bottom-up aggregation, cross-layer translation, and constraint propagation. Use when reasoning across multiple abstraction levels, designing systems with hierarchical layers, explaining concepts at different depths, maintaining consistency between principles and implementation, or when users mention 30,000-foot view, layered thinking, abstraction levels, top-down design, or strategy-to-execution
Hook Generator
200lyndonkl/claude
Generates 3-5 candidate first-line hooks for a specific platform (Substack Note, X, LinkedIn, cross-post) from a given spine. Uses platform-appropriate hook patterns (confession / claim / question / reframe) and voice-profile constraints. Runs before each platform rewrite so the rewrite skill picks the strongest hook rather than reusing the essay's opener verbatim on every platform. Trigger keywords — hook, opening line, platform hook, first tweet, LinkedIn hook, Substack Note hook.
Linkedin Post Rewrite
200lyndonkl/claude
Rewrites a published substacker essay as a LinkedIn post with a hook fitting the 210-char fold, practitioner framing (less confessional than Substack), short 2-3 line paragraphs, and 0-2 niche hashtags. 900-2500 characters. Emits linkedin-post.md. Use as the LinkedIn-native arm of the Distribution Translator. Trigger keywords — LinkedIn post, LinkedIn rewrite, practitioner, professional network, niche hashtags.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.