Per Section Tracking
Breaks down weekly and trailing-4-week substacker performance per Substack section, keyed on section tags in corpus/published/ and section-map.md. Reports opens, clicks, subs-attributable-to-section per section with ≥3 posts. Skips if section-map has <2 sections. Feeds Curator with pruning candidates (sections with 4-week median z ≤ -1.0). Use when section-map has ≥2 live sections. Trigger keywords — per-section, section performance, section metrics, section pruning, differential engagement.
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 per-section-trackinggit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/per-section-tracking ~/.claude/skills/per-section-trackingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Per Section Tracking
## Workflow
```
Per week (if ≥2 sections with ≥3 posts each):
- [ ] Step 1: Load section-map.md
- [ ] Step 2: Join CSV posts with corpus/published/{section}/ to map each post to section
- [ ] Step 3: Compute per-section aggregates (mean open rate, click rate, views/send, subs delta)
- [ ] Step 4: Compute trailing 4-week per-section z-score
- [ ] Step 5: Flag sections with median z ≤ -1.0 over 4 weeks → candidate for Curator prune proposal
- [ ] Step 6: Emit per-section table for the weekly report
```
## Skip rule
- If section-map has <2 sections → skip, note "sections not yet established."
- If a section has <3 posts → exclude from per-section table; show in note: "{section} has <3 posts, not enough for section-level stats."
## Output format (weekly-report subsection)
```markdown
## Per section
| Section | Posts (week / total) | Open rate (week / 4w baseline) | Click rate (week / 4w baseline) | Sub delta | 4w z |
|---|---|---|---|---|---|
| kalshi-log | 2 / 6 | 0.54 / 0.51 | 0.06 / 0.05 | +8 | +0.7 |
| agent-workshop | 0 / 7 | — | — | +2 | +0.2 |
```
Narrative: 1-2 sentences per section summarizing what the numbers say (not interpretation — that's attribute-performance's job).
## Guardrails
1. Skip entirely if section-map empty or only one section.
2. Skip any section with <3 posts.
3. Never compare across sections' absolute numbers ("agent-workshop has higher open rate than kalshi-log"). Audiences differ; compare each to its own baseline.Details
- Skill name
per-section-tracking- Repository
- lyndonkl/claude
- Path
skills/per-section-tracking/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Per Section Tracking skill do?
Breaks down weekly and trailing-4-week substacker performance per Substack section, keyed on section tags in corpus/published/ and section-map.md. Reports opens, clicks, subs-attributable-to-section per section with ≥3 posts. Skips if section-map has <2 sections. Feeds Curator with pruning candidates (sections with 4-week median z ≤ -1.0). Use when section-map has ≥2 live sections. Trigger keywords — per-section, section performance, section metrics, section pruning, differential engagement.
How do I install the Per Section Tracking 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 Per Section Tracking 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.
Principle Redesign From First Principles
100adriannoes/awesome-agentic-ai
Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.
One Pager Prd
200lyndonkl/claude
Creates concise, decision-ready product specifications (one-pagers and PRDs) that align stakeholders on problem, solution, users, success metrics, and constraints. Use when proposing new features/products, documenting product requirements, creating concise specs for stakeholder alignment, pitching initiatives, scoping projects before detailed design, capturing user stories and success metrics, or when user mentions one-pager, PRD, product spec, feature proposal, product requirements, or brief.
Prioritization Effort Impact
200lyndonkl/claude
Transforms overwhelming backlogs into clear, actionable priorities by mapping items on a 2x2 effort-vs-impact matrix, identifying quick wins (high impact, low effort), big bets, time sinks, and fill-ins. Use when ranking backlogs, deciding what to do first, prioritizing feature roadmaps, triaging bugs or technical debt, allocating resources across initiatives, identifying low-hanging fruit, evaluating strategic options, or when user mentions prioritization, quick wins, effort-impact matrix, high-impact low-effort, big bets, or "what should we do first?".
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.