lyndonkl/skills/section-break-check
skills/section-break-check/SKILL.md
--- name: section-break-check description: 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. --- # Section Break Check ## Table of Con
$ install --global
skillsauthnpx skillsauth add lyndonkl/claude skills/section-break-checkInstall 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:21 AM142.8s1 file scanned
SKILL.md
- name:
- section-break-check
- description:
- 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.
Section Break Check
Table of Contents
- The two registers
- Workflow
- Worked example
- 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 |
| Reflective | 1500–2500 | Avoid | Preferred | Frequent H2 → tier-2 |
| Hybrid | any | Yes | Yes | Mixing both in same section → tier-2 |
| Methodology | any | Yes | Rare | H3+ usage → tier-2 |
Worked example
Draft 1: A 1200-word reflective essay on pathology AI with H2s (## The Training Set, ## The Failure, ## What I Learned).
Flag: (Tier-2) H2s in a short reflective post break register. Essays under 1500 words use * * *. Rewrite: replace each ## Heading with * * * and fold the heading concept into the first sentence of the new movement.
Draft 2: A 3000-word methodology post on building an agent system with no H2s, only * * * dividers.
Flag: (Tier-2) Methodology register typically uses H2 for navigation. Consider H2 for each major step of the build. Not blocking, but worth the writer's attention.
Draft 3: A 1800-word essay mixing analysis with a concrete build walk-through, with both H2 and * * * (some sections have H2, some have asterisks).
Flag: (Tier-2) Mixing within one essay breaks register. Pick one. Rewrite suggestion: use H2 for the methodology sections and * * * for the analytical transitions — but be consistent within each register.
Guardrails
- Section-break issues are tier-2. Writer can publish anyway; it's a craft miss, not a voice violation.
- Don't flag H1 in the draft — H1 is the post title and belongs there.
- Don't flag section breaks in code blocks or quoted content.
- H3+ is always flagged (style-guide rule: "Never use H3 or H4").
- Series-log posts (frontmatter
series: {slug}) typically use* * *— if a series post uses H2, flag softly. - Don't propose a full restructure; suggest the one change (replace H2 with
* * *or vice versa) and let the writer execute.
Quick reference
- Detect register → apply rule.
- Two tolerated registers: reflective (asterisks) and methodology (H2).
- Mixed within one essay = tier-2 flag.
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