Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问clear审计未展示

linkedin-content链接内容

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

9,501

周安装

253

GitHub Stars

公开资料未说明

下载量

2,775
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:linkedin-content(链接内容)
来源仓库:https://github.com/inf-sh/skills
仓库路径:skills/linkedin-content
安装命令:
npx skills add inf-sh/skills --skill "linkedin-content"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

AgentSkills.tonpx skills
npx skills add inf-sh/skills --skill "linkedin-content"

简介

使用挂钩公式、格式规则和参与模式编写 LinkedIn 帖子。涵盖帖子类型、算法信号、字符限制和内容支柱。用于:LinkedIn 帖子、专业内容、思想领导力、B2B 内容、个人品牌。触发因素:linkedin帖子、linkedin内容、linkedin写作、linkedin策略、linkedin参与度、linkedin算法、linkedin挂钩、linkedin格式、思想领导力、专业内容、b2b内容、linkedin增长

SKILL.md

name
linkedin-content
description
LinkedIn post writing with hook formulas, formatting rules, and engagement patterns. Covers post types, algorithm signals, character limits, and content pillars. Use for: LinkedIn posts, professional content, thought leadership, B2B content, personal branding. Triggers: linkedin post, linkedin content, linkedin writing, linkedin strategy, linkedin engagement, linkedin algorithm, linkedin hook, linkedin formatting, thought leadership, professional content, b2b content, linkedin growth
allowed-tools
Bash(infsh *)

LinkedIn Content

Write high-engagement LinkedIn posts via inference.sh CLI.

Quick Start

curl -fsSL https://cli.inference.sh | sh && 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"
}'

Post Anatomy

┌─────────────────────────────────────┐
│ 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)                     │
└─────────────────────────────────────┘

Character Limits

ElementLimit
Post text3,000 characters
Visible before "see more"~210 characters (~2 lines on mobile)
Hashtags3-5 recommended
Comment1,250 characters
Article title100 characters
Article body125,000 characters

The first 210 characters are everything. If the hook fails, nobody clicks "see more."

Hook Formulas

What Works

FormulaExample
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."

What Fails

❌ "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

Formatting Rules

Line Breaks Are Your Best Friend

❌ 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."

Formatting Guidelines

RuleWhy
One sentence per lineEasier to scan on mobile
Blank line between paragraphsVisual breathing room
Short paragraphs (1-2 sentences)Mobile readability
Use line breaks for dramatic effectCreates pacing and suspense
Bold key phrases sparinglyDraws eye to important points
Numbered lists for tipsScannable, shareable
Avoid walls of textNobody reads them

Post Types (Ranked by Engagement)

Post TypeEngagementBest For
Personal story + lessonVery HighBuilding connection, authenticity
Contrarian takeHighStarting conversations, visibility
Carousel (document post)HighEducational content, tips
List/tips (numbered)HighActionable value, saves
PollMedium-HighEasy engagement, data gathering
Photo + storyMediumHumanizing, events
Video (native)MediumDemonstrations, personality
Link postLowDriving traffic (algorithm penalizes)
ReshareVery LowDon't bother — write original

Link Posts Strategy

LinkedIn penalizes posts with links (reduces reach). Workarounds:

  1. Comment method: Post without link, add link as first comment, edit post to say "Link in comments"
  2. No-link method: Summarize the content in the post itself, mention "DM for link"
  3. If you must link: Put it at the very end, after strong standalone content

Content Pillars

Every LinkedIn creator should have 3-5 pillars they rotate through:

PillarWhat It CoversExample
ExpertiseIndustry knowledge, how-tos"5 database patterns every engineer should know"
StoriesPersonal experiences, failures, wins"The hardest feedback I ever received"
OpinionsTakes on industry trends, contrarian views"AI won't replace engineers. Bad managers will."
Behind the scenesBuilding in public, process"Here's our actual sprint retrospective format"
Curated insightsTrends, data, research summaries"I analyzed 500 job postings. Here's what changed."

Algorithm Signals

SignalImpactHow
Dwell timeVery HighLonger posts that people read fully
CommentsVery HighAsk questions, create discussion
SavesHighActionable, reference-worthy content
"See more" clicksHighStrong hook that makes people expand
SharesMediumRelatable, quotable content
ReactionsMediumEasy to get but weighted less
External linksNegativeReduces reach — put links in comments
Editing after postingNegativeDon't edit within first hour
Posting frequency3-5x/weekDaily is fine, more than 1/day hurts

Posting Schedule

DayBest Time (your audience's timezone)
Tuesday-Thursday7-8 AM, 12 PM, 5-6 PM
Monday8 AM (people catching up)
Friday7-8 AM (before checkout)
WeekendSkip or light content

Engage in comments for 30-60 minutes after posting — this is more important than the post itself.

Visual Content

# 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&apos;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
}'

CTA Formulas

End every post with engagement driver:

CTA TypeExample
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?"

Common Mistakes

MistakeProblemFix
Weak hookNobody clicks "see more"Use hook formulas above
Wall of textUnreadable on mobileOne sentence per line, blank lines between
Links in main postAlgorithm reduces reachPut links in first comment
Too many hashtagsLooks spammy3-5 relevant hashtags max
Corporate jargon"Leveraging synergies" = instant scroll pastWrite like you talk
Only self-promotionAudience stops engaging80% value, 20% promotion
No CTANo engagement directionAlways end with a question or ask
Resharing without addingNear-zero reachWrite original posts, quote instead
Posting and disappearingKills comment momentumEngage for 30-60 min after posting
Being generic"Hard work pays off" = invisibleSpecific stories and data

Related Skills

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

66.96%
按下载量换算1,858

Cursor

26.4%
按下载量换算733

安全审计

暂无安全审计结果可展示。

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills