bmoir23/git-blog-posts/linkedin-style
Claude Code and agent skill by bmoir23/git-blog-posts
- community
Checking that the SKILL.md file is still in the repository.
Use when drafting or editing a LinkedIn post in the house voice.
Install
npx vskill@latest install bmoir23/git-blog-posts/linkedin-styleSKILL.md
The same SKILL.md was published earlier as vercel-labs/eve-content-agent-template/linkedin-style.
LinkedIn voice & style
When writing or editing a LinkedIn post:
- Hook first. Only ~200 characters show on mobile before "…see more" — the first line
decides whether anyone expands the post. Open on the surprising stat, the bold claim, an open loop, or a one-line story setup. No throat-clearing, no "A few thoughts on…".
- One idea per post. If you have two, write two posts. How-tos and concrete lists land best.
- Short lines and single-sentence paragraphs, with white space between them — it's read on a
phone, and the gaps keep it scannable.
- Concrete and specific: a number, a result, a before/after, a moment. No vague inspiration.
- Deliver the value in the feed. Self-contained text is what people engage with — don't make
the reader leave to get the point.
- End with a genuine question or a clear takeaway, not a "thoughts? 👇" prompt. A real question
earns comments, and comments move the post further than likes.
- At most one emoji, and only if it earns its place. 3–5 relevant hashtags max, grouped at the
end, CamelCase and specific (#BusinessWriting, not #Business) — they're topic signals, not a discovery feed.
- No "I'm humbled to announce", no engagement-bait, no "Agree?" closers or reaction-poll chains.
- Links suppress reach. When a post needs a link, put it in the first comment and say "link
in the comments" — don't put it in the body.
Structure
- Hook — the surprising claim or the moment, line one (before the fold).
- Turn — the tension, or the thing most people get wrong.
- Payoff — what you learned, with a concrete detail.
- Close — one question or one takeaway.
References
references/best-practices.md— researched tactics as a pre-flight checklist (hook, links,
hashtags, formats).
references/post-specs.md— character limits and document/carousel specs for quick lookup.references/banned-words.json— words to avoid. Read it once up front for awareness, then run
the lint_against_style tool (surface linkedin) on your draft to check it against this file before proposing the draft to the writer.
Shared references
Shared global references for all skills in the content agent. These apply regardless of the content type.
references/ai-phrases-to-avoid.md— AI-tell words, phrases, and punctuation to avoid.references/plain-english-alternatives.md— plain-English swaps for bloated or vague wording.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingagent/skills/linkedin-style/SKILL.md
Popularity
- Repository stars
- 1
- 7-day trend score
- 8
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/bmoir23/git-blog-posts/linkedin-style)