- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add sergebulaev/linkedin-skills --skill linkedin-post-writer -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add sergebulaev/linkedin-skills --skill linkedin-post-writer -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add sergebulaev/linkedin-skills --skill linkedin-post-writer -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add sergebulaev/linkedin-skills --skill linkedin-post-writer -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/sergebulaev/linkedin-skills/tree/HEAD/.codex-marketplace/linkedin-skills/skills/linkedin-post-writer來自發布者
Ship long-form LinkedIn posts using hook formulas that actually performed in 2025-2026 (verified engagement multipliers).
* 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 ../../references/hook-formulas.md for each formula's real reference and caveats.
† 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.
Full skeletons in ../../references/hook-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.
The reference numbers above are unchanged; what changed is how the 2026 feed treats the device each formula leans on. Every formula in ../../references/hook-formulas.md now carries a "2026 reach note"; the ones that matter when picking:
If the user knows what they want the post to earn, start here, then narrow by topic. Canonical mapping: ../../references/hook-formulas.md → Engagement-goal split.
Voice profile first (all drafts). If ../../references/voice-profile.md has filled: yes, load it and match the user's voice fingerprint, hard rules, and CTA/link 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 ../../references/story-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.
Founder mode (when the writer is a founder). Before picking a formula, open ../../references/founder-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.
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.
../../references/hook-formulas.md)linkedin-humanizer --mode audit for algorithm + voice checks before showing to user.lib.illustrate(prompt, kind="wide"), pulling brand handle/color from Voice & Brand Profile §6 for the overlay. Show the returned url + cost in the approval card and attach it via on publish. For a (2-10 images in one post) use and pass every in . For a , skip the model and typeset it: — crisp text, same flow. Full workflow: . No Pixfaro key -> it drafts the prompt for the user to generate manually.Global voice rules: see root SKILL.md §Voice rules. Additional skill-specific rules:
../../references/hook-formulas.md — all 20 formula skeletons with worked examples, per-formula 2026 reach notes, "What still lifts reach in 2026" and the Density rule../../references/founder-topics.md — founders-edition library of 10 founder angles (A1-A10) with fill-in templates../../references/algorithm-heuristics.md — 2026 posting rules (timing, format, length)references/humanizer-checklist.md — the full scrub listlinkedin-humanizer — aggressive AI-tell scrubber, plus --mode audit for pre-publish reviewlinkedin-hook-extractor — reverse-engineer a hook from a viral post you admireDraft 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 ang
---name: linkedin-post-writerdescription: Draft a new LinkedIn post from scratch using one of 20 2026 hook formulas (anaphora, R.I.P., time-anchor…---# .codex-marketplace/linkedin-skills/skills/linkedin-post-writer/SKILL.md總覽
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).
常見問題
從發布者下載 .codex-marketplace/linkedin-skills/skills/linkedin-post-writer/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/sergebulaev/linkedin-skills。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。
media_urlslib.illustrate_set([p1, p2, ...], kind="wide", overlay=brand)urlmedia_urls=[...]lib.quote_card("<hook line>", handle="@handle", style="brand")url../linkedin-humanizer/sub-skills/illustration.mdlib.publish(kind="post", draft_text=<approved>, target_url="https://www.linkedin.com/post/new/", platforms=[{"platform":"linkedin","platformId":<id>}], scheduled_time=<iso_or_None>, media_urls=<list_or_None>). The wrapper handles Publora / manual / diy routing. If the user reconsiders after approving, call lib.unpublish(post_group_id=<postGroupId 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.