paragraph-rhythm-check

$npx mdskill add lyndonkl/claude/paragraph-rhythm-check

Enforce rhythmic paragraph structure to prevent monotony and walls.

  • Detects long runs of similar length and excessive paragraph sizes.
  • Integrates with the Editor's structural pass workflow.
  • Flags violations based on word count thresholds and pivot rules.
  • Outputs tier-2 alerts for rhythm, monotony, and wall issues.

SKILL.md

.github/skills/paragraph-rhythm-checkView on GitHub ↗
---
name: paragraph-rhythm-check
description: Checks paragraph rhythm in a substacker draft — long/short mix, one-sentence paragraph at pivots, no walls, avoid monotony. Flags drafts where >3 consecutive paragraphs share the same length bucket, where the pivot lacks a one-sentence paragraph, or where any paragraph exceeds 120 words. Use in the Editor's structural pass. Trigger keywords: rhythm, paragraph length, wall of text, one-sentence paragraph, pivot, monotone.
---

# Paragraph Rhythm Check

## Table of Contents

- [Length buckets](#length-buckets)
- [Rules](#rules)
- [Workflow](#workflow)
- [Worked example](#worked-example)
- [Guardrails](#guardrails)

**Related skills:** Called by Editor in structural pass. Writes to "Paragraph logic" subsection.

## Length buckets

| Bucket | Word count |
|---|---|
| short | ≤25 |
| medium | 26–80 |
| long | 81–150 |
| wall | >150 |

The writer's voice signature is **long + short mix** with **one-sentence paragraphs at pivots**. Monotone = voice violation.

## Rules

1. **Wall rule**: No paragraph >120 words (wall threshold is slightly below 150 for flagging; >150 is a hard flag). Tier-2.
2. **Monotone rule**: >3 consecutive paragraphs in the same bucket = tier-2 flag.
3. **Pivot rule**: Essays >1500 words should have at least one one-sentence paragraph at a pivot. Absence = tier-2 flag.
4. **Opening short rule**: the opener paragraph is typically short (≤60 words) for punch. A 150-word opening block is a flag.

## Workflow

```
Rhythm check draft D:
- [ ] Step 1: Compute word count per paragraph
- [ ] Step 2: Assign bucket
- [ ] Step 3: Detect monotone runs (≥4 consecutive same bucket)
- [ ] Step 4: Detect walls (>120 words)
- [ ] Step 5: Detect missing pivot in essays >1500 words
- [ ] Step 6: Flag + suggest (split wall / insert pivot / tighten opener)
```

## Worked example

**Draft paragraphs (word counts)**: [62, 58, 71, 63, 68, 72, 180, 45]

**Detections**:
- Monotone: [62, 58, 71, 63, 68, 72] = 6 consecutive medium. Tier-2 flag.
- Wall: paragraph 7 at 180 words. Tier-2 flag.
- Pivot: no single-sentence paragraph in the draft. If total >1500 words → tier-2 flag.

**Suggestions**:
- Insert a one-sentence paragraph at ~paragraph 3 or 4 to mark the pivot.
- Split the 180-word paragraph at the natural semantic break (likely a contrast or a named example).
- Optionally cut one of the middle paragraphs to a single declarative sentence.

## Guardrails

1. Word counts exclude blank lines and code fences.
2. Bullet lists count as their own paragraph unit; don't flag list-adjacent rhythm separately.
3. Series-log posts are often shorter and tighter — relax the pivot rule below 1000 words.
4. If the draft uses `* * *` section breaks, count rhythm within each section separately.
5. Don't propose specific rewrites for rhythm issues — surface the issue; let the writer decide.
6. A 150-word paragraph is a wall only if it lacks internal variation (e.g., long-sentence-after-long-sentence); a 150-word paragraph with internal short sentences is less of a wall.

## Quick reference

- Buckets: short (≤25), medium (26–80), long (81–150), wall (>150).
- Hard flags: wall >120, monotone ≥4 consecutive, missing pivot in essays >1500 words.
- Output: paragraph-logic subsection of structural pass.

More from lyndonkl/claude

SkillDescription
abstraction-concrete-examplesBuilds 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-architectGuides 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-architectureDocuments 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.
adverse-selection-priorProduces a Bayesian prior probability that an offered transaction is +EV for the recipient, given that the counterparty chose to propose it. Applies Akerlof market-for-lemons logic -- if they offered it, they believe it is +EV for them, so the prior that it is +EV for us is materially below 50%. Reusable across trade evaluation, waiver drops (another team dropping a player is also adverse selection), job-offer analysis, M&A, and any "someone offered me this" situation. Use when you receive an unsolicited trade/offer/proposal, analyzing incoming trade prior, evaluating why a counterparty proposed a deal, or when user mentions adverse selection, market for lemons, why did they offer this, incoming trade prior, they proposed it, Bayesian adjustment on received offer.
alignment-values-north-starCreates actionable alignment frameworks that give teams a shared North Star (direction), values (guardrails), and decision tenets (behavioral standards). Enables autonomous decision-making while maintaining organizational coherence. Use when starting new teams, scaling organizations, defining culture, establishing product vision, resolving misalignment, creating strategic clarity, or when user mentions North Star, team values, mission, principles, guardrails, decision framework, or cultural alignment.
analogy-weight-checkFor every analogy in a substacker draft, verifies it carries mechanical weight — the analogy does real work explaining the mechanism, not merely decorates it. Cross-references analogy-catalog.md for novelty (is this analogy reused from a prior post?) and domain fit (biology > organizational > sports preferred; physics/military disfavored). Use whenever an analogy appears in the draft. Trigger keywords: analogy weight, decorative, mechanical weight, reused analogy, catalog check, metaphor check.
answer-uncomfortable-questionTakes one strategic question about substacker ("should we launch paid?", "is this section dead?", "are we writing for the wrong audience?") and produces the mandatory evidence + reasoning + downside triad plus a recommendation. Used 3 times per Growth Strategist review. Trigger keywords: uncomfortable question, strategic question, evidence reasoning downside, triad.
attribute-performanceFor each substacker post that materially over- or under-performs the rolling baseline (|z| ≥ 1.0), produces a plain-English attribution paragraph with calibrated confidence (high / medium / low / unexplained). Considers subject-line effect, topic zeitgeist, external share, day-of-week, length effect, and audience-notes signals. Labels unexplained outliers explicitly rather than fabricating a story. Use after compute-baseline when outlier posts exist. Trigger keywords: attribution, why did this post work, outlier explanation, performance analysis.
auction-first-price-shadingComputes the optimal shaded bid for a first-price sealed-bid auction given a true private value, an estimate of the number of competing bidders N, and a value-distribution assumption. Implements the `(N-1)/N` equilibrium shading rule for uniform private values, adjusts for log-normal or empirical value distributions, layers a risk-aversion adjustment, and caps output against the bidder's remaining budget. Domain-neutral auction theory reusable across fantasy sports (baseball FAAB, NBA/NHL waiver auctions), prediction-market limit sizing, sealed procurement bids, and any blind-bid context. Use when user mentions "first-price auction bid", "sealed bid shading", "(N-1)/N", "FAAB bid amount", "auction shading", "optimal bid first-price", "bid for sealed-bid", "blind bid sizing", or when downstream logic needs a principled shade factor rather than an ad-hoc heuristic.
auction-winners-curse-haircutApplies a Bayesian haircut to a bid valuation for common-value auctions where winning is itself evidence the bidder over-estimated. Takes a raw valuation, a value-type classification (common_value / private_value / mixed), the number of informed bidders N, and a signal-dispersion estimate, and returns an adjusted valuation. Domain-neutral and reusable across fantasy FAAB, prediction markets, M&A bids, ad-auction budgets, and any generic bidding context. Use when user mentions "winner's curse", "common value auction", "valuation haircut", "adverse valuation", "Bayesian bid adjustment", or "over-paying in auction".