Skip to content

sergebulaev/linkedin-skills / .codex-marketplace/linkedin-skills/skills/linkedin-humanizer

linkedin-humanizer

Verified

Remove AI tells from LinkedIn posts/comments: 2026 vocabulary density, reveal bridges, staccato fragments, stacked triads, performed sincerity. Tiered rewriter plus `--mode audit` LinkedIn post auditor and `--mode profile` voice builder. Not for drafting from scratch (use linkedin-post-writer) or beating AI detectors. Keywords: humanize, de-AI, post audit, post auditor, audit before posting.

sub-skills/voice-profile.md

View on GitHub
# Sub-skill: Build / update the Voice & Brand Profile

Builds or refreshes `../../../references/voice-profile.md` so every writing skill in
this bundle drafts in the user's real voice instead of a generic "human" voice.
Runs on any agent (Claude Code, Codex, OpenClaw): the core path needs only the
user's own writing pasted in. Apify is an optional accelerator, never required.

## When this runs

- User says "build my voice profile", "learn my voice", "set up my profile", or
  invokes `linkedin-humanizer --mode profile`.
- Also offer it the first time a writing skill runs and finds `filled: no`.

## Inputs (any one is enough)

1. **Pasted samples (portable default).** Ask for 3-6 of the user's own real
   LinkedIn posts or comments. This alone is enough; no token, no history needed.
2. **Apify-assisted (optional).** If `APIFY_TOKEN` is set and the user gives their
   profile URL, pull recent activity with `lib.ApifyClient.fetch_user_recent_comments(username=...)`
   (and any post URLs they share via `lib.fetch_post`) to gather more samples.
   Treat as an accelerator on top of, not a replacement for, pasted samples.
3. **Manual.** The user can also just tell you their niche, rules, and links.

## Steps

1. **Gather 3+ real samples** of the user's writing (pasted or pulled).
2. **Extract the voice fingerprint** from the samples, not from assumptions:
   - sentence-length rhythm (short/medium/mixed, and how often a long line appears)
   - recurring openers and transitions they actually use
   - punctuation habits (soft `..` pause? never em dashes? line breaks per idea?)
   - vocabulary they lean on, and any words/cliches they clearly avoid
   - emoji and hashtag behavior
3. **Infer niche, ICP, and pillars** from the sample topics; confirm with the user
   rather than guessing.
4. **Capture hard rules and CTA/link style** the samples reveal or the user states.
5. **Write `../../../references/voice-profile.md`**: fill sections 1-5, copy the 2-4
   strongest lines verbatim into "Signature examples", and set the Status block to
   `filled: yes`, `source: <pasted|apify|manual>`, `updated: <today's date>`.
6. **Show the user the filled profile for approval** before saving, and tell them
   any writing skill will now match it automatically. They can edit the file anytime.

## Hard rules

- Build the fingerprint from the user's ACTUAL samples. Never invent a voice.
- Preserve their quirks (a favorite phrase, an unusual rhythm). Those are the
  point. Only the generic AI-tell scrub still applies to drafts later, not to the
  profile itself.
- Keep it honest about coverage: with 3 samples say the profile is a first pass and
  will sharpen as they add more; suggest re-running after 10+ posts.
- Never put secrets, private data, or anything the user did not provide into the file.

## Related

- The filled profile is read by `linkedin-post-writer`, `linkedin-comment-drafter`,
  `linkedin-reply-handler`, and `linkedin-repurposer` before they draft.
- Re-run this any time the user's voice or focus shifts to refresh the profile.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall