‹ 首页

write-linkedin-post

@techwolf-ai · 收录于 1 周前

Write or develop a LinkedIn post. Use ALWAYS for LinkedIn content - writing, drafting, developing ideas into drafts, or editing.

适合你,如果你需要持续产出高质量的 LinkedIn 内容来提升影响力。

/ 下载安装
write-linkedin-post.skill双击,或拖进 Claude 桌面版 / Cowork,即完成安装↓ .skill↓ .zip
用别的 agent?下载 .zip 解压,把文件夹放进它的技能目录
Claude Code~/.claude/skills/(项目级 .claude/skills/)
Codex CLI~/.codex/skills/
Cursor自动读取上面两处目录
其他工具见其文档的「skills」目录;两个下载是同一份文件,只是名字不同
/ 通过 npx 安装 校验哈希
npx oh-my-skill add techwolf-ai/ai-first-toolkit/write-linkedin-post
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- techwolf-ai/ai-first-toolkit/write-linkedin-post
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify techwolf-ai/ai-first-toolkit/write-linkedin-post
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
90GitHub stars
~693最小装载
~933含声明引用
~933文本包总量
镜像托管

怎么用

技能原文 SKILL.md作者撰写 · MIT · 8b3107b

Write LinkedIn Post

You are helping write a LinkedIn post for the author.

Before Writing (MANDATORY)

You MUST complete these steps before writing ANY content:

  1. Run ./scripts/print-published.sh linkedin-post to read ALL published posts in one call
  2. This is critical to avoid repeating topics or angles already covered
  3. Note the core insights and data points already used
  4. Identify opportunities to reference or build on previous posts
  5. Pay attention to recent patterns (last 5-10 posts) to avoid repetitive structures, hooks, or phrases
  6. Read guidelines/linkedin.md for style rules
  7. Read references/professional-profile.md for background

If developing an idea-stage post: Check if the idea's core insight or data points overlap with published posts. If so, either:

  • Find a genuinely different angle
  • Explicitly build on the previous post ("In my last post I discussed X. Here's the flip side...")
  • Recommend against developing the idea
Avoid Repetitive Patterns

When reading recent posts, actively note and vary:

Hooks: If recent posts start with similar patterns, try a different structure Sentence patterns: Vary rhythm - don't always use short punchy sentences or always use longer flowing ones Closing lines: Don't repeat formulas Transition phrases: Rotate between "Here's what...", "The pattern...", "This matters because...", etc. Structure: If recent posts all use problem-solution-takeaway, try a different arc

The goal is a consistent voice with varied execution. Each post should feel fresh while still sounding like the author.

Style Requirements
  • Target word count per guidelines/linkedin.md (typically 150-250 words)
  • Personal hook first (under 210 characters before "see more")
  • Specific > abstract
  • Conversational tone
  • No hype words ("revolutionary", "game-changing")
Hook Priority
  1. Personal anecdote
  2. Company experience
  3. Surprising outcome
  4. Counterintuitive framing
Process
  1. If given a topic, develop it into a draft
  2. If given an existing idea file (search with ./scripts/search-posts.sh), develop the content
  3. Always check word count against target
  4. Save to content/posts/ with type: linkedin-post, stage: 02-drafts
Validation

After saving the draft, run the word count checker:

scripts/check-word-count.sh <yaml-file>

Adjust the content if the word count is outside the 150-250 target.

Sub-Agent Review

Before presenting the final draft, spawn a sub-agent to review with fresh eyes. The reviewer should:

  • Check voice consistency against guidelines/linkedin.md
  • Verify the hook works in the first 210 characters
  • Flag any overlap with recently published posts
  • Check for hype words or generic phrasing

Incorporate the reviewer's feedback before finalizing.

Creating New Files

Get timestamp first:

date -u +"%Y%m%d-%H%M%S"  # For slug
date -u +"%Y-%m-%dT%H:%M:%S.000Z"  # For created/lastUpdated
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。