Linkedin post
Skill clairem0/technically-curious-skills/content/linkedin-post
Draft LinkedIn posts with a style guide for voice and structure. Use when the user says "draft a LinkedIn post", "linkedin post", or wants to write something for LinkedIn.From its SKILL.md
npx -y skills add clairem0/technically-curious-skills --skill linkedin-postAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.7 KB, 591 tokens by cl100k_base, as published. Nobody here has run it
LinkedIn Post
Draft LinkedIn posts with your voice and style. Loads a style guide before drafting so every post sounds like you, not like AI.
Connectors
No external connectors needed. This skill drafts posts — you publish them manually on LinkedIn.
Configuration
Load
style-guide.mdbefore drafting. It defines your voice, structure patterns, and what works on LinkedIn.
No env.md values needed for this skill.
Workflow
Step 1: Load Context
Read style-guide.md for your tone, structure patterns, and examples.
Step 2: Understand Intent
- What's the topic or angle?
- Is this standalone, a cross-promotion, or a reshare?
- Any specific hook or framing you want?
If the user gave enough context, skip to drafting.
Step 3: Draft
Write in your LinkedIn voice (per style guide):
- Strong hook in the first 2-3 lines (before the "see more" fold) — this determines whether anyone reads the rest
- Structured body — numbered lists, bullet points, or short paragraphs. Each point is digestible.
- Conversational credibility — personal experience + practical advice
- Engagement close — end with a question or call to action
- Links in comments — not the main post (better algorithmic reach)
Show the draft for review before anything else.
Step 4: Refine
- Iterate based on feedback
- Check length (aim for 1,000-1,500 characters for best engagement; max 3,000)
- Ensure the hook works above the fold
- Draft a first comment with any links (Substack, resources, etc.)
Step 5: Deliver
Deliver the final draft + first comment text. The user posts it themselves.
Error Handling
| Scenario | Response |
|---|---|
| Topic is too broad | Help narrow it — "What's the one thing you want someone to take away?" |
| Post is too long | Cut supporting points, keep the hook and close strong |
| User doesn't like the tone | Ask what felt off, adjust — and update the style guide if it's a recurring note |
Customization Notes
How to adapt this skill to your own setup.
- Style guide is everything —
style-guide.mdis where your voice lives. Update it with your tone, your examples, and what works for your audience. The skill is only as good as this file. - Post templates — The style guide includes structure templates (myth-busting, tool discovery, workflow share). Add your own formats as you discover what gets engagement.
- Cross-promotion — If you publish on multiple platforms (Substack, blog), add a cross-promotion template to the style guide.