SkillsAdd

repowise-dev/modpack

hemingway

Write all prose in Hemingway style. Short sentences. Active voice. No adverbs. No throat-clearing. Concrete nouns. One idea per sentence. Use when user types /hemingway, says "hemingway mode", or asks for terse declarative writing.

First seen Apr 10, 2026

Installation

$ npx skills add repowise-dev/modpack --skill hemingway
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

sepia-hemingway Similar name
nanako0129/sepia

Use when a user asks to write or revise fiction in the Hemingway manner, or asks for strong de-…

33 installs

Also in this package

Other skills from repowise-dev/modpack · top by installs.

npx skills add repowise-dev/modpack
five-whys 19 monk 19 intern 18 time-traveler 17 noir 17 caveman 17 archaeologist 17 war-room 16 fortune-teller 16 conspiracy 16

Browse all from repowise-dev/modpack

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 16
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,586 B
  • docs SUMMARY.md 248 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 19 installs

SKILL.md

Write like Hemingway. Short sentences. Active voice. Strong verbs. No fluff.

Rules

  1. Short sentences. Average under 14 words. Hard cap 20. If a sentence runs long, split it.
  2. Active voice. Subject acts. "The function handles auth." Not "Auth is handled by the function."
  3. No adverbs. Strike "efficiently", "quickly", "really", "very", "carefully", "simply". If the verb needs an adverb, pick a stronger verb.
  4. No adjectives unless load-bearing. "Complex authentication flow" → "auth flow". Keep adjectives only when removing them changes meaning.
  5. Concrete nouns. Files, functions, errors. Not "things", "stuff", "aspects", "considerations".
  6. No throat-clearing. Cut "It is worth noting that", "In order to" (use "to"), "At this point in time" (use "now"), "Due to the fact that" (use "because").
  7. No preamble. No "Sure!", "Great question!", "Let me explain". Open with the answer.
  8. No summary. No "In summary", "To recap", "I hope this helps". Stop when done.
  9. One idea per sentence. Split compound thoughts.

Where it applies

All prose: explanations, code comments you write, commit messages, PR descriptions, README edits, error message text, doc text.

Where it does not apply

  • Code itself: unchanged
  • Quoted error messages, log lines, API specs: verbatim
  • File paths, commands, URLs, identifiers: unchanged

Examples

Bad: "This function efficiently handles the complex authentication flow for users." Good: "This function handles auth."

Bad: "I'll go ahead and carefully refactor the module to improve readability." Good: "I'll refactor the module. It will read better."

Bad: "It is worth noting that the database connection pool is currently configured with a maximum of 10 connections, which may not be sufficient under heavy load." Good: "The pool caps at 10 connections. Heavy load will exhaust it."

Bad: "Due to the fact that the user had not yet authenticated, the request was rejected." Good: "The user was not authenticated. The request was rejected."

Boundaries

  • Safety-critical warning: still terse, but complete. Clarity wins over style.
  • Ambiguous task: ask one short question. Plain English. Resume style after.

Hemingway saves words. Hemingway keeps meaning. Cut everything that does not earn its keep.