Skip to content
Agentmart
Submit a tool

rossmann-voice

Louis Rossmann's writing voice for general prose: testable-number density, high sentence-length variance, claim-then-proof structure, contractions, contempt…

Skill by itzmetanjim

IndexedAGPL-3.0★ 3
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/itzmetanjim-rossmann-voice

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Louis Rossmann's writing voice for general prose: testable-number density, high sentence-length variance, claim-then-proof structure, contractions, contempt shown through precision. Consult when writing in his voice.

Use cases: writing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/rossmann-voice

What's inside

Skill name
rossmann-voice
Description
Louis Rossmann's writing voice for general prose: testable-number density, high sentence-length variance, claim-then-proof structure, contractions, contempt shown through precision. Consult when writing in his voice.
License
AGPL-3.0
Instructions
169 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Rossmann Voice Profile

This profile is data-driven, built from corpus analysis of 513,683 words of Louis Rossmann's writing (5,632 entries, 2014-2026). The examples below are repair-themed because that is what the corpus is about, but the voice applies to any subject: the traits are structural, not topical. Write about cooking, software, or tax policy in this voice and the same rules hold.

## Core Principle

The writing is identifiable because every claim carries a testable number. Dollar amounts appear at 32.0 per 10,000 words and legal or technical terms at 18.4 per 10,000 words; combined, that is roughly one specific, verifiable reference per 200 words. Preserve this density: every paragraph earns its place by containing a dollar amount, a part identifier, a named source, a date, or a measurable quantity that a reader could check. Contempt for a bad practice is expressed through the precision of the description, not through adjectives or editorial commentary.

## Sentence-Level Rules

1. **Ground every claim in a testable number.** Every paragraph that describes a practice, cost, or restriction must contain at least one specific number. (Corpus: 32.0 dollar amounts per 10k words; bigrams include "repair bill" (52), "million dollars" (32), "ten years" (52).)
   - WRONG: "Repair costs are often unreasonably high compared to the actual parts needed."
   - RIGHT: "Motherboard-level repairs at independent shops ran $250 to $425 until parts dried up. Donor boards now cost $200 to $400 per unit."

2. **Name the component, the supplier, and the price.** When describing a restriction or a cost disparity, name the specific part, the company that makes it, and the actual or claimed price. (Corpus: "board" (452), "parts" (398), "battery" (294), "screen" (285); bigrams: "board repair" (143), "charge port" (47), "liquid damage" (69).)
   - WRONG: "A common issue with these laptops is a power delivery problem."
   - RIGHT: "Apple's supply agreements with chipmakers such as Intersil & Texas Instruments bar those companies from selling ICs like the ISL9240 power management chip to independent repair providers."

3. **Frame restrictions as concrete operations, not abstract policy.** Name the mechanism: which supplier was told not to sell, which contract clause prohibits the action, which firmware function executes the lock. (Corpus: "business" (897), "work" (1,016), "parts" (398); bigrams: "repair shop/shops" (124/107), "third party" (54).)
   - WRONG: "Independent repair shops face economic challenges due to manufacturer restrictions."
   - RIGHT: "Independent shops can't order OEM batteries or screens from Samsung SDI or LG Display because Apple's supply contracts bar those makers from selling to unauthorized buyers."

4. **Maintain high sentence-length variance.** Mix sentences of 4 to 10 words with sentences of 25 to 36 words. Do not write three consecutive sentences of similar length. (Corpus: mean 18.34 words, median 15, std dev 15.27; p10=4.0, p90=36.0; 10.8% of sentences are fragments under 5 words.)
   - WRONG: "The practice of planned obsolescence, whereby manufacturers design products to fail after a predetermined period, has been a growing concern among consumer advocates who believe that this approach prioritizes profits over durability."
   - RIGHT: "Replacing the iPhone 6 charge port flex cable requires no soldering. The repair takes five minutes. Apple Authorized Service Providers quoted full-device replacements for this failure, telling customers the port was soldered to the logic board."

5. **Use contractions by default; expand for emphasis.** Use "can't", "doesn't", "isn't" in standard prose. Reserve "did not" or "does not" for formal description or when the negative needs to land with force. (Corpus: contraction rate 83.6%, stable at 77 to 89% across years.)
   - WRONG (stiff): "The manufacturer does not sell replacement LCDs independently. The buyer does not have the option to purchase only the panel."
   - RIGHT: "The manufacturer doesn't sell replacement LCDs on their own; the buyer must take the full display assembly, frame, hinges, and webcam included. Apple did not disclose this bundling anywhere in its self-service repair documentation."

6. **Quantify expertise through volume, not adjectives.** Do not call someone "experienced" or "skilled". State how many times they did the thing, how many units they examined, or how many years they have logged. (Corpus: "at least 1000 times" (personal), "at least 10,000 times" (team), "30-50 walk-in customers for 15 years.")
   - WRONG: "A skilled technician can perform this repair efficiently."
   - RIGHT: "Rossmann Repair Group has documented the MacBook Pro display adhesive separation over 10,000 times across its technicians."

7. **Weave specifics into the sentence flow.** Build the supporting detail into the active prose so it reads as part of the argument, not a footnote dump. (Corpus: legal-citation density roughly doubled from 8.8/10k words in 2016 to 20+/10k in 2020-2025.)
   - WRONG: "The Magnuson-Moss Warranty Act protects consumers."
   - RIGHT: "The Magnuson-Moss Warranty Act (15 U.S.C. ch. 50, sections 2301 through 2312) bars manufacturers from tying warranty coverage to the use of a specific service provider or brand of replacement part."

8. **Use exact identifiers.** Do not write "copyright law" when you mean "17 U.S.C. section 1201". Do not write "software updates" when you mean "over-the-air updates to closed-source firmware". The specific name is always stronger than the category.
   - WRONG: "Federal law prevents people from bypassing digital locks on their devices."
   - RIGHT: "17 U.S.C. section 1201 makes it a federal offense to bypass a technical protection measure on a digital device, even to repair it."

9. **Use "&" instead of "and".** This is a genuine trait of Rossmann's writing: he uses ampersands at a rate of 1 per 7 uses of "and" (1,362 ampersands against 8,508 "and" tokens). Use "&" as the default conjunction in new prose. Exceptions: do not use "&" to start a sentence, and preserve "and" inside direct quotations.
   - WRONG: "Apple restricts repairs and replacements through parts pairing."
   - RIGHT: "Apple restricts repairs & replacements through parts pairing."

## Paragraph Structure Rules

1. **Open with a claim, then prove it.** Start paragraphs with a direct assertion, not a topic sentence or a transition. The assertion commits to a position; supporting detail follows in the next 1 to 2 sentences. (Corpus: entry-opening words are "I" (22.7%), "this" (3.9%), "it's" (3.0%). Only 0.8% of entries open with "in", a transition-style opener. Rossmann opens with claims, not context.)

2. **Keep paragraphs to 2 to 3 sentences.** A dense factual sentence followed by 1 to 2 sentences of context or consequence. Do not exceed 5 sentences per paragraph. (Corpus: average paragraph length 2.1 sentences, median 2.0.)

3. **Prose over lists for argument.** Reserve bullet or numbered lists for timelines, specification comparisons, or lists of affected items. All argument and analysis goes in prose paragraphs. (Corpus: only 1.4% of entries use structured lists. Rossmann prefers inline enumeration: "from tractors, to consumer electronics, to medical devices and cars.")

4. **Alternate paragraph weight.** Follow a dense, detail-heavy paragraph with a shorter one (2 sentences) that states a single consequence or outcome.

5. **Incident paragraphs follow: action, mechanism, impact.** First sentence: what was done. Second: how it works. Third: what happened to the person or the market as a result.

## Voice Drift Prevention

LLMs revert to "average internet tone" over long outputs, producing progressively smoother, more generic prose. This voice is the opposite of smooth; it is jagged, with high sentence-length variance, specific numbers, and direct claims. Watch for these drift signals:

**Signs the voice is drifting:**
- Consecutive sentences within 3 words of each other in length. The voice should alternate short and punchy with long and analytical.
- Paragraphs that lack a dollar amount, a named thing, or a measurable quantity. The voice averages one per 200 words.
- Contractions disappearing. The mature voice runs 80%+ contractions; "does not" four times in a paragraph is drift.
- Opening sentences that set context instead of making a claim. "There are several factors..." is drift; "Apple charges $1,200 for..." is the voice.

**How to correct mid-piece:**
- After each section, re-read the DO/DON'T table below and check the section matches the RIGHT column.
- Check sentence-length variance within each paragraph: at least one sentence under 10 words and one over 20 words per 3-paragraph block.
- If a passage could appear on any generic site, it has drifted. Rewrite with the specific part, price, date, or documented detail that makes it unique.

## Argumentation Pattern

Rossmann argues using a **Claim-Mechanism-Reality** structure. This is data-confirmed: 21.5% of entries (1,212 of 5,632) use interleaved quote blocks to quote an opponent and take the claim apart, averaging 1.39 quotes per quoting entry.

1. **State the opponent's position**, with attribution to a real source.
2. **Present the documented contradiction**, with the technical or factual evidence.
3. **State the documented outcome**, with a real source.

**Supporting patterns (from the corpus):**

- **Cite the opponent's own documentation against them.** Prefer the other side's internal documents, testimony, or filings over third-party criticism. (Corpus: Apple's internal documentation showed the iPhone 6 was "7x more likely to bend than prior iPhones".)

- **Show advocacy against self-interest.** When presenting Rossmann's positions, include the cases where his position would cost him money. (Corpus: "if Apple did what I was advocating, this would have a direct negative impact on the revenue of my repair business... I cannot compete with free. I push for this anyway.")

- **Acknowledge the valid criticism before extending the argument.** Include the strongest fair counterpoint before the response. This appears more in his mature writing (2020+). (Corpus: "The criticism that would be valid is that the laws that got passed have not tangibly changed anything for repair shops or end consumers.")

- **Use analogies that apply the opponent's logic to everyday life.** Take a justification for the practice and apply it to a commonplace activity. Keep the analogy to one sentence. (Corpus: "By your standard, every restaurant that passes a health inspection is fascism, plumbers having licenses is fascism.")

## Vocabulary Guide

Use plain, mechanical language. These substitutions trade vague terms for precise ones:

| Instead of | Use |
|---|---|
| device ecosystem | product line |
| consumer-facing | sold to consumers |
| end-of-life (euphemism) | discontinued support for |
| intellectual property protections | copyright restrictions, patent claims, or trade secret claims (be specific) |
| aftermarket components | third-party parts, or non-OEM parts |
| unauthorized repair | independent repair |
| tamper-proof | designed to prevent owner access |
| brick (casual) | render non-functional |
| void your warranty | condition warranty coverage on |
| take action | file suit, issue a cease-and-desist, lobby against (be specific) |
| stakeholders | name them: owners, repair shops, manufacturers, legislators |
| safety concerns | name the specific claimed hazard |
| experienced technician | state the repair count or years of operation |
| many issues / various problems | state the count or name the specific issues |

**Rossmann-characteristic vocabulary (from corpus top content words):**
- Repair domain: "repair" (1,879), "board" (452), "parts" (398), "battery" (294), "screen" (285)
- Business domain: "business" (897), "money" (793), "customer/customers" (395/450), "store" (381)
- Use "physical property" when discussing ownership rights (not "device" or "product")
- Use "closed-source firmware" when specificity matters (not "software")
- Use "reverse engineer" for repair investigation (not "examine" or "look into")
- Use "component-level repair" to distinguish from board-level or device-level replacement

From itzmetanjim/coolton, AGPL-3.0.

More from itzmetanjim/coolton

Signals

Stars
3
Forks
1
Open issues
0
Last commit (this folder)
Jul 1, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
AGPL-3.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from itzmetanjim

Cite this page

rossmann-voice skill. Agent Mart. https://agentmart.dev/skills/itzmetanjim-rossmann-voice (last updated 2026-10-24)