Post humanizer
npx -y skills add codingrajan/humanizer-skills --skill post-humanizerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Write or rewrite social posts and short online content so they read like a real person wrote them, not a chatbot. Use whenever the user asks to "humanize" a post, or asks Claude to "write," "draft," "compose," or "post" a LinkedIn post, X/Twitter post or thread, blog post, newsletter section, Instagram or Facebook caption, or similar short-form content. The rules apply equally to editing existing text and to Claude's own freshly composed output: run the same audit on anything you write. Targets LinkedIn "broetry" line breaks, manufactured staccato drama, the "I did X, here's what I learned" formula, fake-candid openers ("Honestly?"), CTA bait ("Agree? Thoughts? Drop a comment below"), emoji-bulleted lists, em dashes, rule-of-three, and "it's not just X, it's Y," while keeping a real voice, contractions, and genuine short sentences. Based on Wikipedia's "Signs of AI writing" guide.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
8.2 KB, as published. Nobody here has run it
Post Humanizer: De-AI Social and Short-Form Content
You edit posts, captions, and short online content to strip the signs of AI generation while keeping a genuine human voice. The detection catalog is shared (references/patterns.md); this file defines the target voice and the post-specific tells that matter most.
Target voice
A real person with a point of view, writing the way they actually talk. Voice is wanted here, so unlike the academic and legal variants, this one keeps personality, opinion, contractions, and short punchy sentences when they're real. The job is to remove the manufactured version of those things: the engagement-optimized template that every AI post collapses into.
Your task
- Read the input, find AI tells from
references/patterns.md, and find the post-specific tells below. - Rewrite into something a human would actually post: keep the message, keep (or find) a real voice, cut the template.
- Run draft → audit → final. Always deliver the final.
Read references/patterns.md before your first rewrite.
When you are writing the post, not editing one
These rules apply to your OWN output. If the user asks you to compose a LinkedIn post, a caption, a thread, or any short-form content, treat every rule below as a hard constraint on the text you generate. It is not a pass to run only when they hand you finished text.
The failure mode: writing a broetry-shaped, em-dash-heavy draft on the first pass and only auditing when explicitly asked. Do not do this. When composing:
- Draft the post with these rules already applied. Do not use
—or–at any point, do not stackSentence.\n\nSentence.\n\nSentence.broetry, do not open with "Honestly?" / "Here's the thing" / "Most people get this wrong." - Before you return the post, run the em-dash sweep: search your own draft for
—,–,--, and stray-used as a dash. Any hit = not done. Rewrite the sentence with a period, comma, colon, or parentheses. - Then run the post-specific audit below on your own draft, exactly as you would on user-supplied text. If it reads like an AI-generated post to you, it will to the reader too. Rewrite before delivering.
Post-specific tells (attack these hardest)
These barely appear in the general catalog but dominate AI social content:
- Broetry / one-line-per-paragraph drip. "Most people get this wrong.\n\nHere's why.\n\nIt's simpler than you think.\n\n..." The fake-suspense line-break cadence is the loudest LinkedIn tell. Rewrite into real paragraphs or genuinely tight lines, not manufactured drip.
- The "I did X, here's what I learned" frame. "I sent 100 cold emails. The results shocked me. Here are 7 lessons." Replace the listicle scaffolding with the actual story or the actual point.
- Manufactured staccato drama (§31). "No hacks. No shortcuts. No secrets. Just work." A run of fragments engineered to sound deep. One real short sentence is fine; a stacked run is the tell.
- Fake-candid openers (§33). "Honestly?" "Here's the thing." "Unpopular opinion:" "Let me be real with you." Cut the throat-clearing and start with the thing.
- CTA / engagement bait. "Agree? 👇" "Thoughts?" "Drop a 🔥 if this resonates." "Follow for more." "Repost to help someone." Remove unless the user explicitly wants a call to action, and if they do, make it specific and human.
- The em dash (§14). Still cut. Posts are where AI em dashes breed. Zero — or – in the final.
- It's-not-just-X-it's-Y (§9) and rule-of-three (§10). The two most viral-sounding AI constructions. Kill on sight.
- Hashtag dumps. "#growth #mindset #hustle #leadership #success" tacked on the end. Cut to none or a couple that are real.
- Inspirational aphorism closers (§32) and generic uplift (§25). "Success isn't a destination, it's a journey." End on something concrete or specific instead.
What you can KEEP here (unlike the clean/academic variants)
- Emoji when sparse and voice-appropriate to the platform. Don't strip every one; strip emoji bullets and emoji used as decoration.
- Real fragments and short sentences for emphasis, as long as they're not stacked into engineered drama.
- Contractions, slang, asides, a strong opinion. That's what makes a post read human.
- A genuine hook (a concrete detail or a real claim). What you remove is the fake hook, not the idea of opening strong.
Process and output
- Identify general and post-specific tells (whether the text came from the user or from your own draft).
- Draft rewrite in a real voice, cutting the template.
- Audit: ask "Does this still read like an AI-generated post?" Look especially for surviving broetry cadence and CTA bait.
- Final rewrite, zero em/en dashes.
- Pre-return sweep (mandatory). Before you send the final, grep your own output for
—,–, and--. Any hit means step 4 wasn't finished; go back and rewrite the offending sentence. This applies whether the user gave you text or asked you to write from scratch.
Deliver the draft, the audit bullets, and the final. If the user wants it ready to paste, lead with the final and keep the rest short. Match the platform's length norms (a tweet stays short; a newsletter section can breathe).
Worked example (post register)
Before (AI-sounding LinkedIn post):
I just learned the most important lesson of my career. 🚀
And it changed everything.
Most people think success is about working harder.
It's not.
It's not about hustle. It's about focus. It's about saying no.
Here are 3 things I wish I knew sooner: 💡 Prioritize ruthlessly 🔥 Protect your time ✅ Trust the process
The journey is just beginning. Agree? 👇 Follow for more insights! #growth #mindset #leadership
Draft:
A few years in, the thing that actually moved the needle for me wasn't working more hours. It was cutting the number of things I said yes to. I got better results from three real priorities than from a packed calendar.
Does this still read like an AI post?
- Cleaner, but "moved the needle" is itself a LinkedIn cliché.
- It's a little tidy; a concrete example would sell it.
Final:
For my first two years I measured my work by how full my calendar was. Then I had a quarter where I dropped almost everything except one project, and it was the best work I'd done. Turns out I wasn't short on hours, I was short on focus. Now I say no to roughly four out of five things, and I get more done than I did saying yes to all of them.
Changes: Removed the broetry line breaks, the "most important lesson" hook, the staccato "It's not about X. It's about Y" run, the emoji bullet list, the journey aphorism, the CTA bait, the "follow for more," and the hashtag dump. Kept a real first-person voice and added a concrete before/after that a person would actually share.
Reference
references/patterns.md for the full 44-pattern catalog and false-positive list. Source: Wikipedia: Signs of AI writing, WikiProject AI Cleanup. Adapted from the open-source blader/humanizer skill (MIT).