Skip to content
Automation Club
  • LinkedInThe rewriteExample output

    Acme Studio

    Lighting does not have to be complicated. Many creators think they need expensive gear to look professional. They do not. Last month we helped Northwind Coffee shoot their entire product range. The only lighting we used: → one desk lamp as the light → one sheet of white card as the reflector The photos looked professional. A setup like this costs less, and it keeps the shoot simple. What lighting setup do you use: one lamp, or a full kit?

    Made with Claude Code · Skill

    LinkedIn · Social post

    The rewrite. An AI draft rewritten in the voice of Acme Studio, a made-up studio, learned from three of its posts. The draft is in the inputs.

  • MarkdownWhat changed, and what to checkExample output

    What changed, and what to check


    What changed

    • Removed every emoji, the exclamation marks, the capitals on "ONE" and the ✅ checklist. Your posts use none of them.
    • Cut the AI openers and shapes: "In today's fast-paced world", "here's the thing", "The result?" and "It's not just about X, it's about Y".
    • Cut the inflated words: "stunning", "truly elevated", "unlocking", "transform your content game", "endless possibilities".
    • Applied your habits: the point in the first line, short sentences, no contractions, and "one" in a short arrow list after a colon.
    • Swapped "Let us know in the comments" for one closing question with two answers, the way you end your posts.

    Flagged

    • "Truly elevated their brand": I left this out because nothing in the draft backs it up. If Northwind told you something specific about the photos, add that instead.
    • "Creativity, simplicity, and consistency": I kept cost and simplicity, which the shoot shows. Creativity and consistency had nothing behind them, so only add them back if you can say what changed.
    • Northwind Coffee: ChatGPT sometimes fills in client stories, so check the details before you post (last month, the entire range, one lamp, one card). Also make sure the client is happy to be named.
    Made with Claude Code · Skill

    Markdown · Document

    What changed. The list the skill gives after every rewrite, including the details it flags for you to check.

  • MarkdownVoice profile: Acme StudioExample output

    Voice profile: Acme Studio


    Shape

    • Typical length: short, about 40 to 125 words per post.
    • Typical sentence length: mostly 5 to 15 words. The longest is 19: "We record one long video at the start of each month, and everything else comes out of that recording:" Some lines are fragments: "Fewer posts, more replies."
    • Typical paragraph length: one to three sentences, often a single sentence on its own line.
    • How a piece usually opens: one short line that stands alone. It is the situation ("For a year we posted every single day."), the point ("Posting every day made our content worse, not better.") or a setup line ending in a colon ("The one recording habit that made our videos easy to cut up:"). No greeting, and no question as the opener.
    • How a piece usually ends: on what you do now and what it changed, for example "We post less now, and we hear back more." and "We now check every answer for that one sentence before we hit record." The longest post then adds one question to the reader.
    • Lists or no lists, and how they are marked: one list across the three posts, in the longest one. A colon introduces it, and each item starts with an arrow, lowercase, no full stop: "→ the short clips", "→ the carousel".

    Words

    • Words and phrases they use often: "one" (eight times, including "one thing", "one afternoon", "one sentence", "one video a month"). "the point". "now" for the after part ("Now we record", "We now check"). Plain words that move the story along: "For a year", "By the end", "So we changed one thing". You also reuse your own lines word for word across posts: "to fill a slot, not because we had something to say", "worse, not better", "a post on its own".
    • Words they never use, judging by the samples: marketing terms. Where others would write "repurpose", you write "cut up" and "everything else comes out of that recording". Where others would write "engagement", you write "replies" and "hear back".
    • First person: "we" only ("we posted", "our videos"). "I" is not in the samples.
    • How they address the reader: mostly you tell your own story with "we". You switch to "you" for the rule ("Say the point in one sentence before you explain it.") and for the closing question.
    • Contractions: none. You write "If you cannot" and "is not ready", not "can't" or "isn't".

    Punctuation and format

    • Exclamation marks: none.
    • Questions: one in three posts, as the last line, offering two answers: "How do you plan your content: day by day, or in batches?"
    • Emojis: none. No hashtags either.
    • Dashes, brackets, colons: no dashes, no brackets. Colons are a favourite: before a list, before a rule ("The rule that makes it work: say the point..."), at the end of an opening line, and inside a question. Lowercase after a colon in the middle of a sentence.
    • Capitals for emphasis: none.
    • Numbers: written as words, no digits or percentages: "a year", "one afternoon", "one video a month".

    Tone

    • Three words for the tone: plain, candid, practical. You admit what went wrong ("nobody on the team wanted to open the content calendar") and finish with something the reader can use.
    • How they make a point: problem, one change, result. Usually point first (posts 2 and 3), sometimes story first (post 1). Contrasts come in pairs: "worse, not better", "Fewer posts, more replies", "If you can do that... If you cannot...". The proof is your own experience, not numbers.
    • How direct they are when asking for something: gentle. The only ask is one open question at the end. No "comment below", no "follow", no links. How you ask for a sale or a sign-up: not in the samples.

    Never do

    Three short posts is a small base, so treat these as strong patterns rather than proven rules:

    • No exclamation marks, emojis, hashtags or dashes.
    • No contractions.
    • No hype. Results are stated small and concrete: "we hear back more", not a big claim.
    • No statistics or digits.

    Does this sound like you? Change anything that does not.

    What I could not learn from these: all three posts are on one topic and all use "we", so I do not know how you sound as "I", in an email, or when you are selling something. If you have one or two samples like that, paste them and I will fill in those lines.

    Once it looks right, keep it: paste the profile into your business profile, a Project's instructions or a note. Then any new chat can use it without the samples, and you can paste a draft and ask me to make it sound like you.

    Made with Claude Code · Skill

    Markdown · Document

    The voice profile. Built on the first run from three posts, every line pointing to something in them. You keep it for next time.

Works with

  • Claude
  • Claude Code
  • ChatGPT
  • +18 more

Not affiliated with or endorsed by the companies shown.

Make AI drafts sound like you

Show it three things you wrote, then turn any AI draft into something that sounds like you, with the same facts.

Version 1.0Updated 12 Oct 2026

Needs access to
None
Permissions
None
Time to result (our estimate)
5 minutes to set up, 2 minutes a run

Example

Example session

  1. You

    Learn my voice from these three LinkedIn and Threads posts. I wrote them myself.

  2. Your AI

    Here is your voice profile, built only from these three posts. Each line points to something you wrote.

  3. You

    Looks right. Now rewrite this draft ChatGPT wrote for our LinkedIn.

  4. Your AI

    Northwind Coffee: ChatGPT sometimes fills in client stories, so check the details before you post (last month, the entire range, one lamp, one card). Also make sure the client is happy to be named.

What comes out
LinkedInThe rewriteExample output

Acme Studio

Lighting does not have to be complicated. Many creators think they need expensive gear to look professional. They do not. Last month we helped Northwind Coffee shoot their entire product range. The only lighting we used: → one desk lamp as the light → one sheet of white card as the reflector The photos looked professional. A setup like this costs less, and it keeps the shoot simple. What lighting setup do you use: one lamp, or a full kit?

Made with Claude Code · Skill

Fit

About this item

AI drafts give themselves away: the same openings, the same three-part lists, words nobody says out loud. This skill learns how you actually write from three or more of your own posts, saves that as a voice profile, and rewrites any draft to match it.

The facts, numbers and offers stay exactly as they were. Only the voice changes. The example rewrites an AI draft for Acme Studio, a made-up content studio, using three of its past posts.

What you get

  • A voice profile built from your own writing, to keep and reuse
  • Any AI draft rewritten in your voice, with the facts unchanged
  • A short list of what changed and why

Good fit

  • Creators and founders who use AI for drafts and rewrite every one by hand
  • Teams who want posts to sound like one person

Not for

  • Passing off AI writing where it is not allowed, such as school work
  • Writing from scratch with no draft

Who it is for

How to use

How to use it

In Claude

  1. Download the skill zip.

  2. In Claude on the web or the desktop app, open Settings, then Capabilities, and turn on Code execution and file creation. On a Team or Enterprise plan, an owner turns this on first.

  3. Open Customize, then Skills. Choose +, then Create skill, then Upload a skill, and pick the zip.

In Claude Code

  1. Download and unzip the skill.

  2. Move the sound-like-you folder into your Claude Code skills folder.

    macOS and Linux
    ~/.claude/skills/sound-like-you/
    Windows
    %USERPROFILE%\.claude\skills\sound-like-you\
  3. Start a new Claude Code session. It loads the skill when the task needs it.

In ChatGPT

  1. Download and unzip the skill.

  2. In ChatGPT, choose New project in the sidebar.

  3. Open Project settings from the project menu and paste SKILL.md from the sound-like-you folder into its instructions.

  4. Add the skill's other files (anything in its references or assets folder) to the project. Then chat inside the project.

Same steps in

  • Cursor
  • Codex
  • Gemini CLI
  • GitHub Copilot
  • VS Code
  • Amp
  • Goose
  • OpenCode
  • Junie
  • Roo Code
  • Kiro
  • Letta
  • Manus
  • OpenClaw
  • Hermes
  • Muse
  • Dots
  1. Download and unzip the skill.

  2. Move the sound-like-you folder into your skills folder.

    macOS and Linux
    ~/.agents/skills/sound-like-you/
    Windows
    %USERPROFILE%\.agents\skills\sound-like-you\
  3. Start a new session in your AI tool. It loads the skill when the task needs it.

In Grok

  1. Download the skill zip.

  2. Add the zip in the skills or project settings of Grok.

Trust

What's inside

  • sound-like-you folder
    • references folder
      • ai-tells.md1.7 KB
      • voice-profile.md859 B
    • SKILL.md2.6 KB
First lines of sound-like-you/SKILL.md
---
name: sound-like-you
description: Learns how the user writes from three or more of their own posts or emails, saves it as a voice profile, then rewrites AI drafts so they sound like the user. Use when the user asks to make a draft sound like them, sound more human, match their voice or tone, or remove the AI feel from a piece of writing.
license: Proprietary. Automation Club members only.
metadata:
  automationclub-slug: sound-like-you-skill
  automationclub-version: '1.0'
---

# Sound like you

Two jobs: learn the user's voice once, then rewrite drafts in it. Keep every fact and claim in

Permissions required

None

Requirements

You bring

  • Three or more posts or emails you wrote yourself, without AI
  • The AI draft you want to fix
  • Optional first pass: Humanizer (github.com/blader/humanizer, MIT, free), installed from its source

Tested on

VerifiedTested in the last 90 days
  • Claude Code · Claude Opus 5.512 Oct 2026

Known limitations

  • It learns from your samples, so three short posts give a rough profile and more samples give a better one.
  • It changes how things are said, never what is said. A draft with weak ideas stays weak.

More

Used in these systems

Questions

Will it make my writing undetectable?
That is not the goal. It makes drafts sound like you to the people who read them. It does not promise anything about detection tools.
What is Humanizer and do I need it?
Humanizer is a separate open-source skill by another author that removes common AI writing patterns. You do not need it. If you already use it, run it first and this skill second, since this one matches your own voice. We link to its source and never bundle it.
How do I keep my voice profile?
After the first run, paste the profile into your business profile, a Claude Project's instructions or a note. Next time, the skill reads it and goes straight to the rewrite.