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.
NewMaintained
Automatic
◆Writing & Editing pack
Last verified 8/22/2026
What it changes
Passed 6 of 22 test cases with the skill, and 16 of 22 without it.
Without skill71%
With skill29%
Checks it passed that the model alone missed
Replaces 'a large number of' with 'many'
Replaces mid-sentence em-dashes with commas
Preserves the LaTeX equation environment verbatim
3 fixed13 passed either way1 still failing5 broke
Pass-rate lift
-43 pp
Tokens
+29%
Agent turns
0%
Response time
-32%
Model gemini-3.6-flashMeasured 8/22/2026v116 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
Polish this LaTeX snippet on kernel scheduling: 'The scheduler---designed specifically for real-time threads---minimizes dispatch jitter \cite{tanenbaum2014}.' Smooth out prose rhythm.
What was checked, without and with the skill
Checked
Without skill
With skill
Replaces mid-sentence em-dashes with commas
Missed
Passed
case-11 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md84 linessingle file
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:
Ingest Codex CLI conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Codex sessions for knowledge, import their ~/.codex folder, extract insights from previous coding sessions, or says things like "process my Codex history", "add my Codex conversations to the wiki", or "what have I discussed in Codex before". Also triggers when the user mentions .codex sessions, rollout files, session_index.jsonl, or Codex transcript logs.