All skills
sergebulaev avatar

/fb-humanizer

@7ec9963

Remove the AI tells readers react to in a Facebook Page post: 2026 vocabulary by density, reveal bridges, staccato stacks, stacked triads, performed sincerity, "We are thrilled to announce" auto-pilot; caps em dashes. Includes --mode audit (under-80 sweet spot, hook, engagement bait, hashtag and emoji limits) and --mode profile. Not for beating AI detectors (no edit reliably does). Not for writing from scratch (use fb-post-writer). Keywords: humanize, de-AI my post, audit before posting.

Use this Skill: https://skilld.dev/gh/sergebulaev/facebook-skills/fb-humanizer

This session only. Nothing lands on disk.

referencesexamples.md

≈959 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Humanizer Examples (Facebook Page)

Worked before/after rewrites. Each shows the AI tells caught and the fix.

Example 1 - the corporate announcement

Before (AI-drafted):

We are thrilled to announce that we have officially launched our brand-new product, which fundamentally reimagines the way our customers leverage their daily workflow. This is a true game-changer and we cannot wait to embark on this journey with all of you. Stay tuned for more updates.

Tells caught:

  • "We are thrilled to announce" (corporate opener, single-hit blocker)
  • The paragraph scores 4 markers ("fundamentally", "leverage", "game-changer", "embark on this journey"), so it is rewritten as a paragraph, not word-swapped
  • No specific detail, no number with a referent, no human voice
  • Way over the 80-char sweet spot with nothing earning the length
  • Not caught: nothing about rhythm. The fix is the short version of the point, not the paragraph chopped into fragments. Pass 4: no hedge, no "we'll be honest" frame was added; "rebuilt three times" came from the user

After (rewrite, short):

It is live. The thing we rebuilt three times finally shipped today.

73 chars. One plain line, a real detail ("rebuilt three times"), human voice, under the sweet spot. Designed to be shared.

Example 2 - the buried short post

Before:

In today's fast-paced world, customer service can really make or break a business, and we have always believed that being responsive is essentially the most important thing you can do. That is why our team works incredibly hard to get back to every single message as fast as humanly possible.

Tells caught:

  • "in today's fast-paced world" (dead phrase, blocker)
  • "essentially", "really" (filler)
  • The actual point is one number hiding in a paragraph

After (the short version that was hiding inside):

We answer every message in under 4 minutes. On weekends too.

59 chars. The number was the whole post. Everything else was padding.

Example 3 - engagement bait

Before:

Our new menu drops Friday! LIKE and SHARE this post if you are excited, and tag 3 friends who need to try it! Let us know in the comments below!! 🔥🔥🔥🔥

Tells caught:

  • "LIKE and SHARE", "tag 3 friends" (engagement bait, downranked, blocker)
  • "Let us know in the comments below" (dead closer)
  • 4 emoji (cut to 0-1)

After:

New menu drops Friday. Which one are you trying first?

54 chars. The question earns real comments without begging. One idea, under the sweet spot, designed for comments.

Example 4 - keeping a real story post (long is fine when earned)

Before:

We wanted to take a moment to delve into the journey of how our bakery navigated a really challenging period and ultimately emerged stronger, which we believe is a testament to the robust resilience of our incredible team.

Tells caught:

  • "delve", "navigated", "ultimately", "robust", "testament", "journey" (AI vocab)
  • Abstract, no scene, no specific moment

After (a real story post, deliberately longer, FB8 shape):

The oven died at 4am on our busiest Saturday.

Two of us drove across town, borrowed a friend's oven, and baked 200 loaves in a stranger's kitchen by 9.

Sold out by noon. Sometimes the backup plan is just people who show up.

A long post, but every line earns its place: a real scene, a real number with a referent (200 loaves, a stranger's kitchen, by 9), a quotable ending built to be shared. This is when going long is the right call. Pass 2 note: the lines vary in length because the story does, not because a humanizer chopped them; "Sold out by noon." is the post's one standalone fragment, under the 2-per-post cap. Pass 4 note: the uncomfortable fact ("The oven died at 4am") is stated flat with no "we'll be honest" frame around it.

Source: SKILL.md on GitHub

No alerts16d3 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The analyzed skill contains instructions, regex patterns, and structured workflows designed to remove machine-like signatures and 'AI tells' from Facebook Page posts. It includes an optional module for text-to-image integration via a specific library layer, alongside profile building capabilities. No malicious code, exfiltration paths, or suspicious patterns were identified during the analysis.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

Signed by skilld at 7ec9963. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 weeks ago

README badge

README badge for sergebulaev/facebook-skills/fb-humanizer