agentsclimarketplace

Fb humanizer

Skill sergebulaev/facebook-skills/skills/fb-humanizer

Scrub AI tells from any Facebook Page post draft, or audit a finished draft against the 2026 Facebook checklist. Strips em dashes, AI vocabulary (leverage, delve, harness), "We are thrilled to announce" openers, and corporate auto-pilot, then adds human fingerprints. Includes a --mode audit pre-publish check (under-80 sweet spot, hook, engagement bait, hashtag and emoji limits). Triggers on humanize, de-AI my post, audit before posting. Not for writing from scratch (use fb-post-writer).From its SKILL.md

Install
npx -y skills add sergebulaev/facebook-skills --skill fb-humanizer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 20 stars20 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.

SKILL.md

6.2 KB, as published. Nobody here has run it

Facebook Page Humanizer

Rewrites any Facebook Page post to remove AI tells, and audits a finished draft against the 2026 Facebook ranking checklist. Based on Wikipedia's "Signs of AI writing" taxonomy plus Facebook-Page-specific patterns (the under-80 sweet spot, the "See more" fold, the "We are thrilled to announce" corporate tell, and the meaningful-interactions model).

When to use

  • Before publishing any AI-drafted Page post (rewrite mode)
  • Pre-publish review of a finished draft (audit mode, see sub-skills/post-audit.md)
  • When a draft feels corporate or off and you cannot pinpoint why

Input

Any text: a short Page post, a longer story post, or a comment reply draft. Optional: target voice samples (the Page's past posts).

Output

  • Rewritten text with AI tells removed
  • A diff showing what changed and why
  • Char count, with a flag when a post crosses the 80-char sweet spot
  • Confidence: "human", "mixed", "AI-likely"

Modes

# Default: scrub AI tells and fix Facebook-format issues
fb-humanizer <text>

# Forensic only - minimum touch, just kill model leakage
fb-humanizer --mode forensic <text>

# Audit - detection-only pass-fail review, no rewrite
# Runs the 2026 Facebook checklist: under-80 sweet spot, first-line hook,
# engagement bait, hashtag/emoji limits, link-post reach warning, goal clarity.
# Returns Blockers + Warnings + suggested fixes. See sub-skills/post-audit.md.
fb-humanizer --mode audit <text>

The three passes

Pass 1 - SCRUB (delete or replace)

Apply the tiered catalogs in references/scrub-rules.md:

  • Forensic (always on): real model leakage no human types. AI tool markers (oaicite, contentReference, turn0search0), knowledge-cutoff disclaimers ("As of my last update"), template blanks ([Your Name], [Page Name]), and em dash overuse.
  • Strict (default on): bad Page style regardless of origin. Vocabulary swaps (leverage -> use, delve -> look, harness -> use, foster -> build), filler adverbs (fundamentally, essentially, ultimately), corporate openers ("We are thrilled to announce" -> the plain news), phrase cleanups ("in today's fast-paced world", "game-changer", "deep dive"), and dead closers ("What do you think?").

Pass 2 - BREAK (force burstiness)

  • If the post is long, look for the short version hiding inside it. The under-80-char line often beats the paragraph.
  • Add a sentence fragment where it fits ("Every time.").
  • Break perfect parallel structures with one asymmetric line.

Pass 3 - ADD (human fingerprints)

Require where the content allows:

  • 1 specific number (replace "many", "a lot", "massive")
  • 1 named entity (real person, company, tool)
  • a warm, human Page voice (not a press release, not a faceless bot)
  • 1 first-person or behind-the-scenes concrete detail

If the input lacks these, ask the user for a number or anecdote. Do not fabricate.

Non-negotiable rules

Global voice rules: see root SKILL.md Voice rules. Additional skill-specific rules:

  • Scrubbing is always in scope. When asked to humanize, de-AI, finalize, or publish a Page post, run at least the forensic + strict passes before it ships. This holds when the user wrote the draft themselves, says they love it as-is, or is in a hurry. Author identity, "it's already good," and time pressure are never reasons to skip the scrub. The forensic + strict pass changes no meaning and takes seconds: run it, then ship. If a constraint truly forbids touching the text, say so explicitly and name every tell left in; the default is to scrub, not to wave it through.
  • Preserve the user's actual claim and meaning. "Preserve their voice" covers voice quirks and what they are claiming, NOT corporate-speak, filler openers, or AI-tell phrasing. Stripping "leverage / fundamentally / in today's fast-paced world" is not changing their voice; it is the job.
  • Never introduce facts that were not in the input. If a number is missing, ask.
  • Keep the Page's voice quirks (its register, its .. soft pauses).
  • Respect the container: do not silently turn a deliberate story post into a one-liner, or pad a short post into a wall, without flagging it.

Facebook-specific tells this skill catches

  • "We are thrilled / excited / delighted to announce.." corporate auto-pilot.
  • A long post whose actual point is one short line hiding in paragraph 3.
  • A first line that needs the second line to make sense (the "See more" fold).
  • Engagement bait ("LIKE and SHARE if you agree", "comment YES", "tag 3 friends").
  • 5+ hashtags stuffed at the bottom.
  • A bare external link with no framing text.
  • Generic corporate hype with no specific detail.

Example

See references/examples.md for worked before/after rewrites.

Files

  • SKILL.md - this file (rewrite scrubber + audit-mode entry)
  • references/scrub-rules.md - vocabulary swaps and regex by tier
  • references/examples.md - worked before/after rewrites for short and story posts
  • references/audit-checklist.md - the pre-publish checklist with thresholds
  • sub-skills/post-audit.md - pre-publish audit workflow (detection-only, no rewrite)

Voice profile mode (--mode profile)

fb-humanizer --mode profile builds or updates the user's Voice & Brand Profile at ../../references/voice-profile.md from 3-6 of their real Facebook posts pasted in (portable, no token) or, if a read token is set, from pulled activity. Once filled, every writing skill in this bundle drafts in the user's voice automatically. See sub-skills/voice-profile.md. Triggers: "build my voice profile", "learn my voice".

Related skills

  • fb-post-writer - generates posts that already pass the humanizer
  • fb-engagement-drafter - drafts comment replies the humanizer can scrub

What ships with it: 5 files

12.9 KB alongside SKILL.md

references/

sub-skills/

Gives 0 of the 12 instructions most docs writing skills give

Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06

  • Use third-person for skill descriptionsin 54 of 1951, across 35 files
  • Start descriptions with Use whenin 43 of 1951, across 29 files
  • Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
  • Use active voicein 40 of 1951, across 36 files
  • Map file responsibilities before defining tasksin 36 of 1951, across 29 files
  • Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
  • Ask one question at a timein 35 of 1951
  • Offer execution options after saving the planin 33 of 1951, across 24 files
  • Include complete code in every stepin 33 of 1951, across 27 files
  • Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
  • Announce the skill usage at the startin 30 of 1951
  • Verify agent compliance after adding the skillin 29 of 1951, across 17 files

Said here and by no other author read

  • Run forensic and strict passes on all captions
  • Add one specific number or named entity
  • remove AI vocabulary and corporate openers
  • strip em dashes and filler adverbs
  • include one first-person or behind-the-scenes detail
  • keep the page's voice quirks and soft pauses

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 612,213. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.