linkedin-post
Use when the user wants to write a LinkedIn post from an idea, a link, a project win, or a lesson. Produces three variants in the user's voice with hooks that don't sound like every other post.
SKILL.mdskills/linkedin-post/SKILL.md
GitHubLinkedIn Post
Write posts that sound like the user, not like LinkedIn. Three variants so they can pick, not edit.
Step 1 — Load context
Read .solo/business.md for tone, services, and who the audience is (ideal clients — posts should be useful to them, not to peers).
Step 2 — Get the seed
One of: an idea, a link/article (fetch and read it), a project outcome, a mistake and lesson, a question the user keeps getting asked. If the seed is vague ("post about AI"), ask for the one specific thing they believe that others might not.
Step 3 — Write three variants
Save to content/linkedin/<YYYY-MM-DD>-<slug>.md. Each variant:
- Hook (first line, before "see more"): a specific claim, number, or moment. Under 12 words. No questions like "Ever wondered…?", no "Unpopular opinion:", no "I've been thinking a lot about…".
- Body: 80–180 words. Short paragraphs (1–2 lines). One idea. Concrete example from the user's work if the seed allows.
- Close: either a plain takeaway or a real question the user wants answered. No "Agree?" No "Thoughts?"
- No hashtags unless business.md says to use them. Max 3 if so.
Variant angles:
- A — Story: what happened, what it taught. Past tense, first person.
- B — Contrarian/insight: the thing most people get wrong, and the better way.
- C — Practical: a numbered mini-how-to (3–5 steps) the audience can use today.
After the three, add a ## Notes line: which variant you'd post and why, in one sentence.
Tone rules
- Match business.md tone. If it says "no buzzwords", remove: game-changer, leverage, unlock, journey, thrilled, humbled, delve.
- Write like a person talking to one reader.
- No emojis unless the tone section says so.
- No fake vulnerability, no "I failed 100 times" unless it's true and specific.
Do not
- Do not write engagement-bait (polls, "comment YES", "repost if you agree").
- Do not exceed 200 words per variant.
- Do not fabricate results or client stories.