hemingway-tonality
Skill181 starsChanged 9 months agoMITView on GitHub
Rewrite sales copy in a plain, declarative, Hemingway register — short sentences, concrete words, no hedges. Use when the user asks for copy to be tighter, plainer, more direct, or "like Hemingway". Not for warm nurture content or long-form storytelling.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
No hedges: Delete "just", "really", "very", "quite", "actually", "I think", "I believe", "sort of", "kind of", "in order to".
- Distinctive: line 23
End on the ask or the fact: Not on a pleasantry.
- Distinctive: line 28
Read the whole piece once.
- Distinctive: line 30
Read the rewrite aloud in your head.
- Distinctive: line 32
If the original was under 60 words already, say so and change only what the rules demand.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hemingway Tonality
A final pass for emails, LinkedIn posts, proposals and call scripts. The goal is not to sound like a novelist. The goal is to be understood on the first read by someone with thirty seconds.
Rules
- Short sentences. Average under fifteen words. One idea per sentence. If a sentence has a comma and an "and", it is probably two sentences.
- Concrete nouns. "Pipeline" not "revenue motion". "Reps" not "sales resources". "Email" not "touchpoint".
- Strong verbs. Replace "is able to", "helps to", "serves to" with the verb itself. "Cuts ramp time" not "helps to reduce ramp time".
- No hedges. Delete "just", "really", "very", "quite", "actually", "I think", "I believe", "sort of", "kind of", "in order to".
- No stacked adjectives. One adjective if it carries information. Zero if it does not. "Innovative, seamless, powerful platform" becomes "platform".
- No abstractions where a number will do. "Faster" becomes "two days instead of nine". If there is no number, say what happens.
- Active voice. "We ship Tuesday" not "Shipping is scheduled for Tuesday".
- Cut the first sentence. It is usually a warm-up. Check whether the second sentence is the real start.
- End on the ask or the fact. Not on a pleasantry.
- Keep the meaning. This is a register change, not an edit of substance. Do not remove a claim, a number or a commitment. Flag anything you were tempted to cut for substance reasons.
Process
- Read the whole piece once.
- Rewrite top to bottom applying the rules.
- Read the rewrite aloud in your head. Anything you stumble on, split or cut.
- Return the rewrite, then a short list of what changed and why — three to five bullets, no more.
- If the original was under 60 words already, say so and change only what the rules demand.
Before / after
Before (71 words): I hope this email finds you well! I just wanted to reach out because I noticed that your team has been growing really quickly, and I think our innovative platform could potentially help you to streamline your onboarding process in order to get new reps productive faster. Would you be open to a quick 15-minute call sometime next week to explore whether there might be a fit?
After (34 words): You hired eleven reps in March. Most teams lose the first six weeks of a cohort to account research. We cut that to two for Loom and Ramp. Is ramp time a number you track?
What changed: cut the greeting and the "I noticed" frame; replaced "growing quickly" with the number; replaced "streamline onboarding" with what happens; replaced the meeting request with a one-word question.
In this repository3 other files it gives its agents.
- public/llms.txtllms.txt
- cold-email-fundamentalsSkill
- meddic-discovery-liteSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

