[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMS2Q2YZ53P45WQEAW77SP":3,"skill-same:01M6MMS2Q2YZ53P45WQEAW77SP":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6MMS2Q2YZ53P45WQEAW77SP","linkedin-post-writer",null,"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\u002FB, 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).","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-post-writer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"linkedin","writer","linkedin post writer","post","linkedin post","new","humanizer","2026","for","mode","more","drafts","formulas","hook","false","anchor","get","time","goal","write","audit","library","2026-11-10 10:12:30",false,"---\nname: linkedin-post-writer\ndescription: \"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\u002FB, 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).\"\n---\n\n# LinkedIn Post Writer\n\nShip long-form LinkedIn posts using hook formulas that actually performed in 2025-2026 (verified engagement multipliers).\n\n## When to use\n\n- User says \"write me a LinkedIn post about X\"\n- User has a topic + a rough angle and needs a hook + structure\n- User wants to pick from known-winning formats and fill in their voice\n- User wants to audit + schedule in one flow\n\n## Formulas this skill can use\n\n| Code | Formula | Reference eng | Best for |\n|---|---|---|---|\n| F1 | Platform Risk Anaphora | 4,240 | Category\u002Fplatform posts, product-as-fix |\n| F2 | R.I.P. Obituary | 3,822 | Era-ending claims, industry pivots |\n| F3 | Year-over-Year Pivot | 494, 3.74x | Identity shifts, founder reflection |\n| F4 | Time-Anchor Confession | 1,519+ | Vulnerability, voice reset, ICP re-targeting (2026: use with care, see caveats) |\n| F5 | Self-Proving Meta | 1,082 \u002F 435 comments | Commitment-based posts, tests in public |\n| F6 | Comment-Gate Lead Magnet | 717-3,008 | List building (2026: use with care, real deliverable only, see caveats) |\n| F7 | Odd-Precision Money Ledger | 1,755, 9.4x | Founder build-log, cost breakdowns (2026: strongest opener, number-first) |\n| F8 | Paid-vs-Free Reversal | 550, 19.64x | Free framework give-away |\n| F9 | Curiosity-Gap Teaser | 306, 4.25x | Emergent behavior, behind-the-scenes (2026: use with care, pay off in 2 lines) |\n| F10 | Contrarian + Historical Receipts | 3,083 | Sacred-cow takes, AI\u002Ftech cycles |\n| F11 | Emotional Cold-Open | high-reach* | Real story with emotional stakes (likes) |\n| F12 | Permission Slip | comment-heavy* | Encouragement, reassurance (comments; 2026: use with care, needs a dated fact) |\n| F13 | Bait-and-Switch Reversal | high-reach* | Policy\u002Fprocess change that's an upgrade (likes) |\n| F14 | Named Gratitude \u002F Tribute | repost-heavy* | Thanking mentors \u002F team \u002F departing colleague (reposts) |\n| F15 | Explain-to-Kids | save-heavy* | Demystifying jargon (saves) |\n| F16 | Status-Strip Humility | like-heavy* | Senior voice wanting warmth not distance (likes) |\n| F17 | Controlled A\u002FB Anecdote | structural† | One-variable comparison, delegation\u002FAI takes (comments) |\n| F18 | False-Binary Dissolve | structural† | \"Both obvious answers fail\" governance\u002Fstrategy (comments\u002Freposts; 2026: it is the post's one contrast) |\n| F19 | Anecdote-Meets-Evidence Bridge | structural† | Personal noticing + a data stack (comments\u002Fsaves) |\n| F20 | Diverging-Curves Close | structural† | Two trajectories that diverge, quotable maxim (reposts) |\n\n\\* F11-F16 reach is absolute 2026-corpus reach (often source-driven: a reshare or a famous author), NOT a baseline multiplier like the F1-F10 numbers. The two columns measure different things and are not comparable: F11's \"256k\" is raw reach, F8's \"550, 19.64x\" is a format multiplier. Do not rank formulas by putting these side by side. See `..\u002F..\u002Freferences\u002Fhook-formulas.md` for each formula's real reference and caveats.\n\n† F17-F20 are **structural formulas**: they shape the logic of a post (a controlled comparison, a false binary, an evidence bridge, two diverging curves) rather than its topic. They carry no reference number and are chosen by primary goal. They were built for the founders edition and several founder angles pin them by name.\n\nFull skeletons in `..\u002F..\u002Freferences\u002Fhook-formulas.md`. F1-F10 are the long-form thought-leadership set; F11-F16 (validated against a 2026 corpus of above-average performers) skew shorter and emotional and each carries a primary engagement goal.\n\n### 2026 reach caveats (Sep 2026 audit)\n\nThe reference numbers above are unchanged; what changed is how the 2026 feed treats the *device* each formula leans on. Every formula in `..\u002F..\u002Freferences\u002Fhook-formulas.md` now carries a \"2026 reach note\"; the ones that matter when picking:\n\n- **Never open with a question.** Question as the first line is -34% median likes across all follower bands (MagicPost, 1.2M posts; vendor data, proprietary AI-score). Move the question to the close, where it is +3%.\n- **Prefer number-first.** An odd-precision number in line 1 is +34% median likes (same source). F7 is the strongest 2026 opener; F3, F5, F17 are number-first by construction.\n- **F4 Confession, use with care:** a specific, dated, uncomfortable fact with no \"let me be honest\" \u002F \"confession:\" framing; substance inside the first 3 lines. Manufactured candor is the \"false vulnerability\" tell; genuine vulnerability is +7 to +10% (vendor data).\n- **F6 Comment-Gate, use with care:** comment-gate CTAs are the named target of LinkedIn's March 2026 authenticity update, and the July 2026 \"AI slop\" report button cuts flagged posts ~40% views. Only with a real, named deliverable, and never \"comment X to get Y\" phrasing.\n- **F9 Curiosity-Gap, use with care:** teaser phrases (\"what nobody tells you\", \"what most people miss\", \"the real question is\") are on the 2026 AI-tell consensus lists. The gap must be specific and pay off within 2 lines, before the fold.\n- **F12 Permission Slip and F18 False-Binary, use with care:** both are generic-frame devices (\"Stop X, start Y\" -6.7%, \"It's not X, it's Y\" -4.9%, vendor data). They survive with a dated fact and as the post's only contrast.\n- **Density rule:** one contrast and one triple per post, zero \"The result?\" \u002F \"Plot twist:\" \u002F \"Here's what\" bridges. 98-100% of top human creators still use these devices; the tell is repetition plus emptiness, not the device.\n- **Still lifts reach:** number-first line, closing question, P.S. sign-off (+7.5%), 1,000+ chars (1.18x) and 20+ sentences (1.14x, AuthoredUp 3M posts), 1-2 sentence paragraphs with blank lines (recommended layout, not a tell).\n\n### Pick by goal first\n\nIf the user knows what they want the post to earn, start here, then narrow by topic. Canonical mapping: `..\u002F..\u002Freferences\u002Fhook-formulas.md` → Engagement-goal split.\n\n| Goal | Reach for |\n|---|---|\n| Comments | F17, F10, F4, F12, F9 (F4\u002FF12\u002FF9 with their 2026 caveats) |\n| Reposts | F14, F2, F8 |\n| Likes | F11, F13, F16 |\n| Saves | F15, F7, F8 |\n\n## Steps\n\n**Voice profile first (all drafts).** If `..\u002F..\u002Freferences\u002Fvoice-profile.md` has `filled: yes`, load it and match the user's voice fingerprint, hard rules, and CTA\u002Flink style throughout. If it is not filled, mention once that `linkedin-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules. If `..\u002F..\u002Freferences\u002Fstory-bank.md` has `filled: yes`, load it too and take concrete details (numbers, dates, named projects) from there instead of asking mid-draft. Never invent a figure that is not in it; if the bank has nothing that fits, ask the user or offer `linkedin-interviewer`.\n\n**Founder mode (when the writer is a founder).** Before picking a formula, open `..\u002F..\u002Freferences\u002Ffounder-topics.md` and offer a founder **angle** (A1-A10) that fits their goal. The angle picks the *territory* (reprice the category, the scarce-shots math, the delegation line, and so on); several angles pin the formula for you (A9 uses F17, A10 uses F18+F20). Founder angles compound trust with a narrow audience of investors, hires, and design partners rather than chasing broad reach. Fill the angle's bracketed slots with the founder's real numbers, then continue from step 3.\n\n**Spine from an interview (skip the asking).** If `linkedin-interviewer --mode post` handed over a five-line spine (Moment, Number, Correction, Opposition, Ask), that spine is the skeleton: Moment opens the post, Number is the proof, Correction is the turn, Opposition fixes the audience, Ask is the close. Do not re-ask for anything the spine already carries, and do not fill a line the interview left labelled empty. Pick the formula that fits the spine rather than bending the spine to a formula; if none fits, say which line is the obstacle.\n\n1. **Gather inputs.** Topic, angle, draft ideas if the user has them, target audience (founders \u002F operators \u002F marketers), desired length (short 300-500 \u002F medium 900-1300 \u002F long 1500-1900 chars).\n2. **Pick the formula.** First ask (or infer) the goal: comments, reposts, likes, or saves. Use the \"Pick by goal first\" table to shortlist, then suggest 2-3 formulas that also fit the topic and let the user pick. Show the reference engagement number next to each, plus the formula's 2026 caveat if it has one. Two hook rules apply regardless of formula: **never open with a question** (-34% median likes; the question goes at the close, +3%) and **prefer a number-first line** (+34% median likes; both MagicPost vendor data, proprietary AI-score). If the best hook you have is a question, invert it into the number that answers it.\n3. **Draft the post.** Fill the formula skeleton with user voice. Respect the 2026 algorithm rules:\n   - Hook in first 210 chars (before \"… see more\"); line 1 is a statement or a number, never a question, never \"Here's what\u002Fhow\", never \"Stop X, start Y\"\n   - Length: **the target the user picked in step 1 wins.** 900-1,300 chars is the default when they express no preference, not a ceiling over their choice. If they asked for long (1,500-1,900), write long and do not trim toward the sweet spot: 1,000+ chars and 20+ sentences carry a 1.18x \u002F 1.14x reach lift (AuthoredUp, 3M posts), so the evidence runs with them, not against them. The one hard limit is LinkedIn's 3,000 characters.\n   - Double line-breaks between ideas, not single; 1-2 sentence paragraphs are the recommended layout\n   - One contrast and one triple per post maximum; no \"The result?\" \u002F \"Plot twist:\" reveal bridges (Density rule in `..\u002F..\u002Freferences\u002Fhook-formulas.md`)\n   - Close with a specific question, and add a one-line P.S. when there is a real follow-up (+7.5%)\n   - 0-2 hashtags, placed at end\n   - No external links in body (move to first comment)\n4. **Humanizer pass.** Scrub 2026 AI vocab by density, cap em dashes (about one per 100 words), break stacked triads, generic openers and reveal bridges. Add at least 1 specific number, 1 named entity, 1 first-person concrete detail per 100 words.\n5. **Run audit.** Optionally invoke `linkedin-humanizer --mode audit` for algorithm + voice checks before showing to user.\n6. **Optional illustration.** If the post would land better with a visual (or the user asks), offer one: draft an image and generate it with `lib.illustrate(prompt, kind=\"wide\")`, pulling brand handle\u002Fcolor from Voice & Brand Profile §6 for the overlay. Show the returned `url` + `cost` in the approval card and attach it via `media_urls` on publish. For a **multi-image grid** (2-10 images in one post) use `lib.illustrate_set([p1, p2, ...], kind=\"wide\", overlay=brand)` and pass every `url` in `media_urls=[...]`. For a **quote-card of the hook**, skip the model and typeset it: `lib.quote_card(\"\u003Chook line>\", handle=\"@handle\", style=\"brand\")` — crisp text, same `url` flow. Full workflow: `..\u002Flinkedin-humanizer\u002Fsub-skills\u002Fillustration.md`. No Pixfaro key -> it drafts the prompt for the user to generate manually.\n7. **Approval card.** Show: formula used, full draft, char count, suggested posting window (Tue\u002FWed\u002FThu 7:30-9:00 AM local), reaction targets from likely commenters, and the illustration (if any).\n8. **On approval.** Call `lib.publish(kind=\"post\", draft_text=\u003Capproved>, target_url=\"https:\u002F\u002Fwww.linkedin.com\u002Fpost\u002Fnew\u002F\", platforms=[{\"platform\":\"linkedin\",\"platformId\":\u003Cid>}], scheduled_time=\u003Ciso_or_None>, media_urls=\u003Clist_or_None>)`. The wrapper handles Publora \u002F manual \u002F diy routing. If the user reconsiders after approving, call `lib.unpublish(post_group_id=\u003CpostGroupId from the response>)` to cancel it before it goes out. On the publora tier the post is already queued, so the dashboard is otherwise the only way back.\n\n## Hard rules (from user feedback)\n\nGlobal voice rules: see root `SKILL.md` §Voice rules. Additional skill-specific rules:\n\n- Never frame LinkedIn as inferior in a LinkedIn post (algo penalty).\n- Don't name-drop the user's product in a way that reads as self-promo. One mention max, and only when it's the natural conclusion, not the pitch.\n- Include at least one moment of real vulnerability or concrete stakes. Pure insight posts don't land in 2026.\n- Natural rhythm, not manufactured variance: one genuinely long sentence next to a short one per paragraph is fine; never alternate long\u002Fshort across the post and never stack fragments (at most 2 standalone fragments per post). Touch a paragraph only if every sentence reads the same flat length.\n\n## Anti-patterns (skill will refuse)\n\n- All-caps first line (\"THIS CHANGED EVERYTHING.\"). This holds even for F11 Emotional Cold-Open: carry the intensity with word choice, never caps.\n- Question as the first line (\"Ever wondered why...?\"). Invert to a number, move the question to the close.\n- \"Here's what \u002F here's how\" or \"Stop X, start Y\" as the opener; \"The result?\" \u002F \"Plot twist:\" as a reveal bridge\n- Announced candor (\"Let me be honest\", \"Confession:\") with no dated fact behind it\n- \"Comment X to get Y\" comment-gate phrasing\n- Em dashes above the cap (more than about one per 100 words)\n- \"In today's fast-paced world\" openers\n- Rule-of-three lists without receipts\n- \"Game-changer\", \"deep dive\", \"leverage\", \"fundamentally\"\n- External links in the body\n- Reused engagement-bait closers (\"tag someone who needs this\")\n\n## Resources\n\n- `..\u002F..\u002Freferences\u002Fhook-formulas.md` — all 20 formula skeletons with worked examples, per-formula 2026 reach notes, \"What still lifts reach in 2026\" and the Density rule\n- `..\u002F..\u002Freferences\u002Ffounder-topics.md` — founders-edition library of 10 founder angles (A1-A10) with fill-in templates\n- `..\u002F..\u002Freferences\u002Falgorithm-heuristics.md` — 2026 posting rules (timing, format, length)\n- `references\u002Fhumanizer-checklist.md` — the full scrub list\n\n## Related skills\n\n- `linkedin-humanizer` — aggressive AI-tell scrubber, plus `--mode audit` for pre-publish review\n- `linkedin-hook-extractor` — reverse-engineer a hook from a viral post you admire\n","# LinkedIn Post Writer\n\nShip long-form LinkedIn posts using hook formulas that actually performed in 2025-2026 (verified engagement multipliers).\n\n## When to use\n\n- User says \"write me a LinkedIn post about X\"\n- User has a topic + a rough angle and needs a hook + structure\n- User wants to pick from known-winning formats and fill in their voice\n- User wants to audit + schedule in one flow\n\n## Formulas this skill can use\n\n| Code | Formula | Reference eng | Best for |\n|---|---|---|---|\n| F1 | Platform Risk Anaphora | 4,240 | Category\u002Fplatform posts, product-as-fix |\n| F2 | R.I.P. Obituary | 3,822 | Era-ending claims, industry pivots |\n| F3 | Year-over-Year Pivot | 494, 3.74x | Identity shifts, founder reflection |\n| F4 | Time-Anchor Confession | 1,519+ | Vulnerability, voice reset, ICP re-targeting (2026: use with care, see caveats) |\n| F5 | Self-Proving Meta | 1,082 \u002F 435 comments | Commitment-based posts, tests in public |\n| F6 | Comment-Gate Lead Magnet | 717-3,008 | List building (2026: use with care, real deliverable only, see caveats) |\n| F7 | Odd-Precision Money Ledger | 1,755, 9.4x | Founder build-log, cost breakdowns (2026: strongest opener, number-first) |\n| F8 | Paid-vs-Free Reversal | 550, 19.64x | Free framework give-away |\n| F9 | Curiosity-Gap Teaser | 306, 4.25x | Emergent behavior, behind-the-scenes (2026: use with care, pay off in 2 lines) |\n| F10 | Contrarian + Historical Receipts | 3,083 | Sacred-cow takes, AI\u002Ftech cycles |\n| F11 | Emotional Cold-Open | high-reach* | Real story with emotional stakes (likes) |\n| F12 | Permission Slip | comment-heavy* | Encouragement, reassurance (comments; 2026: use with care, needs a dated fact) |\n| F13 | Bait-and-Switch Reversal | high-reach* | Policy\u002Fprocess change that's an upgrade (likes) |\n| F14 | Named Gratitude \u002F Tribute | repost-heavy* | Thanking mentors \u002F team \u002F departing colleague (reposts) |\n| F15 | Explain-to-Kids | save-heavy* | Demystifying jargon (saves) |\n| F16 | Status-Strip Humility | like-heavy* | Senior voice wanting warmth not distance (likes) |\n| F17 | Controlled A\u002FB Anecdote | structural† | One-variable comparison, delegation\u002FAI takes (comments) |\n| F18 | False-Binary Dissolve | structural† | \"Both obvious answers fail\" governance\u002Fstrategy (comments\u002Freposts; 2026: it is the post's one contrast) |\n| F19 | Anecdote-Meets-Evidence Bridge | structural† | Personal noticing + a data stack (comments\u002Fsaves) |\n| F20 | Diverging-Curves Close | structural† | Two trajectories that diverge, quotable maxim (reposts) |\n\n\\* F11-F16 reach is absolute 2026-corpus reach (often source-driven: a reshare or a famous author), NOT a baseline multiplier like the F1-F10 numbers. The two columns measure different things and are not comparable: F11's \"256k\" is raw reach, F8's \"550, 19.64x\" is a format multiplier. Do not rank formulas by putting these side by side. See `..\u002F..\u002Freferences\u002Fhook-formulas.md` for each formula's real reference and caveats.\n\n† F17-F20 are **structural formulas**: they shape the logic of a post (a controlled comparison, a false binary, an evidence bridge, two diverging curves) rather than its topic. They carry no reference number and are chosen by primary goal. They were built for the founders edition and several founder angles pin them by name.\n\nFull skeletons in `..\u002F..\u002Freferences\u002Fhook-formulas.md`. F1-F10 are the long-form thought-leadership set; F11-F16 (validated against a 2026 corpus of above-average performers) skew shorter and emotional and each carries a primary engagement goal.\n\n### 2026 reach caveats (Sep 2026 audit)\n\nThe reference numbers above are unchanged; what changed is how the 2026 feed treats the *device* each formula leans on. Every formula in `..\u002F..\u002Freferences\u002Fhook-formulas.md` now carries a \"2026 reach note\"; the ones that matter when picking:\n\n- **Never open with a question.** Question as the first line is -34% median likes across all follower bands (MagicPost, 1.2M posts; vendor data, proprietary AI-score). Move the question to the close, where it is +3%.\n- **Prefer number-first.** An odd-precision number in line 1 is +34% median likes (same source). F7 is the strongest 2026 opener; F3, F5, F17 are number-first by construction.\n- **F4 Confession, use with care:** a specific, dated, uncomfortable fact with no \"let me be honest\" \u002F \"confession:\" framing; substance inside the first 3 lines. Manufactured candor is the \"false vulnerability\" tell; genuine vulnerability is +7 to +10% (vendor data).\n- **F6 Comment-Gate, use with care:** comment-gate CTAs are the named target of LinkedIn's March 2026 authenticity update, and the July 2026 \"AI slop\" report button cuts flagged posts ~40% views. Only with a real, named deliverable, and never \"comment X to get Y\" phrasing.\n- **F9 Curiosity-Gap, use with care:** teaser phrases (\"what nobody tells you\", \"what most people miss\", \"the real question is\") are on the 2026 AI-tell consensus lists. The gap must be specific and pay off within 2 lines, before the fold.\n- **F12 Permission Slip and F18 False-Binary, use with care:** both are generic-frame devices (\"Stop X, start Y\" -6.7%, \"It's not X, it's Y\" -4.9%, vendor data). They survive with a dated fact and as the post's only contrast.\n- **Density rule:** one contrast and one triple per post, zero \"The result?\" \u002F \"Plot twist:\" \u002F \"Here's what\" bridges. 98-100% of top human creators still use these devices; the tell is repetition plus emptiness, not the device.\n- **Still lifts reach:** number-first line, closing question, P.S. sign-off (+7.5%), 1,000+ chars (1.18x) and 20+ sentences (1.14x, AuthoredUp 3M posts), 1-2 sentence paragraphs with blank lines (recommended layout, not a tell).\n\n### Pick by goal first\n\nIf the user knows what they want the post to earn, start here, then narrow by topic. Canonical mapping: `..\u002F..\u002Freferences\u002Fhook-formulas.md` → Engagement-goal split.\n\n| Goal | Reach for |\n|---|---|\n| Comments | F17, F10, F4, F12, F9 (F4\u002FF12\u002FF9 with their 2026 caveats) |\n| Reposts | F14, F2, F8 |\n| Likes | F11, F13, F16 |\n| Saves | F15, F7, F8 |\n\n## Steps\n\n**Voice profile first (all drafts).** If `..\u002F..\u002Freferences\u002Fvoice-profile.md` has `filled: yes`, load it and match the user's voice fingerprint, hard rules, and CTA\u002Flink style throughout. If it is not filled, mention once that `linkedin-humanizer --mode profile` can learn their voice from a few posts, then proceed with the generic voice rules. If `..\u002F..\u002Freferences\u002Fstory-bank.md` has `filled: yes`, load it too and take concrete details (numbers, dates, named projects) from there instead of asking mid-draft. Never invent a figure that is not in it; if the bank has nothing that fits, ask the user or offer `linkedin-interviewer`.\n\n**Founder mode (when the writer is a founder).** Before picking a formula, open `..\u002F..\u002Freferences\u002Ffounder-topics.md` and offer a founder **angle** (A1-A10) that fits their goal. The angle picks the *territory* (reprice the category, the scarce-shots math, the delegation line, and so on); several angles pin the formula for you (A9 uses F17, A10 uses F18+F20). Founder angles compound trust with a narrow audience of investors, hires, and design partners rather than chasing broad reach. Fill the angle's bracketed slots with the founder's real numbers, then continue from step 3.\n\n**Spine from an interview (skip the asking).** If `linkedin-interviewer --mode post` handed over a five-line spine (Moment, Number, Correction, Opposition, Ask), that spine is the skeleton: Moment opens the post, Number is the proof, Correction is the turn, Opposition fixes the audience, Ask is the close. Do not re-ask for anything the spine already carries, and do not fill a line the interview left labelled empty. Pick the formula that fits the spine rather than bending the spine to a formula; if none fits, say which line is the obstacle.\n\n1. **Gather inputs.** Topic, angle, draft ideas if the user has them, target audience (founders \u002F operators \u002F marketers), desired length (short 300-500 \u002F medium 900-1300 \u002F long 1500-1900 chars).\n2. **Pick the formula.** First ask (or infer) the goal: comments, reposts, likes, or saves. Use the \"Pick by goal first\" table to shortlist, then suggest 2-3 formulas that also fit the topic and let the user pick. Show the reference engagement number next to each, plus the formula's 2026 caveat if it has one. Two hook rules apply regardless of formula: **never open with a question** (-34% median likes; the question goes at the close, +3%) and **prefer a number-first line** (+34% median likes; both MagicPost vendor data, proprietary AI-score). If the best hook you have is a question, invert it into the number that answers it.\n3. **Draft the post.** Fill the formula skeleton with user voice. Respect the 2026 algorithm rules:\n   - Hook in first 210 chars (before \"… see more\"); line 1 is a statement or a number, never a question, never \"Here's what\u002Fhow\", never \"Stop X, start Y\"\n   - Length: **the target the user picked in step 1 wins.** 900-1,300 chars is the default when they express no preference, not a ceiling over their choice. If they asked for long (1,500-1,900), write long and do not trim toward the sweet spot: 1,000+ chars and 20+ sentences carry a 1.18x \u002F 1.14x reach lift (AuthoredUp, 3M posts), so the evidence runs with them, not against them. The one hard limit is LinkedIn's 3,000 characters.\n   - Double line-breaks between ideas, not single; 1-2 sentence paragraphs are the recommended layout\n   - One contrast and one triple per post maximum; no \"The result?\" \u002F \"Plot twist:\" reveal bridges (Density rule in `..\u002F..\u002Freferences\u002Fhook-formulas.md`)\n   - Close with a specific question, and add a one-line P.S. when there is a real follow-up (+7.5%)\n   - 0-2 hashtags, placed at end\n   - No external links in body (move to first comment)\n4. **Humanizer pass.** Scrub 2026 AI vocab by density, cap em dashes (about one per 100 words), break stacked triads, generic openers and reveal bridges. Add at least 1 specific number, 1 named entity, 1 first-person concrete detail per 100 words.\n5. **Run audit.** Optionally invoke `linkedin-humanizer --mode audit` for algorithm + voice checks before showing to user.\n6. **Optional illustration.** If the post would land better with a visual (or the user asks), offer one: draft an image and generate it with `lib.illustrate(prompt, kind=\"wide\")`, pulling brand handle\u002Fcolor from Voice & Brand Profile §6 for the overlay. Show the returned `url` + `cost` in the approval card and attach it via `media_urls` on publish. For a **multi-image grid** (2-10 images in one post) use `lib.illustrate_set([p1, p2, ...], kind=\"wide\", overlay=brand)` and pass every `url` in `media_urls=[...]`. For a **quote-card of the hook**, skip the model and typeset it: `lib.quote_card(\"\u003Chook line>\", handle=\"@handle\", style=\"brand\")` — crisp text, same `url` flow. Full workflow: `..\u002Flinkedin-humanizer\u002Fsub-skills\u002Fillustration.md`. No Pixfaro key -> it drafts the prompt for the user to generate manually.\n7. **Approval card.** Show: formula used, full draft, char count, suggested posting window (Tue\u002FWed\u002FThu 7:30-9:00 AM local), reaction targets from likely commenters, and the illustration (if any).\n8. **On approval.** Call `lib.publish(kind=\"post\", draft_text=\u003Capproved>, target_url=\"https:\u002F\u002Fwww.linkedin.com\u002Fpost\u002Fnew\u002F\", platforms=[{\"platform\":\"linkedin\",\"platformId\":\u003Cid>}], scheduled_time=\u003Ciso_or_None>, media_urls=\u003Clist_or_None>)`. The wrapper handles Publora \u002F manual \u002F diy routing. If the user reconsiders after approving, call `lib.unpublish(post_group_id=\u003CpostGroupId from the response>)` to cancel it before it goes out. On the publora tier the post is already queued, so the dashboard is otherwise the only way back.\n\n## Hard rules (from user feedback)\n\nGlobal voice rules: see root `SKILL.md` §Voice rules. Additional skill-specific rules:\n\n- Never frame LinkedIn as inferior in a LinkedIn post (algo penalty).\n- Don't name-drop the user's product in a way that reads as self-promo. One mention max, and only when it's the natural conclusion, not the pitch.\n- Include at least one moment of real vulnerability or concrete stakes. Pure insight posts don't land in 2026.\n- Natural rhythm, not manufactured variance: one genuinely long sentence next to a short one per paragraph is fine; never alternate long\u002Fshort across the post and never stack fragments (at most 2 standalone fragments per post). Touch a paragraph only if every sentence reads the same flat length.\n\n## Anti-patterns (skill will refuse)\n\n- All-caps first line (\"THIS CHANGED EVERYTHING.\"). This holds even for F11 Emotional Cold-Open: carry the intensity with word choice, never caps.\n- Question as the first line (\"Ever wondered why...?\"). Invert to a number, move the question to the close.\n- \"Here's what \u002F here's how\" or \"Stop X, start Y\" as the opener; \"The result?\" \u002F \"Plot twist:\" as a reveal bridge\n- Announced candor (\"Let me be honest\", \"Confession:\") with no dated fact behind it\n- \"Comment X to get Y\" comment-gate phrasing\n- Em dashes above the cap (more than about one per 100 words)\n- \"In today's fast-paced world\" openers\n- Rule-of-three lists without receipts\n- \"Game-changer\", \"deep dive\", \"leverage\", \"fundamentally\"\n- External links in the body\n- Reused engagement-bait closers (\"tag someone who needs this\")\n\n## Resources\n\n- `..\u002F..\u002Freferences\u002Fhook-formulas.md` — all 20 formula skeletons with worked examples, per-formula 2026 reach notes, \"What still lifts reach in 2026\" and the Density rule\n- `..\u002F..\u002Freferences\u002Ffounder-topics.md` — founders-edition library of 10 founder angles (A1-A10) with fill-in templates\n- `..\u002F..\u002Freferences\u002Falgorithm-heuristics.md` — 2026 posting rules (timing, format, length)\n- `references\u002Fhumanizer-checklist.md` — the full scrub list\n\n## Related skills\n\n- `linkedin-humanizer` — aggressive AI-tell scrubber, plus `--mode audit` for pre-publish review\n- `linkedin-hook-extractor` — reverse-engineer a hook from a viral post you admire\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-post-writer",483,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-13 02:16:32",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-post-writer",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-post-writer",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-post-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-post-writer\u002FSKILL.md",true,[70,76,80],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Falgorithm-heuristics.md","REFERENCE","参考文档",114,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-post-writer\u002Freferences\u002Falgorithm-heuristics.md",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fhook-formulas.md",100,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-post-writer\u002Freferences\u002Fhook-formulas.md",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fhumanizer-checklist.md",6504,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-post-writer\u002Freferences\u002Fhumanizer-checklist.md",[85,93,100,107,134,159],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":92},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":92},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":41},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":41},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[141,142,143,129,144,145,146,147,148,149,150,151,152,153,119,154,155,156,157,158],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":176,"publishedAt":41},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[165,170,173],{"categoryNo":166,"categoryName":167,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":171,"categoryName":172,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":174,"categoryName":175,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000010","后端与接口",[161,177,178,179,180,181,182,155,183,120,184,185,186,187,125,188,189,190,191,192],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]