sergebulaev/facebook-skills / .codex-marketplace/facebook-skills/skills/fb-humanizer
fb-humanizer
VerifiedRemove the AI tells readers react to in a Facebook Page post: 2026 vocabulary by density, reveal bridges, staccato stacks, stacked triads, announcement auto-pilot. Also --mode audit (under-80 sweet spot, hook, engagement bait), --mode profile (learns how you write) and --mode interview (fills your Story Bank: the stories, scars and numbers posts are made of). Not for writing from scratch (use fb-post-writer). Keywords: humanize, de-AI my post, interview me, audit before posting.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.2 KB |
| references/audit-checklist.md | markdown | 4.0 KB |
| references/examples.md | markdown | 3.7 KB |
| references/scrub-rules.md | markdown | 20.6 KB |
| sub-skills/illustration.md | markdown | 3.8 KB |
| sub-skills/post-audit.md | markdown | 5.0 KB |
| sub-skills/story-bank-interview.md | markdown | 6.5 KB |
| sub-skills/voice-profile.md | markdown | 2.3 KB |
references/examples.md
View on GitHub# 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |