Token导航 LogoToken导航

Agent Skill · 开发

linkedin-post-writer(linkedin 帖子作者)

linkedin-post-writer 用于处理音频、语音、转写和声音素材相关任务,适合在 OpenClaw 中需要整理音频流程、转写内容或生成配音素材时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

linkedin-post-writer 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 8,856。

总安装 2,970周安装 119GitHub Stars 公开资料未说明下载 962核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:linkedin-post-writer(linkedin 帖子作者)
来源仓库:https://github.com/sergebulaev/linkedin-post-writer
安装命令:
openclaw skills install linkedin-post-writer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install linkedin-post-writer

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

使用经过验证的 2026 年挂钩公式、量身定制的语音以及为创始人、营销人员和思想领袖提供的日程安排选项起草 LinkedIn 帖子。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install linkedin-post-writer;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

linkedin-post-writer 怎么安装?

在终端执行 openclaw skills install linkedin-post-writer。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

linkedin-post-writer 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

linkedin-post-writer 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

linkedin-post-writer 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

linkedin-post-writer 用的人多吗?

公开数据是累计安装 2,970 次,近一周安装 119 次,下载 962 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

linkedin-post-writer 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
linkedin-post-writer

linkedin 帖子作者 · 本页

2,970—需要联网MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
linkedin-post-writer
description
Draft a viral-ready LinkedIn post using a 2026 hook formula. Use when the user wants to write a new LinkedIn post, needs help with a hook, or wants to pick a proven format (platform-risk anaphora, R.I.P. obituary, year-over-year pivot, time-anchor confession, self-proving meta, paid-vs-free reversal, curiosity-gap teaser, odd-precision money ledger, contrarian historical receipts). The skill drafts the post, runs the humanizer pass, shows an approval card, and schedules via Publora on confirmation. Keywords: linkedin post, viral hook, personal brand, founder post, content draft, thought leadership, 2026 algorithm.

LinkedIn Post Writer

Ship long-form LinkedIn posts using hook formulas that actually performed in 2025-2026 (verified engagement multipliers from Jake Ward, Lara Acosta, Cam Trew, Noam Nisand, Alex Vacca, Richard Illingworth, Naïlé Titah).

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

Formulas this skill can use

CodeFormulaReference engBest for
F1Platform Risk Anaphora (Jake Ward)4,240Category/platform posts, product-as-fix
F2R.I.P. Obituary (Alex Vacca)3,822Era-ending claims, industry pivots
F3Year-over-Year Pivot (Cam Trew)494, 3.74xIdentity shifts, founder reflection
F4Time-Anchor Confession (Lara Acosta)1,519+Vulnerability, voice reset, ICP re-targeting
F5Self-Proving Meta (Noam Nisand)1,082 / 435 commentsCommitment-based posts, tests in public
F6Comment-Gate Lead Magnet (Illingworth)717-3,008List building (use sparingly, capped reach)
F7Odd-Precision Money Ledger (Jake Ward)1,755, 9.4xFounder build-log, cost breakdowns
F8Paid-vs-Free Reversal (Illingworth)550, 19.64xFree framework give-away
F9Curiosity-Gap Teaser (Naïlé Titah)306, 4.25xEmergent behavior, behind-the-scenes
F10Contrarian + Historical Receipts (Jake Ward)3,083Sacred-cow takes, AI/tech cycles

Full skeletons in references/hook-formulas.md.

Steps

  1. Gather inputs. Topic, angle, draft ideas if the user has them, target audience (founders / operators / marketers), desired length (short 300-500 / medium 900-1300 / long 1500-1900 chars).
  2. Pick the formula. If the user didn't specify, suggest 2-3 formulas that fit the topic and let them pick. Show the reference engagement number next to each.
  3. Draft the post. Fill the formula skeleton with user voice. Respect the 2026 algorithm rules:

- Hook in first 210 chars (before "… see more") - 900-1,300 char sweet spot for text posts - Double line-breaks between ideas, not single - 0-2 hashtags, placed at end - No external links in body (move to first comment)

  1. Humanizer pass. Strip em dashes, AI vocab, rule-of-three, generic openers. Add at least 1 specific number, 1 named entity, 1 first-person concrete detail per 100 words.
  2. Run audit. Optionally invoke linkedin-post-audit for algorithm + voice checks before showing to user.
  3. Approval card. Show: formula used, full draft, char count, suggested posting window (Tue/Wed/Thu 7:30-9:00 AM local), reaction targets from likely commenters.
  4. On approval — adapt to the active backend. Call lib.active_backend():

- publora (PUBLORA_API_KEY set) → schedule via lib.PubloraClient.create_post with LinkedIn platformId. If scheduledTime omitted, Publora posts ~90s in the future. - manual (no backend configured — the default) → output the approved post via lib.manual_mode_message(draft_text, target_url="https://www.linkedin.com/post/new/", kind="post"). User pastes directly into LinkedIn's post composer. Do NOT attempt to publish programmatically. - diy (LINKEDIN_SKILLS_CUSTOM_POSTER set) → invoke the custom poster with the post content + optional media URLs.

Hard rules (from user feedback)

  • No em dashes. Ever. Period.
  • Capitalize all names, companies, products.
  • Never frame LinkedIn as inferior in a LinkedIn post (algo penalty).
  • 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.
  • Include at least one moment of real vulnerability or concrete stakes — pure insight posts don't land in 2026.
  • Vary sentence length aggressively. Mix 3-word sentences and 25-word sentences.

Anti-patterns (skill will refuse)

  • All-caps first line ("THIS CHANGED EVERYTHING.")
  • Em dashes anywhere
  • "In today's fast-paced world" openers
  • Rule-of-three lists without receipts
  • "Game-changer", "deep dive", "leverage", "fundamentally"
  • External links in the body
  • Reused engagement-bait closers ("tag someone who needs this")

Resources

  • references/hook-formulas.md — all 10 formula skeletons with worked examples
  • references/algorithm-heuristics.md — 2026 posting rules (timing, format, length)
  • references/humanizer-checklist.md — the full scrub list
  • Upstream: ../../corporate-knowledge/personal/knowledge/linkedin/serge/2026-04-13-viral-drafts/ — canonical reference drafts

Related skills

  • linkedin-post-audit — run this on any draft before publishing
  • linkedin-humanizer — aggressive AI-tell scrubber
  • linkedin-hook-extractor — reverse-engineer a hook from a viral post you admire

平台分布

OpenClaw

74.09%
按下载量换算713

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills