linkedin-content by inferen-sh/skills
npx skills add https://github.com/inferen-sh/skills --skill linkedin-content通过 inference.sh CLI 撰写高互动率的 LinkedIn 帖子。
需要 inference.sh CLI (
infsh)。安装说明
infsh login
# 研究 LinkedIn 热门内容模式
infsh app run tavily/search-assistant --input '{
"query": "LinkedIn viral post examples 2024 high engagement patterns"
}'
# 发布到 X（交叉发布参考）
infsh app run x/post-create --input '{
"text": "Your cross-posted version here"
}'
┌─────────────────────────────────────┐
│ 钩子（前 1-2 行） │ ← 在“...查看更多”之前可见
│ │
│ ...查看更多 ─────────────────────── │ ← 点击门槛
│ │
│ 正文（故事/价值） │
│ - 使用换行符格式化 │
│ - 短段落（1-2 句话） │
│ - 列表或编号要点 │
│ │
│ 行动号召（最后 1-2 行） │ ← 请求互动
│ │
│ #话题标签（3-5 个） │
└─────────────────────────────────────┘
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者，精准高效
| 元素 | 限制 |
|---|---|
| 帖子正文 | 3000 个字符 |
| “查看更多”前可见部分 | ~210 个字符（移动端约 2 行） |
| 话题标签 | 建议 3-5 个 |
| 评论 | 1250 个字符 |
| 文章标题 | 100 个字符 |
| 文章正文 | 125,000 个字符 |
前 210 个字符至关重要。 如果钩子失败，没人会点击“查看更多”。
| 公式 | 示例 |
|---|---|
| 逆向观点 | “不受欢迎的观点：代码审查是浪费时间。” |
| 个人故事开场 | “我在一个周二被解雇了。这是发生过的最好的事。” |
| 惊人数据 | “92% 的初创公司会失败。但原因并非你所想。” |
| 列表承诺 | “我招聘过 200 多名工程师。以下是我关注的 5 个危险信号。” |
| 大胆陈述 | “你的简历不重要。重要的是这个。” |
| 前后对比 | “3 年前我一个面试都拿不到。昨天我拒绝了一个 FAANG 的录用通知。” |
| 模式中断 | “停。在你发送那封冷邮件之前，先读读这个。” |
❌ “激动地宣布，我们很高兴分享……”（官方套话）
❌ “在当今快速发展的格局中……”（陈词滥调，言之无物）
❌ “我想花点时间……”（节奏慢，无钩子）
❌ “刚刚发布了一篇新博客文章！”（无价值主张）
❌ 以话题标签或表情符号开头
❌ 密集段落：
“我上周学到了关于领导力的一些重要东西。我的团队在截止日期前挣扎，我没有选择更努力地推动，而是决定缩减范围。结果令人难以置信——我们交付得更快，质量也更好。有时少即是多。”
✅ 为 LinkedIn 格式化：
“我上周学到了关于领导力的一些东西。
我的团队在截止日期前挣扎。
我没有选择更努力地推动，而是缩减了范围。
结果呢？
我们交付得更快。
而且质量更好了。
有时少即是多。”
| 规则 | 原因 |
|---|---|
| 每行一句话 | 在移动端更易于浏览 |
| 段落间空行 | 视觉呼吸空间 |
| 短段落（1-2 句话） | 移动端可读性 |
| 使用换行制造戏剧效果 | 创造节奏和悬念 |
| 有节制地加粗关键短语 | 将视线引向重点 |
| 使用编号列表提供建议 | 可浏览，可分享 |
| 避免大段文字墙 | 没人会读 |
| 帖子类型 | 互动率 | 最佳用途 |
|---|---|---|
| 个人故事 + 教训 | 非常高 | 建立联系，展现真实性 |
| 逆向观点 | 高 | 开启对话，提高可见度 |
| 轮播图（文档帖子） | 高 | 教育性内容，技巧分享 |
| 列表/技巧（编号） | 高 | 可操作的价值，值得收藏 |
| 投票 | 中高 | 易于互动，数据收集 |
| 照片 + 故事 | 中 | 人性化，事件分享 |
| 视频（原生） | 中 | 演示，展现个性 |
| 链接帖子 | 低 | 引流（算法会降权） |
| 转发 | 非常低 | 别费劲——写原创内容 |
LinkedIn 会降低包含链接的帖子的曝光（减少触及范围）。变通方法：
每个 LinkedIn 创作者都应该有 3-5 个轮流使用的内容支柱：
| 支柱 | 涵盖内容 | 示例 |
|---|---|---|
| 专业知识 | 行业知识，操作指南 | “每个工程师都应该知道的 5 种数据库模式” |
| 故事 | 个人经历，失败，成功 | “我收到过的最难听的反馈” |
| 观点 | 对行业趋势的看法，逆向观点 | “AI 不会取代工程师。糟糕的管理者才会。” |
| 幕后花絮 | 公开构建过程，流程 | “这是我们实际的冲刺回顾会格式” |
| 精选洞察 | 趋势，数据，研究总结 | “我分析了 500 个职位描述。以下是变化。” |
| 信号 | 影响 | 方法 |
|---|---|---|
| 停留时间 | 非常高 | 人们完整阅读的长帖子 |
| 评论 | 非常高 | 提问，创造讨论 |
| 收藏 | 高 | 可操作、值得参考的内容 |
| “查看更多”点击 | 高 | 强有力的钩子促使人们展开 |
| 分享 | 中 | 有共鸣、可引用的内容 |
| 反应 | 中 | 容易获得但权重较低 |
| 外部链接 | 负面 | 降低触及范围——将链接放在评论中 |
| 发布后编辑 | 负面 | 发布后一小时内不要编辑 |
| 发布频率 | 每周 3-5 次 | 每天一次没问题，超过一次有害 |
| 日期 | 最佳时间（你受众的时区） |
|---|---|
| 周二至周四 | 上午 7-8 点，中午 12 点，下午 5-6 点 |
| 周一 | 上午 8 点（人们正在跟进） |
| 周五 | 上午 7-8 点（下班前） |
| 周末 | 跳过或发布轻松内容 |
发布后在评论区互动 30-60 分钟——这比帖子本身更重要。
# 为 LinkedIn 帖子生成视觉内容
infsh app run infsh/html-to-image --input '{
"html": "<div style=\"width:1080px;height:1080px;background:#0f172a;display:flex;align-items:center;justify-content:center;padding:80px;font-family:system-ui;color:white;text-align:center\"><div><h1 style=\"font-size:56px;font-weight:900;line-height:1.2;margin:0\">The best code is the code you don't write</h1><p style=\"font-size:22px;opacity:0.5;margin-top:24px\">— Every senior engineer</p></div></div>"
}'
# 为个人帖子生成专业照片
infsh app run falai/flux-dev-lora --input '{
"prompt": "candid professional photo, person speaking at a conference podium, audience in background blurred, natural stage lighting, authentic moment, corporate event photography",
"width": 1200,
"height": 900
}'
每条帖子都以互动驱动结尾：
| 行动号召类型 | 示例 |
|---|---|
| 提问 | “你收到过的最糟糕的职业建议是什么？” |
| 寻求认同 | “同意还是不同意？” |
| 请求分享 | “如果引起共鸣，请转发 ♻️” |
| 提示收藏 | “为你的下一个[情况]收藏这个 🔖” |
| 征求建议 | “你会在这个列表中添加什么？” |
| 询问经历 | “你遇到过这种情况吗？” |
| 错误 | 问题 | 解决方法 |
|---|---|---|
| 钩子薄弱 | 没人点击“查看更多” | 使用上面的钩子公式 |
| 文字墙 | 在移动端难以阅读 | 每行一句话，段落间空行 |
| 主帖中包含链接 | 算法降低触及范围 | 将链接放在第一条评论中 |
| 话题标签过多 | 看起来像垃圾信息 | 最多 3-5 个相关话题标签 |
| 官方套话 | “利用协同效应” = 立刻被划走 | 像说话一样写作 |
| 只有自我推广 | 受众停止互动 | 80% 价值，20% 推广 |
| 没有行动号召 | 没有互动引导 | 总是以提问或请求结尾 |
| 转发而不添加内容 | 触及率几乎为零 | 写原创帖子，引用代替 |
| 发布后消失 | 扼杀评论势头 | 发布后互动 30-60 分钟 |
| 内容泛泛 | “努力就有回报” = 隐形 | 具体的故事和数据 |
npx skills add inference-sh/skills@social-media-carousel
npx skills add inference-sh/skills@content-repurposing
npx skills add inference-sh/skills@twitter-thread-creation
浏览所有应用：infsh app list
每周安装量
7.0K
代码库
GitHub 星标数
182
首次出现
12 天前
安全审计
安装于
claude-code5.6K
gemini-cli5.0K
codex5.0K
amp5.0K
opencode5.0K
github-copilot5.0K
Write high-engagement LinkedIn posts via inference.sh CLI.
Requires inference.sh CLI (
infsh). Install instructions
infsh login
# Research trending LinkedIn content patterns
infsh app run tavily/search-assistant --input '{
"query": "LinkedIn viral post examples 2024 high engagement patterns"
}'
# Post to X (cross-posting reference)
infsh app run x/post-create --input '{
"text": "Your cross-posted version here"
}'
┌─────────────────────────────────────┐
│ HOOK (first 1-2 lines) │ ← Visible before "...see more"
│ │
│ ...see more ─────────────────────── │ ← The click gate
│ │
│ BODY (story/value) │
│ - Formatted with line breaks │
│ - Short paragraphs (1-2 sentences) │
│ - Lists or numbered points │
│ │
│ CTA (last 1-2 lines) │ ← Ask for engagement
│ │
│ #hashtags (3-5) │
└─────────────────────────────────────┘
| Element | Limit |
|---|---|
| Post text | 3,000 characters |
| Visible before "see more" | ~210 characters (~2 lines on mobile) |
| Hashtags | 3-5 recommended |
| Comment | 1,250 characters |
| Article title | 100 characters |
| Article body | 125,000 characters |
The first 210 characters are everything. If the hook fails, nobody clicks "see more."
| Formula | Example |
|---|---|
| Contrarian opinion | "Unpopular opinion: code reviews are a waste of time." |
| Personal story opening | "I got fired on a Tuesday. Best thing that ever happened." |
| Surprising stat | "92% of startups fail. But not for the reason you think." |
| List promise | "I've hired 200+ engineers. Here are 5 red flags I look for." |
| Bold statement | "Your resume doesn't matter. Here's what does." |
| Before/after | "3 years ago I couldn't get a single interview. Yesterday I turned down a FAANG offer." |
| Pattern interrupt | "Stop. Before you send that cold email, read this." |
❌ "Excited to announce that we are pleased to share..." (corporate speak)
❌ "In today's rapidly evolving landscape..." (cliché, says nothing)
❌ "I'd like to take a moment to..." (slow, no hook)
❌ "Just published a new blog post!" (no value proposition)
❌ Starting with a hashtag or emoji
❌ Dense paragraph:
"I learned something important about leadership last week. My team was struggling with a deadline and instead of pushing harder, I decided to remove scope. The result was incredible — we shipped faster and the quality was better. Sometimes less really is more."
✅ Formatted for LinkedIn:
"I learned something about leadership last week.
My team was struggling with a deadline.
Instead of pushing harder, I removed scope.
The result?
We shipped faster.
And the quality was BETTER.
Sometimes less really is more."
| Rule | Why |
|---|---|
| One sentence per line | Easier to scan on mobile |
| Blank line between paragraphs | Visual breathing room |
| Short paragraphs (1-2 sentences) | Mobile readability |
| Use line breaks for dramatic effect | Creates pacing and suspense |
| Bold key phrases sparingly | Draws eye to important points |
| Numbered lists for tips | Scannable, shareable |
| Avoid walls of text | Nobody reads them |
| Post Type | Engagement | Best For |
|---|---|---|
| Personal story + lesson | Very High | Building connection, authenticity |
| Contrarian take | High | Starting conversations, visibility |
| Carousel (document post) | High | Educational content, tips |
| List/tips (numbered) | High | Actionable value, saves |
| Poll | Medium-High | Easy engagement, data gathering |
| Photo + story | Medium | Humanizing, events |
| Video (native) | Medium | Demonstrations, personality |
| Link post |
LinkedIn penalizes posts with links (reduces reach). Workarounds:
Every LinkedIn creator should have 3-5 pillars they rotate through:
| Pillar | What It Covers | Example |
|---|---|---|
| Expertise | Industry knowledge, how-tos | "5 database patterns every engineer should know" |
| Stories | Personal experiences, failures, wins | "The hardest feedback I ever received" |
| Opinions | Takes on industry trends, contrarian views | "AI won't replace engineers. Bad managers will." |
| Behind the scenes | Building in public, process | "Here's our actual sprint retrospective format" |
| Curated insights | Trends, data, research summaries | "I analyzed 500 job postings. Here's what changed." |
| Signal | Impact | How |
|---|---|---|
| Dwell time | Very High | Longer posts that people read fully |
| Comments | Very High | Ask questions, create discussion |
| Saves | High | Actionable, reference-worthy content |
| "See more" clicks | High | Strong hook that makes people expand |
| Shares | Medium | Relatable, quotable content |
| Reactions | Medium | Easy to get but weighted less |
| External links | Negative | Reduces reach — put links in comments |
| Editing after posting |
| Day | Best Time (your audience's timezone) |
|---|---|
| Tuesday-Thursday | 7-8 AM, 12 PM, 5-6 PM |
| Monday | 8 AM (people catching up) |
| Friday | 7-8 AM (before checkout) |
| Weekend | Skip or light content |
Engage in comments for 30-60 minutes after posting — this is more important than the post itself.
# Generate a visual for a LinkedIn post
infsh app run infsh/html-to-image --input '{
"html": "<div style=\"width:1080px;height:1080px;background:#0f172a;display:flex;align-items:center;justify-content:center;padding:80px;font-family:system-ui;color:white;text-align:center\"><div><h1 style=\"font-size:56px;font-weight:900;line-height:1.2;margin:0\">The best code is the code you don't write</h1><p style=\"font-size:22px;opacity:0.5;margin-top:24px\">— Every senior engineer</p></div></div>"
}'
# Generate a professional photo for a personal post
infsh app run falai/flux-dev-lora --input '{
"prompt": "candid professional photo, person speaking at a conference podium, audience in background blurred, natural stage lighting, authentic moment, corporate event photography",
"width": 1200,
"height": 900
}'
End every post with engagement driver:
| CTA Type | Example |
|---|---|
| Question | "What's the worst career advice you've received?" |
| Agreement check | "Agree or disagree?" |
| Share request | "Repost if this resonates ♻️" |
| Save prompt | "Save this for your next [situation] 🔖" |
| Recommendation ask | "What would you add to this list?" |
| Experience ask | "Has this happened to you?" |
| Mistake | Problem | Fix |
|---|---|---|
| Weak hook | Nobody clicks "see more" | Use hook formulas above |
| Wall of text | Unreadable on mobile | One sentence per line, blank lines between |
| Links in main post | Algorithm reduces reach | Put links in first comment |
| Too many hashtags | Looks spammy | 3-5 relevant hashtags max |
| Corporate jargon | "Leveraging synergies" = instant scroll past | Write like you talk |
| Only self-promotion | Audience stops engaging | 80% value, 20% promotion |
| No CTA | No engagement direction | Always end with a question or ask |
| Resharing without adding | Near-zero reach | Write original posts, quote instead |
| Posting and disappearing | Kills comment momentum |
npx skills add inference-sh/skills@social-media-carousel
npx skills add inference-sh/skills@content-repurposing
npx skills add inference-sh/skills@twitter-thread-creation
Browse all apps: infsh app list
Weekly Installs
7.0K
Repository
GitHub Stars
182
First Seen
12 days ago
Security Audits
Gen Agent Trust HubPassSocketWarnSnykFail
Installed on
claude-code5.6K
gemini-cli5.0K
codex5.0K
amp5.0K
opencode5.0K
github-copilot5.0K
48,100 周安装
| Low |
| Driving traffic (algorithm penalizes) |
| Reshare | Very Low | Don't bother — write original |
| Negative |
| Don't edit within first hour |
| Posting frequency | 3-5x/week | Daily is fine, more than 1/day hurts |
| Engage for 30-60 min after posting |
| Being generic | "Hard work pays off" = invisible | Specific stories and data |