Linkedin Post Writer

Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing. Do NOT use for X/Twitter threads, newsletters, or blog posts — those need different length and hook rules.

116 stars 35 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add aakashg/pm-claude-skills --skill linkedin-post-writer
Manual install
git clone --depth 1 https://github.com/aakashg/pm-claude-skills.git /tmp/pm-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-claude-skills/skills/linkedin-post-writer ~/.claude/skills/linkedin-post-writer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# LinkedIn Post Writer

Turn a rough idea into one publishable LinkedIn post: one hook, one format, one CTA.

## Step 0 — Read first

Read these before writing a single line. Do not write from memory of "how LinkedIn posts go."

| Source | Path | What to extract |
|--------|------|-----------------|
| Project context | `CLAUDE.md` | Who the user is, their product, banned words, audience |
| Post patterns | `references/post-patterns.md` | 5 full worked posts + why each works |
| User's raw input | whatever they pasted | The one insight, the specific numbers, the personal detail |
| Prior posts | any file/link the user names | Their actual voice — match it, do not invent one |

If `references/post-patterns.md` is missing, say so and proceed with the worked example below only.

## Constraints

These are mandatory. Violating any one means the draft is not done.

- Hook is ONE line. Two-line hooks lose reach. No exceptions.
- Total body 800–1,300 characters. Under 800 reads thin; over 1,300 truncates in feed.
- Exactly ONE call to action. Not two, not "and follow me."
- Zero or one emoji. Zero is the default.
- No paragraph longer than 3 lines.
- The post must contain at least one specific number, name, or timeframe.
- Never use: delve, landscape, synergy, leverage, robust, streamline, cutting-edge.
- Never open with "I'm excited to announce" or "Thrilled to share."
- No hashtags in the body. If requested, 3–5 after a line break at the end.
Read the full skill on GitHub

Details

Skill name
linkedin-post-writer
Path
skills/linkedin-post-writer/SKILL.md
License
MIT
Repo updated
8 August 2026

FAQ

What does the Linkedin Post Writer skill do?

Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing. Do NOT use for X/Twitter threads, newsletters, or blog posts — those need different length and hook rules.

How do I install the Linkedin Post Writer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add aakashg/pm-claude-skills --skill linkedin-post-writer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Linkedin Post Writer popular?

It lives in aakashg/pm-claude-skills, which has 116 GitHub stars and 35 forks.

Related skills

Idea Validator

116

aakashg/pm-claude-skills

Use when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something. Do NOT use for prioritizing an existing backlog or reviewing a shipped feature — those need RICE scoring or a design review instead.

Testing & QA35

Product Designer

116

aakashg/pm-claude-skills

Use when the user asks to review a design, critique a UI or mockup, give design feedback, or check a screen for usability and accessibility issues. Do NOT use for visual brand or aesthetic preference debates, or for reviewing copy before layout is settled.

Frontend & Design35

Prompt Engineer

116

aakashg/pm-claude-skills

Use when the user asks to improve, optimize, rewrite, debug, or shorten a prompt, or asks why a prompt is producing bad output. Do NOT use for writing a Claude Code SKILL.md — that needs skill structure rules, not prompt techniques.

AI, LLMs & Agents35

Merge Docs

155

serpro69/claude-toolbox

Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.

Writing & ContentIn 1 list30

Document

155

serpro69/claude-toolbox

After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.

Writing & ContentIn 1 list30

Review Spec

155

serpro69/claude-toolbox

Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.

Writing & ContentIn 1 list30

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.