lyndonkl/skills/identify-kill-list
skills/identify-kill-list/SKILL.md
--- name: identify-kill-list description: 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 --global
skillsauthnpx skillsauth add lyndonkl/claude skills/identify-kill-listInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 10:15 AM146.0s1 file scanned
SKILL.md
- name:
- identify-kill-list
- description:
- 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.
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
- 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
- Never exceed 4 items.
- Order by ease. First item should be actionable this week.
- One-sentence rationale each. No paragraphs.
- Pull from multiple candidate sources — don't have all 4 be sections.
- Never suggest killing something the writer explicitly committed to this quarter.
- Previous-quarter kills that the writer didn't execute can be re-named — but only once, not indefinitely.
Related Skills
lyndonkl/skills/zettel-note
development
VerifiedTrustedCommunity
--- name: zettel-note description: The note-writing discipline for this vault's evergreen knowledge graph, modeled on a Zettelkasten reading companion and governed by the vault conventions. Enforces declarative-claim titles, one claim per note (atomicity), own-words prose with no block quotes, the piped [[slug|Title]] link form, the labeled link-relationship vocabulary (Confirms/Contradicts/Extends/Context/Prerequisite/Builds-on/Applies/Example-of/Contrasts-with), 3-6 links per note, and search-
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-transfer-planner
development
VerifiedTrustedCommunity
Plans between-round FIFA World Cup Fantasy transfers — budgets the round's free transfer(s), forces out players whose nation has been eliminated, chases fixture-swing drops, upgrades on value, and decides when a rebuild is large enough to fire the Wildcard instead of spending free transfers one at a time. Ranks candidate in/out pairs by EV gain over each player's remaining survival horizon (delta xEV weighted by progression_carry) MINUS transfer cost (a free transfer is cheap, a points hit is real, churning the squad for marginal swings is a critic flag), and tags forced/fixture/upgrade priority. Emits a `transfer-plan` signal. Use when called by wc-squad-architect (whose transfer work this skill is the engine for) and by the strategists in the populate stage when their candidate is transfer-adjacent rather than a full rebuild.
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-tournament-state
testing
VerifiedTrustedCommunity
Reads and updates the FIFA World Cup Fantasy tournament state machine (footballfantasy/context/tournament-state.md) — the temporal backbone tracking phase (pre-tournament → group MD1-3 → R32 → R16 → QF → SF → final), budget ($100m group / $105m knockouts), nation cap (3 group, loosening in knockouts), chips remaining, surviving nations, each owned player's elimination-risk horizon, and deadlines. Validates state on load (count/feasibility checks), applies phase transitions, and appends to the append-only state log (never silent overwrite). Use to load state at the start of a run and to commit state changes after the manager makes a move.
119SKILL.mdUpdated Jun 12, 2026
lyndonkl/wc-signal-emitter
development
VerifiedTrustedCommunity
Validates and persists FIFA World Cup Fantasy signal files to signals/YYYY-MM-DD-<type>.md. Checks the required frontmatter (type, round, date, emitted_by, confidence, source_urls), range-checks declared numeric signals, confirms every factual claim carries a source URL or "manager-provided", rejects unknown signal types, and refuses to persist a signal that fails validation (logging the failure instead). Keeps the inter-agent signal layer auditable so downstream agents can trust what they read and never re-derive it. Use whenever an agent or skill writes a signal.
119SKILL.mdUpdated Jun 12, 2026