← ClaudeAtlas

substack-humanizerlisted

Use when a Substack draft, Note, or post reads as AI written, sounds generic, needs a pre-publish review or audit, or the user wants their voice captured from past writing into a voice profile. Not for writing new drafts from scratch (use substack-notes-writer or substack-post-writer).
Arin117Kaushik/substack-skills · ★ 3 · AI & Automation · score 64
Install: claude install-skill Arin117Kaushik/substack-skills
# Substack Humanizer Make a draft sound like the user by removing AI tells, without adding anything the user didn't write. ## Modes | Mode | Trigger | Output | |---|---|---| | rewrite (default) | "fix this", "make it sound human" | Tells found, rewrite, fact trail | | `--mode audit` | "review before I publish", "audit" | Same as rewrite | | `--mode profile` | "learn my voice", 3 to 6 pieces the user wrote | Filled voice profile | ## Rewrite and audit Read `references/voice-rules.md`, `references/anti-fabrication.md`, and `~/.substack-skills/voice-profile.md` if it exists. Output, in this order: **1. Tells found.** One line each: quoted phrase, the voice rule number it breaks, the fix. Check every rule, including dashes (rule 1) and the closing line (rule 10). **2. Rewrite.** Full text. **3. Fact trail.** Every number, name, date, and experience in the rewrite, each with the original line it came from. Anything without a source line gets removed before you show the rewrite. ## The rule that matters most A rewrite **removes**. It never adds experiences. When you cut a vague claim ("studies show readers can tell"), replace it with: - nothing, or - a plainer version of what the user already said, or - a slot: `[a real example of this, if you have one]` Not with a story. "I did it twice and both posts flopped" is fabrication even though it sounds more human. That is the failure this skill exists to prevent. ## Profile mode 1. Read the pieces the user gave. Treat them