linkedin-skills is a collection of Claude Code and Codex skills for creating and managing LinkedIn content from a terminal. It helps users draft posts, comments, and replies, review their feeds, and plan a publishing cadence while requiring approval before publication. The catalogue entries are the project's skills, instructions, and plugin for using these workflows with coding agents.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sergebulaev/linkedin-skillsnpx agentmods add skills/sergebulaev/linkedin-skills/linkedin-humanizerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sergebulaev/linkedin-skills/linkedin-humanizer)<a href="https://agentmods.dev/skills/sergebulaev/linkedin-skills/linkedin-humanizer"><img src="https://agentmods.dev/badge/skills/sergebulaev/linkedin-skills/linkedin-humanizer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sergebulaev/linkedin-skills/linkedin-humanizer"><img src="https://agentmods.dev/badge/skills/sergebulaev/linkedin-skills/linkedin-humanizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00093 | $0.04746 |
| Opus 5.5 | $0.00037 | $0.01898 |
| Sonnet 5.5 | $0.00019 | $0.00949 |
| Haiku 4.5 | $0.00009 | $0.00475 |
Grade A, and why
linkedin-humanizer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 27d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Humanizer V3
Rewrites any text to remove the AI tells that human readers notice and that LinkedIn's "AI slop" filter reacts to. Based on Wikipedia's "Signs of AI writing" taxonomy, the 2025-2026 stylometry literature, and our own length-controlled corpus. V3 (2026-09): recalibrated on 2026 evidence. Vocabulary is scored by density, em dashes are capped instead of banned, forced rhythm is now a tell instead of a fix, and there is an over-correction guard.
What this skill does not do: it does not make text "pass" GPTZero, Pangram, Turnitin or Originality. Those are trained classifiers keyed on the instruction-tuning style signature; prompt-style "sound like a real person" rewrites are caught 92-95% of the time (VUB IJEI 2026, Russell 2025), and light mechanical rewriting raises detectability (arXiv 2603.17522). No post-hoc edit reliably beats a Pangram-class detector, and detector scores on LinkedIn-length text (100-300 words) are noise. The real value is elsewhere: expert human readers cite vocabulary (53%) and sentence structure (36%) as what gives AI text away, and LinkedIn's July 2026 slop-report button costs a flagged post roughly 40% of its views. This skill removes what those readers and that filter react to.
What changed in V3
Evidence tier in brackets: [strong] = replicated across 2+ independent 2025-2026 studies or our own length-controlled corpus; [vendor] = single platform or vendor dataset; [weak] = one study or expert-panel report.
- Vocabulary moved from a delete-list to density scoring. The 2023-24 words (delve, tapestry, realm, journey) are decaying as humans avoid them [strong: Geng & Trotta 2025]. The durable 2026 markers are common words (significant, crucial, notably, comprehensive, insights, robust, leverage, foster, landscape, nuanced, streamline, elevate) plus grammar: nominalisations and "-ing" clause openers at 5.3x human rate [strong: Kobak Sci Adv 2025; Wu et al 2026; PNAS 2025]. AI vocabulary is also the one marker consistently reach-negative on LinkedIn in our own corpus (0.74-0.84 author-relative) [strong]. One marker in a paragraph is not a verdict. Three or more is.
- Em dash is no longer a tell. GPT-5.4 emits 1.43 per 1,000 words, below the 3.23 human baseline; 29% of human captions and 23% of top-creator LinkedIn posts in our corpus use one (author-relative ratio 1.09) [strong]. Zero em dashes is now its own tell (the writer is trying to look human). New rule: cap at about 1 per 100 words, replace excess with comma, colon, parentheses or a rewrite. Never a period.
- Forced burstiness is the #1 2026 tell, not the fix. LLM sentence-length variance is half of human [strong], but detectors do not score it, mechanical long/short alternation is a learnable humanizer fingerprint [weak: DAMAGE 2025], and on LinkedIn sentence-length variance is not an engagement lever in either direction (our corpus, n=397, within-creator: null to slightly negative) [strong]. "Short. Punchy. Done.", "No X. No Y. Just Z.", one-word paragraphs and "The result?" reveals are the current top tells. Pass 2 is now RHYTHM, not BREAK: fix machine-flat rhythm, never manufacture variance.
- Rule of three is still a tell, at density. Tricolon runs at 2x expert-human rate across 2026 frontier models [strong: arXiv 2604.19768]. Stacked, perfectly parallel triads and 3+ per post get scrubbed. One natural triple stays (26% of top human tweets have one).
- Fingerprint injection was half wrong. Named entities and concreteness are supported [strong: lower entity density in LLM text across 3 studies]; an odd-precision number with a referent in line 1 lifts likes 34% [vendor]. Bare numbers are not a discriminator, and inserted hedges and confessions backfire: performed hesitancy is 2x more common in LLM text than expert human text, and sincerity announcements ("let me be honest") are a named 2026 tell [strong: tropes.fyi false vulnerability; Schilke & Reimann 2025]. Pass 3 now asks for a flat, dated, uncomfortable fact instead.
- Over-correction guard. Humanizer output has its own fingerprint; "writing slightly worse on purpose" now reads as a tell [weak: DAMAGE 2025; slopotron]. Pass 4 checks whether Passes 1-3 introduced the very patterns they were meant to remove. Edits are proportional to real problems. When in doubt, leave it.
What ships with it
18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/audit-ai-tells.md 12 KB
- references/audit-checklist.md 4.1 KB
- references/audit-examples.md 452 B
- references/detector-list.md 6.1 KB
- references/emoji-patterns.md 3.8 KB
- references/examples.md 1.4 KB
- references/rules-explainer.md 15 KB
- references/scrub-rules.md 27 KB
- references/tier-rationale.md 17 KB
- references/voice-fingerprint.md 5.3 KB
- scripts/detectors.env.example 428 B
- scripts/test_detectors.py 13 KB runs code
- sub-skills/detector-tester.md 6.0 KB
- sub-skills/emoji-detector.md 3.9 KB
- sub-skills/illustration.md 7.4 KB
- sub-skills/post-audit.md 4.9 KB
- sub-skills/rules-explainer.md 5.2 KB
- sub-skills/voice-profile.md 3.0 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 27d ago Changed · -31 tokens per session 15d30a63d7f4
- 1mo ago Changed · +1 lines 3bf5d57f18f9
- 1mo ago Changed 9eb6f3feb227
- 1mo ago Changed · +23 lines · -45 tokens per session 6e6b654af4fe
- 1mo ago Changed · +84 tokens per session 7348f42e1d1f
- 1mo ago First seen · 152 lines · 85 tokens per session scan A de7d57cd9f31
linkedin-humanizer is a skill published in the GitHub repository sergebulaev/linkedin-skills (5,223 stars, last pushed 5d ago), licensed MIT. It adds 93 tokens to every session and 4,746 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
linkedin-content-calendar-planner
Generate a 4-week LinkedIn content calendar tuned to the user's pillars, posting cadence, and audience. Returns a day-by-day plan with topic, format, hook angle, and CTA per post. Use when the user wants a system for the next month instead of inventing content every morning. Once the plan is confirmed it writes a…
linkedin-comment-opportunity-finder
Find the LinkedIn posts the user should comment on today to earn visibility, followers, and inbound. Pulls live candidates from the Taplio engagement feeds (the personalized selection, a curated creator feed for their niche, or a keyword search), scores each post on recency, audience overlap, engagement velocity, and…
linkedin-comment-reply-manager
Clear the comment inbox under the user's own LinkedIn posts. Pulls the comments that still need an answer (already answered, own, and hidden comments are filtered out), triages each one (question, pushback, lead signal, praise, spam), drafts a reply in the user's voice, and schedules the approved replies to post under…
linkedin-daily-engagement-routine
Run the user's daily 15-minute LinkedIn engagement session end to end : answer what is waiting under their own posts, pick today's 5 posts to comment on from the Taplio feeds, draft every reply and comment in their voice, get one batch approval, schedule everything, and close with the queue, yesterday's failures, and…
linkedin-engagement-watchlist-builder
Build the bench of creators the user should engage with every day. Samples the Taplio curated feeds that match their niche, the personalized selection, and a keyword search, clusters the live posts by author, and returns a ranked watchlist of 10 to 15 creators split into reach targets (bigger audiences, for…
linkedin-smart-comment-writer
Write a LinkedIn comment that gets noticed by the post author and the audience, save it as a Taplio comment draft, and, only on the user's explicit go, schedule it to post under their name. Avoids the generic great-post trap : 3 options on one angle (add, disagree, story, framework, question), ranked by likelihood of…