Section Break Check

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.

200 stars 25 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill section-break-check
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/section-break-check ~/.claude/skills/section-break-check

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Section Break Check

## Table of Contents

- [The two registers](#the-two-registers)
- [Workflow](#workflow)
- [Worked example](#worked-example)
- [Guardrails](#guardrails)

**Related skills:** Called by Editor in structural pass. Reads `shared-context/style-guide.md` for the break rule.

## The two registers

From `style-guide.md`:

- **Essays (<1500 words, reflective register)**: no H1/H2 in body; use `* * *` between movements.
- **Essays (1500+ words)**: `* * *` preferred; H2 only if structured as a how-to.
- **Methodology / technical posts**: H2 is fine and often necessary.
- **Never use H3 or H4.**

How to detect register:

- **Reflective**: first-person throughout, confession or admission opener, narrative arc, no numbered steps, no code blocks, <2500 words.
- **Methodology**: numbered steps, code blocks, command invocations, technical diagrams, "how to X" or "building Y" framing.
- **Hybrid** (e.g., *Architecture, Not Prompting*): both analytical claim and how-to sections. H2 is acceptable here.

## Workflow

```
Section-break check draft D:
- [ ] Step 1: Detect register: reflective | methodology | hybrid
- [ ] Step 2: Scan for section breaks: count H1s, H2s, H3+, asterisk dividers
- [ ] Step 3: Apply register-appropriate rules
- [ ] Step 4: Flag mismatches
```

### Scoring matrix

| Register | Word count | H2 OK? | `* * *` OK? | Flag conditions |
|---|---|---|---|---|
| Reflective | <1500 | No | Yes | H2 in body → tier-2 |
Read the full skill on GitHub

Details

Skill name
section-break-check
Path
skills/section-break-check/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Section Break Check skill do?

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.

How do I install the Section Break Check 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 Section Break Check popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/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.

Testing & QA25

Academic Letter Architect

200

lyndonkl/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.

Research & Science25

Adr Architecture

200

lyndonkl/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.

Software Development25

Structural Review

200

lyndonkl/claude

Performs pass-1 structural review of a substacker essay draft — argument flow, out-of-order moves, buried topic sentences, missing pivots, weak signposting, paragraph-logic issues. Emits the "Argument flow" and "Structural blockers" sections of the Editor artifact. Use when reviewing a draft's macro-structure before addressing voice, when a draft feels like it meanders, or when the user asks whether the argument lands. Trigger keywords — structure, argument flow, outline, signposting, meandering, pivot, macro edit, substantive edit.

Writing & Content25

Search Corpus

200

lyndonkl/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.

Writing & Content25

Summarize Signal

200

lyndonkl/claude

Given a candidate item from the substacker Trend Scout fetch, WebFetches the full post or arXiv abstract and produces a one-line "teaches X" summary plus signal_type classification (mechanism / empirical / tool / opinion / announcement / benchmark). Distinguishes teaching-content from capability-announcement explicitly. Use during the weekly run, after fetching and before ranking. Trigger keywords — summarize, signal type, mechanism vs announcement, teaching content.

Writing & Content25

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.