DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to write or revise fiction with the Hemingway voice profile with Sepia

Apply the built-in Hemingway voice to a story with an opt-in direct entry.

  • Content
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Voice cloning. The profile imitates a named author's published style, so use it as a technique and do not present the output as that author's writing.

Who it is forA fiction writer who wants a spare, omission-driven style on a new scene or a revision.

The problemGeneric de-AI passes do not give a fiction draft a distinct voice to follow.

The outcomeA scene or revision written under the Hemingway profile, with Sepia stating the profile and how to decline it.

What you need first

  • An Agent Skills-compatible agent, or Claude Code or Codex for the native plugin packaging
  • The complete sepia plugin package installed, since the README says standalone wrapper installation is unsupported
  • A draft file or pasted text to review

Steps

  1. Install the complete Sepia plugin package for your agent.
  2. Run /sepia-hemingway on the scene or draft, or $sepia-hemingway in Codex.
  3. Read the profile notice Sepia prints and decline it if you did not want the voice applied.
  4. Run the review operation to see the voice's known costs that Sepia reports.
  5. Keep the moves you want and revert the rest by hand.

Prompt for your agent

Using the sepia repo, run its hemingway operation on <scene file path>. Expected output: the scene with the Hemingway voice applied and a review of the profile's known costs. Verify that the story's facts and character names are unchanged.

Caveat. The voice-skills interface rests on one blind review experiment that the README calls a worked example rather than measured evidence.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page