From content-studio
Generates LinkedIn post drafts by checking published posts to avoid repetition, following linkedin.md style guidelines, targeting 150-250 words, and incorporating sub-agent review.
npx claudepluginhub techwolf-ai/ai-first-toolkitThis skill uses the workspace's default tool permissions.
You are helping write a LinkedIn post for the author.
Writes LinkedIn posts matching user's voice from about-me.md and voice.md files. Triggers on 'write a post', topic requests, or context dumps like notes/transcripts. Outputs post in code block.
Drafts viral LinkedIn posts using 2026 hook formulas like platform-risk anaphora, R.I.P. obituary, and year-over-year pivot. Humanizes drafts, shows approval, and schedules via Publora. Use for new posts, hooks, or formats.
Generates two viral LinkedIn posts in proven formats with voice matching from templates. Use for creating engaging, high-performing LinkedIn content.
Share bugs, ideas, or general feedback.
You are helping write a LinkedIn post for the author.
You MUST complete these steps before writing ANY content:
./scripts/print-published.sh linkedin-post to read ALL published posts in one call
guidelines/linkedin.md for style rulesreferences/professional-profile.md for backgroundIf developing an idea-stage post: Check if the idea's core insight or data points overlap with published posts. If so, either:
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.
guidelines/linkedin.md (typically 150-250 words)./scripts/search-posts.sh), develop the contentAfter 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.
Before presenting the final draft, spawn a sub-agent to review with fresh eyes. The reviewer should:
guidelines/linkedin.mdIncorporate the reviewer's feedback before finalizing.
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