domains / families / marketing / linkedin-post-writer

linkedin-post-writer

combined

Draft a new LinkedIn post from scratch using one of 20 2026 hook formulas (anaphora, R.I.P., time-anchor, curiosity-gap, contrarian, controlled A/B, false-binary, and more) plus a founders-edition angle library, picked by engagement goal (comments, reposts, likes, saves). Runs the humanizer pass and schedules via Publora on approval. Use to write a post, find a hook or proven format, or get founder-specific angles. Not for reviewing existing drafts (use linkedin-humanizer --mode audit). Draft LinkedIn posts from 16 tested hook formulas mapped to engagement goals (comments, reposts, likes, saves), with 2026 algorithm formatting rules and an AI-tell scrub pass before publishing.

When to use

• User says "write me a LinkedIn post about X"
• User has a topic + a rough angle and needs a hook + structure
• User wants to pick from known-winning formats and fill in their voice
• User wants to audit + schedule in one flow
• Use when the user says "write me a LinkedIn post about X"
• Use when the user has a topic and a rough angle but needs a hook and structure
• Use when the user wants to pick from proven post formats instead of improvising
• Use when a draft exists but the hook is weak and needs a formula-based rebuild

When not to use

• Reference engagement numbers describe the 2025-2026 corpus the formulas were extracted from; they are priors, not guarantees, and LinkedIn's ranking changes over time.
• The skill drafts text posts; it does not generate images, carousels, or video scripts.
• This standalone version does not schedule or publish. Scheduling, comment drafting, reply handling, and engagement analytics require the full bundle from the source repo.
• Voice quality depends on the raw material the user provides; a formula cannot invent authentic anecdotes, and the skill should ask for real details rather than fabricate them.

Skill page

Conflict

The two copies are not a clean original-and-derivative pair. The sergebulaev copy is the more complete, upstream procedure: it defines 20 formulas (F1-F20), including four structural formulas (F17-F20) that the sickn33 copy omits, and it carries a detailed 2026 reach-caveats section (question-open penalty, number-first lift, per-formula authenticity warnings, density rule) that the sickn33 copy does not reproduce. The sickn33 copy, however, adds material steps the sergebulaev copy lacks: an explicit four-step workflow (gather inputs, pick formula by engagement goal, draft, scrub AI tells), a goal-to-formula shortlist table, concrete 2026 formatting rules (210-char hook fold, 900-1,300 char sweet spot, 0-2 hashtags, no body links, 'How I' over 'How to'), and a named AI-tell scrub pass. Crowning either one would hide a real alternative: the sergebulaev copy hides the operational workflow and formatting rules, and the sickn33 copy hides the structural formulas and the 2026 caveats. They also disagree on the formula count (20 vs 16) and on the F6 comment-gate constraint (sergebulaev: real named deliverable, never 'comment X to get Y'; sickn33: max once a month), so a combined instruction is warranted.