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

How to run the structural pass on a long draft or story with Humanizer Stack

Check discourse structure with six audits, then vary the shape so the piece is not a new template.

  • Content
  • Intermediate
  • 45 minutes
  • From the README
  • Claude Code

Who it is forA fiction writer or long-form author whose draft reads as if it explains its theme, resolves every thread, and names every feeling.

The problemSurface edits fix the words but leave the skeleton of the piece intact, and the structure is where the durable fingerprint lives.

The outcomeA structural scan report and a revised draft with one or two interventions chosen on purpose for that piece.

What you need first

  • Claude Code installed, since the passes are packaged as Claude Code Skills
  • git and a terminal to clone the repo and run install.sh
  • Python 3 to run the scanners
  • A draft file in plain text or Markdown to work on

Steps

  1. git clone https://github.com/NulightJens/humanizer-stack.git
  2. cd humanizer-stack
  3. ./install.sh
  4. python3 skills/structural-humanizer/scripts/structural_scan.py draft.md
  5. In Claude Code, send: run the structural pass on draft.md, and read skills/structural-humanizer/references/genre-calibration.md to confirm which audits apply to your genre.

Prompt for your agent

Using the humanizer-stack repo at <repo path>, run the structural_scan.py script on <draft file> and then apply the structural-humanizer skill audits that apply to this genre. Output a revised draft and a list of the audits that changed text. Verify that at most two interventions were applied in this piece and that each one is explained.

Caveat. The study covered roughly 5,000-word fiction, so applying the audits to short nonfiction is an inference; audits 1, 3, 4, and 6 transfer most cleanly.

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