linkedin-content-creator
SKILL.md
LinkedIn Content Creator
Draft high-performing B2B LinkedIn content for founder-led personal accounts and company pages.
Step 1: Identify the Author
Before writing anything, confirm who is posting:
- If the author has a profile in
references/voice-profiles.md, read it and match their voice. - If the author is new (no existing profile), ask:
- "Who is the author? Can you share their LinkedIn or a few past posts?"
- If samples are available, analyze and create a voice profile (append to
references/voice-profiles.md). - If no samples, ask the 5 voice-profiling questions listed in that file.
- If the post is for a company page, use the company voice section in
references/voice-profiles.md.
Never skip this step. Voice match is the difference between content that sounds authentic and content that gets ignored.
Step 2: Draft the Post
- Read
references/post-formats.mdfor hook patterns, format guidance, and ICP context. - Read
references/creator-analysis.mdif the user wants style inspiration or is exploring approaches. - Draft the content:
- Always present 3 hook options first. Let the user pick or indicate a preference.
- For complex or ambiguous briefs, present 2-3 short outlines (3-4 bullet points each) before writing the full draft. Ask which direction to develop.
- Write the full post body using the selected hook and direction.
- Suggest a format (text-only, +image, carousel, etc.) with rationale.
- Flag the funnel position (TOFU/MOFU/BOFU) so it fits the user's content plan.
Input Types
Drafting requests may arrive as any of:
- A topic or theme from a content planner
- A link to content for inspiration or analysis
- Raw data, metrics, or customer story details
- A rough outline or bullet points
- A voice memo transcript
Adapt the workflow to the input. If the input is rich (detailed customer story), go straight to hooks. If it's thin (just a topic), ask 1-2 clarifying questions before drafting.
Step 3: Review and Refine
After the user selects a direction:
- Write the full draft in the author's voice
- Check against anti-patterns in
references/post-formats.md - Ensure the post is 200-400 words (sweet spot) unless intentionally longer
- Verify whitespace, readability, and mobile-friendliness (short paragraphs, line breaks)
When asked to review/improve an existing draft:
- Evaluate: hook strength, voice authenticity, specificity, whitespace, CTA clarity
- Provide specific rewrites, not just feedback
- Call out anti-patterns by name
Reference Files
| File | When to read | Contents |
|---|---|---|
references/voice-profiles.md |
Every drafting request — match the author's voice | Author-specific voice profiles (Everest, Stitchi company page, + any added authors) |
references/post-formats.md |
Every drafting request — format and structure | Hook patterns, formats, ICP context, content types ranked by effectiveness, anti-patterns |
references/creator-analysis.md |
Style inspiration or strategy discussions | Analysis of Tyler Denk, Alex Lieberman, Jenny Rothenberg, Danny Sheridan, beehiiv company page |
Key Principles
- Hook is everything. First 1-2 lines determine if anyone reads the rest.
- Voice match is non-negotiable. Every author sounds different. Never write in a generic "LinkedIn voice."
- Specificity wins. Real numbers, real stories, real names beat vague generalities every time.
- One idea per post. Depth over breadth.
- Whitespace is your friend. Short paragraphs (1-3 sentences). Line breaks. Scannable on mobile.
- Earn the CTA. Provide value first. Most posts should have no CTA at all.
- Write for the ICP, not for other founders. The audience is marketing, HR, sales, and ops leaders — not startup Twitter.
Formatting Rules
- Short paragraphs (1-3 sentences max)
- Line break between every paragraph
- Hashtags: 0-3 max, only if genuinely relevant
- Emojis: sparingly and purposefully (1-3 per post, not every line)
- No markdown headers (LinkedIn doesn't render them)
- Bold (text) works on LinkedIn — use for key phrase emphasis
- Target 1,200-2,500 characters (~200-400 words) unless intentionally going long
Weekly Installs
1
Repository
stitchi-co/skillsFirst Seen
6 days ago
Security Audits
Installed on
amp1
cline1
openclaw1
trae-cn1
opencode1
cursor1