mcpbeat

Latex Rhythm Refiner

appautomaton/latex-rhythm-refiner

> Post-process LaTeX project prose to improve readability through varied sentence and paragraph lengths. Removes filler phrases and unnecessary transitions while preserving all citations and semantic meaning. Use after drafting is complete, when sections read as monotonous or blocky.

893 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
392
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/appautomaton/latex-arxiv-SKILL --skill latex-rhythm-refiner

The instruction itself

13 sections, as written by the author

LaTeX Rhythm Refiner

When to Use

  • After LaTeX content generation is complete
  • To improve prose flow and readability in academic documents
  • When sections feel monotonous or blocky

When NOT to Use

  • During initial content drafting
  • For citation verification or addition
  • For technical/structural LaTeX fixes

Core Principles

1. Preserve Citations Exactly

  • Every \cite{...} must remain in place
  • Citations stay attached to their original semantic context
  • Never move a citation to a different claim or sentence meaning

2. Vary Rhythm Stochastically

Sentence length: Mix short (5-12 words), medium (13-22 words), and long (23-35 words) sentences. Avoid consecutive sentences of similar length.

Paragraph length: Alternate between:

  • Short (2-3 sentences) for emphasis or transitions
  • Medium (4-5 sentences) for standard exposition
  • Long (6-8 sentences) for complex arguments

3. Remove Fillers

Eliminate or replace:

  • "in order to" → "to"
  • "it is worth noting that" → (delete or rephrase directly)
  • "due to the fact that" → "because"
  • "in the context of" → "in" or "for"
  • "a large number of" → "many"
  • "in spite of the fact that" → "although"
  • "at the present time" → "now" or "currently"
  • "for the purpose of" → "to" or "for"

4. Minimize Transitions

Remove when structure already implies the relationship:

  • "However," / "Therefore," / "Moreover," / "Furthermore,"
  • "As mentioned above," / "As previously discussed,"
  • "It should be noted that" / "In this regard,"

5. Tighten Prose

  • Prefer active voice; replace vague verbs ("shows", "does", "works") with concrete ones
  • Replace mid-sentence em-dashes with commas, colons, or a new sentence
  • Use semicolons sparingly (at most one per paragraph as a rule of thumb)
  • Avoid repeated sentence openings across adjacent sentences ("This", "In practice", etc.)
  • Replace hedge stacks ("may potentially") with one qualifier
  • Each paragraph: one main idea, clear first sentence
  • Ensure figures/tables are referenced and explained in text

Processing Workflow

Per-Section Refinement

Process one section at a time:

  • Read the section fully to understand context and argument flow
  • Identify all \cite{...} locations and their attached claims
  • Map current sentence/paragraph lengths
  • Refine:
  • Vary sentence lengths (break long chains, combine choppy sequences)
  • Adjust paragraph boundaries for rhythm
  • Strip fillers and unnecessary transitions
  • Verify all citations remain with their original semantic claims
  • Output the refined section

Verification Checklist

Before finalizing each section:

  • [ ] Citation count unchanged
  • [ ] Each citation still supports its original claim
  • [ ] No 3+ consecutive sentences of similar length
  • [ ] Paragraph lengths vary
  • [ ] Filler phrases removed
  • [ ] Unnecessary transitions eliminated
  • [ ] Technical accuracy preserved

Constraints

  • Do not add, remove, or relocate citations
  • Do not change technical claims or data
  • Do not alter LaTeX commands, environments, or structure
  • Do not modify figure/table references or captions
  • Do not expand abbreviations or change terminology

How to use it

Copy the folder

Take appautomaton/latex-rhythm-refiner from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.