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/conf-theme-clustering
testing
VerifiedTrustedCommunity
Cluster a conference's event records into a small set of coarse themes with finer sub-clusters, an explicit outlier bucket, and soft (multi-membership) affinities — using the hybrid embed-then-label pipeline (embed abstracts, reduce, density-cluster, then LLM-label the clusters) when embedding libraries are available, and an LLM-reasoned hierarchical fallback when they are not. Embeddings do the grouping; the LLM only names the groups. Conference-agnostic. Use when turning structured event records into a navigable theme map for preference elicitation and scheduling, when you need 6-8 reasonable themes rather than 20 muddy ones, or when overlapping talks must belong to more than one theme. Trigger keywords - theme clustering, cluster talks, embed then label, soft membership, outlier talks, conference themes, topic map.
127SKILL.mdUpdated Jun 28, 2026
lyndonkl/conf-schedule-optimization
development
VerifiedTrustedCommunity
Build a personal conference schedule as a constraint-optimization problem — hard constraints (no time overlap, room-to-room travel time, capacity/registration, the attendee's own must-attends and blackouts) plus a user-owned weighted objective trading interest against breadth, pacing (maximize contiguous free time), and serendipity. Surfaces unbreakable conflicts (two high-value overlapping talks the model cannot rank) as decisions for the human rather than silently picking, and reports what each choice traded away. Conference-agnostic. Use to turn a preference profile plus a theme map into a day-by-day plan, to resolve overlapping sessions, or to balance a packed vs paced schedule. Trigger keywords - schedule optimization, conference schedule, constraint optimization, overlapping talks, contiguous free time, conflict surfacing, packed vs paced.
127SKILL.mdUpdated Jun 28, 2026
lyndonkl/conf-program-extraction
development
VerifiedTrustedCommunity
Parse a heterogeneous conference program (markdown, HTML, PDF-derived text, or JSON) into normalized event records with per-field confidence scores and independent classification axes (topic, depth, format, prerequisites, recorded, capacity). Detects the program's format before extracting, treats every inferred field as uncertain (present vs inferred vs missing), and flags thin or missing abstracts so downstream enrichment can target them. Conference-agnostic. Use when ingesting a conference or event schedule into a structured store, normalizing a talk/session list, or extracting per-session metadata with calibrated confidence. Trigger keywords - program ingestion, parse schedule, session extraction, event records, conference program, talk metadata, per-field confidence.
127SKILL.mdUpdated Jun 28, 2026
lyndonkl/conf-preference-elicitation
development
VerifiedTrustedCommunity
Build a personalized preference profile from a small number of well-chosen, cluster-grounded questions instead of a long survey. Represents the person's interests as an uncertainty region over the theme map, picks the single highest-information-gain choice-based question (contrasting real talks from different clusters), balances exploiting known interests against exploring uncertain ones, deliberately injects outlier probes to fight selection bias, and stops as soon as the schedule would be stable. Also elicits the user-owned objective weights and hard constraints. Interactive — runs where it can actually ask the person. Conference-agnostic. Use to turn a theme map into a preference profile, to decide what to ask a conference attendee, or to elicit scheduling priorities. Trigger keywords - preference elicitation, ask few questions, information gain, choice-based questions, selection bias probe, objective weights, attendee preferences.
127SKILL.mdUpdated Jun 28, 2026