Install any skill in seconds. Free to start, no credit card required.
Get Started Free →realrossmanngroup/rossmann-voice
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.
Passed 20 of 22 test cases with the skill, and 3 of 22 without it.
and 13 more in the full report
17 fixed3 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
Write a brief commentary contrasting a console manufacturer's official $250 out-of-warranty mainboard swap quote against an independent repair shop replacing a damaged HDMI custom socket for $15 in parts. Maintain a declarative tone with no rhetorical questions or profanity.
| Checked | Without skill | With skill |
|---|---|---|
| Uses '&' instead of 'and' as default conjunction. | Missed | Passed |
| Avoids rhetorical questions. | Passed | Passed |
| Avoids profanity in new prose. | Passed | Passed |
The instructions your model reads when the skill loads.
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.
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.
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).)
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).)
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).)
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.)
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.)
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.")
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.)
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.
test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.