What do you want to do?
4 use cases
-
Strip AI tells from a blog post before publishing
Run the word-level pass and scanner on an AI-drafted post so it reads like a person wrote it.
- Humanizer Stack
- Claude Code
- Content
- Intermediate
View prompt
Using the humanizer-stack repo at <repo path>, run python3 scripts/copy_scan.py on <draft file> and then apply the humanizer skill to fix every flagged word-level tell. Output the revised file and any remaining scanner hits. Verify that the rerun of the scanner shows no hits except lines the author marked copy-ignore.
-
Block AI-tell copy from merging with a strict scan
Use the scanner's exit codes and JSON output to fail a check when a draft still has copy tells.
- Humanizer Stack
- Content
- Advanced
View prompt
In the humanizer-stack repo at <repo path>, run python3 scripts/copy_scan.py --strict on <copy file> and capture the exit code and the output from --json. Report each hit with its line number and whether the file passed. Verify that a file with no hits returns exit code 0.
-
Run the structural pass on a long draft or story
Check discourse structure with six audits, then vary the shape so the piece is not a new template.
- Humanizer Stack
- Claude Code
- Content
- Intermediate
View prompt
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.
How to use Humanizer Stack
- Check you have what it needs: 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.
- Open NulightJens/humanizer-stack on GitHub and read the README and license.
git clone https://github.com/NulightJens/humanizer-stack.gitcd humanizer-stack./install.shpython3 scripts/copy_scan.py draft.md
These steps come from our top use case, Strip AI tells from a blog post before publishing, which also has a copy-paste agent prompt.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeAbout this repo
- Who it is forWriters, marketers, and course creators who publish AI-assisted copy and want it to read as if a specific person wrote it.
- Why it is hot
- LanguagePython
- Sourcegithub.com/NulightJens/humanizer-stack · Back to Hot repos
Requirements
- 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
Maintain Humanizer Stack? Add the Featured on Deduped badge
Paste this into your README:
[](https://dedupedai.com/use-cases/nulightjens-humanizer-stack/?ref=badge)
Questions about Humanizer Stack
What is Humanizer Stack?
A two-pass set of Claude Code Skills and Python scanners that removes AI writing tells from outward-facing text, first at the word level and then at the structural level. It is an open-source project on GitHub: https://github.com/NulightJens/humanizer-stack.
Who is Humanizer Stack for?
Writers, marketers, and course creators who publish AI-assisted copy and want it to read as if a specific person wrote it.
What can I do with Humanizer Stack?
4 use cases so far, for example: Strip AI tells from a blog post before publishing; Block AI-tell copy from merging with a strict scan; Run the structural pass on a long draft or story. Each has steps and a copy-paste agent prompt.
What do I need to run Humanizer Stack?
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.
What are alternatives to Humanizer Stack?
Other hot AI repos in Content: Voice Studio, Anatomy, Comfy UI, Hyperframes, Earshot.
Is Humanizer Stack safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.