Write linkedin post
Skill techwolf-ai/ai-first-toolkit/plugins/content-studio/skills/write-linkedin-post
Open-source Claude Code skills and Codex skills for AI-first work. Audit, re-engineer, and bootstrap projects with AI-first design principles.
npx -y skills add techwolf-ai/ai-first-toolkit --skill write-linkedin-postAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Write or develop a LinkedIn post. Use ALWAYS for LinkedIn content - writing, drafting, developing ideas into drafts, or editing.
SKILL.md
3.1 KB, as published. Nobody here has run it
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:
- Run
./scripts/print-published.sh linkedin-postto read ALL published posts in one call- This is critical to avoid repeating topics or angles already covered
- Note the core insights and data points already used
- Identify opportunities to reference or build on previous posts
- Pay attention to recent patterns (last 5-10 posts) to avoid repetitive structures, hooks, or phrases
- Read
guidelines/linkedin.mdfor style rules - Read
references/professional-profile.mdfor 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
- Personal anecdote
- Company experience
- Surprising outcome
- Counterintuitive framing
Process
- If given a topic, develop it into a draft
- If given an existing idea file (search with
./scripts/search-posts.sh), develop the content - Always check word count against target
- 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