New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Linkedin Post Writer

by aakashg in aakashg/pm-claude-skills

A skill your agent uses 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.

MITAuto-check passedWriting & Content

Install Linkedin Post Writer

skills CLI
$ npx skills add aakashg/pm-claude-skills --skill linkedin-post-writer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aakashg/pm-claude-skills linkedin-post-writer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aakashg/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/linkedin-post-writer .claude/skills/linkedin-post-writer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
linkedin-post-writer
GitHub stars
112
Token cost
~1.8k tokens
SKILL.md length
858 words
Files
2 (incl. references)
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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.

  • Works in 3 steps: Read first → Gather → Pick the format
  • The user asks to write
  • SKILL.md covers Step 0 — Read first, Constraints, Existence check and Step 1 — Gather, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Linkedin Post Writer is an agent skill from aakashg/pm-claude-skills. 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.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/post-patterns.md`).

It sits in Writing & Content, covering Social media posts. It works with LinkedIn. The repository describes itself as: 5 Claude Code skills for product managers. Drop them in your .claude/skills/ folder and go. The licence is MIT.

When your agent uses it

  • The user asks to write
  • Rewrite a LinkedIn post
  • An article into a LinkedIn post
  • Fix a hook that is not landing

Example prompts

  • “/linkedin-post-writer”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Read first
  2. Gather
  3. Pick the format

What it can do on your machine

Read from SKILL.md and the folder at commit 64deebf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Linkedin Post Writer loads about 1.8k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 858 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~69
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aakashg/pm-claude-skills at commit 64deebf, republished under its MIT licence (© aakashg). 858 words, ~1,833 tokens.

Download SKILL.mdSave it as .claude/skills/linkedin-post-writer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
linkedin-post-writer
description
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.

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."

SourcePathWhat to extract
Project contextCLAUDE.mdWho the user is, their product, banned words, audience
Post patternsreferences/post-patterns.md5 full worked posts + why each works
User's raw inputwhatever they pastedThe one insight, the specific numbers, the personal detail
Prior postsany file/link the user namesTheir 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.
  • Lead with the insight, never the product. Product appears in context or not at all.

Existence check

Before drafting, verify three things:

  1. The insight — one sentence the reader did not already know.
  2. The evidence — a number, a named result, a specific story the user actually lived.
  3. The audience — a specific person or role, not "professionals."

If two of three are missing, do not draft. Say which are missing and ask for exactly those. A post with no insight and no evidence is engagement bait, and publishing it costs the user credibility.

Step 1 — Gather

Ask, in one message:

  1. What is the one insight or takeaway?
  2. Who is the target reader?
  3. Any hook or angle you want?
  4. Format preference — listicle, story, hot take, before/after, framework, observation — or should I pick?

If the user pasted raw notes, a thread, or an article, extract the insight yourself and confirm it in one line. Never ask the user to organize their notes first.

Step 2 — Pick the format

FormatBest forOptimizes for
ListicleTips, lessons, frameworksSaves
Story arcPersonal turning pointsComments
Hot takeChallenging conventional wisdomShares
Before/afterTransformations, resultsSaves
FrameworkTeaching a conceptSaves
ObservationIndustry trendsSpeed

Output template

Produce exactly this, in this order. No preamble, no "here's your post!"

[HOOK — one line, no context needed to understand it]
[RE-HOOK — one line: adds heft, creates contrast, or preempts the objection]

[BODY — 8–16 lines. Chosen format. 1-3 line paragraphs, alternating single
lines with short clusters. At least one signpost line showing how the author
knows this. Specific numbers throughout.]

[CLOSER — the reusable line. The part someone screenshots.]

[CTA — one question, low friction, easy to answer. "P.S." form works well.]

Then, below the post, output:

  • Character count: [number]
  • Format used: [name]
  • Hook alternatives: two more one-line hooks the user can swap in.

Example

Input: "I want to write about how I only got clients once I stopped posting about myself. Got my first 10 clients in 2024 with under 1,000 followers."

Output:

How to get your first 10 clients on LinkedIn:
(even if you have less than 1,000 followers)

Most people overcomplicate this.

They build funnels, run ads, and buy courses.

But the people I've watched go from 0 to 6 figures did 4 things:

1. Picked ONE problem they solve
→ Not 5. Not "I help businesses grow." One specific pain.

2. Posted 3x/week about that problem
→ Not about themselves. About the reader's pain.

3. Commented on 20 posts a day from their ideal clients
→ Not "Great post!" — they added a missing insight or tip #8.

4. Ended every conversation with "How can I help?"
→ Not "Buy my thing." Just helped. For free. Consistently.

That's it. No funnel. No ads. No viral post needed.

The boring stuff works. Most people just won't do it long enough.

P.S. What's the one thing that got YOU your first client?

Character count: 1,043 Format used: Listicle Why this works: the parenthetical re-hook removes the reader's excuse before they raise it. Each point carries a DO and a DON'T, which forces specificity. The P.S. is low friction.

Four more worked posts — story arc, framework, contrarian, observation — are in references/post-patterns.md. Read them before choosing a format.

Show full SKILL.md (313 more words)Show less

Shortcuts Claude takes

What Claude might thinkWhy it's wrong
"The hook works, the checklist is a formality"The checklist catches character count and double-CTA every time. Run it.
"Two lines make a stronger hook"Two-line hooks measurably lose reach. Cut to one.
"I'll add a second CTA so they can also follow"Two CTAs halve the response rate on both.
"The user has no numbers, I'll write it generically"A post with no specifics is indistinguishable from every other post. Ask for the number.
"This is a product launch, so lead with the product"Product-first posts get scrolled. Insight first, always.
"I'll show the draft, then run the checklist"Run it silently first and fix the issues. Show only the clean version.

Exit checklist

Run this silently. Fix every failure, then present the clean draft. Not complete until every box is checked. Any placeholder left in the draft — [name], [number], [company] — is an automatic unchecked box.

  • Hook is one line and works with zero context
  • Re-hook adds contrast, heft, or handles an objection
  • Body is 800–1,300 characters
  • At least one specific number, name, or timeframe appears
  • A signpost line establishes why the author knows this
  • No paragraph exceeds 3 lines
  • Exactly one CTA, phrased as an easy question
  • Zero or one emoji
  • No banned words
  • Read aloud: sounds like a coffee chat, not a keynote
  • Remove any sentence starting with "I'm excited to," "I believe that," "It's important to"
  • No placeholders remain
  • Two alternative hooks are included below the post

Next

  • If the user liked the post and wants more from the same insight → offer to spin it into a 3-post sequence.
  • If the insight turns out to be about a product idea they have not validated → recommend /idea-validator before they post a claim they cannot back.
  • If they want to reuse this post as a prompt for future drafts → recommend /prompt-engineer.

© aakashg, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/linkedin-post-writer of aakashg/pm-claude-skills.

  • SKILL.md
  • references/post-patterns.md

Open the folder on GitHubat commit 64deebf

Compare with similar skills

Linkedin Post Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Linkedin Post Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Linkedin Post Writer this skillaakashg/pm-claude-skills112—~1.8kAutomated safety check: PassMIT
Socialcoreyhaines31/marketingskills54k4 repos~4.5kAutomated safety check: PassMIT
Social Contentfreekmurze/dotfiles1k23 repos~2.1kAutomated safety check: PassNone
Linkedin Marketingsergebulaev/linkedin-skills4.4k1 repos~3.2kAutomated safety check: NotesMIT
Linkedin Content Plannersergebulaev/linkedin-skills4.4k1 repos~2.1kAutomated safety check: PassMIT
Typefullyfreekmurze/dotfiles1k1 repos~3.4kAutomated safety check: NotesNone

Similar skills

  • Social

    coreyhaines31/marketingskills

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.

    54k GitHub starsUsed in 4 repos~4.5k tokens
    Writing & ContentAuto-check passed

  • Social Content

    freekmurze/dotfiles

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms.

    1k GitHub starsUsed in 23 repos~2.1k tokens
    Writing & ContentAuto-check passed

  • Linkedin Marketing

    sergebulaev/linkedin-skills

    Plan, draft, audit, and publish LinkedIn posts and comments.

    4.4k GitHub starsUsed in 1 repo~3.2k tokens
    Writing & ContentAuto-check: notes

  • Linkedin Content Planner

    sergebulaev/linkedin-skills

    Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.

    4.4k GitHub starsUsed in 1 repo~2.1k tokens
    Writing & ContentAuto-check passed

  • Typefully

    freekmurze/dotfiles

    Create, schedule, and manage social media posts via Typefully.

    1k GitHub starsUsed in 1 repo~3.4k tokens
    Writing & ContentAuto-check: notes

  • Changelog Social Recap

    FlorianBruniaux/claude-code-ultimate-guide

    Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.

    6.1k GitHub stars~1.8k tokensUpdated 2 days ago
    Writing & ContentAuto-check: notes

More from aakashg/pm-claude-skills

  • Idea Validator

    aakashg/pm-claude-skills

    A skill your agent uses 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.

    112 GitHub stars~2.3k tokensUpdated 2 mo ago
    Auto-check passed

  • Product Designer

    aakashg/pm-claude-skills

    A skill your agent uses 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.

    112 GitHub stars~2.4k tokensUpdated 2 mo ago
    Auto-check passed

  • Prompt Engineer

    aakashg/pm-claude-skills

    A skill your agent uses when the user asks to improve, optimize, rewrite, debug, or shorten a prompt, or asks why a prompt is producing bad output.

    112 GitHub stars~2.2k tokensUpdated 2 mo ago
    Auto-check passed

  • Status Update Writer

    aakashg/pm-claude-skills

    A skill your agent uses when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR.

    112 GitHub stars~2.5k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Categories

Questions about Linkedin Post Writer

What does Linkedin Post Writer do?

A skill your agent uses 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. Linkedin Post Writer is an agent skill from aakashg/pm-claude-skills. 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.

When should I use Linkedin Post Writer?

Linkedin Post Writer fits situations like: the user asks to write; rewrite a LinkedIn post; an article into a LinkedIn post; fix a hook that is not landing.

How do I install Linkedin Post Writer in Claude Code?

Run `npx skills add aakashg/pm-claude-skills --skill linkedin-post-writer -a claude-code`. Or copy the skill folder (skills/linkedin-post-writer in aakashg/pm-claude-skills) into .claude/skills/linkedin-post-writer in your project. Claude Code loads it when a task matches its description.

How do I install Linkedin Post Writer in Codex?

Run `npx skills add aakashg/pm-claude-skills --skill linkedin-post-writer -a codex`. Or copy the skill folder (skills/linkedin-post-writer in aakashg/pm-claude-skills) into .agents/skills/linkedin-post-writer in your project. Codex loads it when a task matches its description.

Can I use Linkedin Post Writer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aakashg/pm-claude-skills --skill linkedin-post-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linkedin-post-writer, .gemini/skills/linkedin-post-writer, .github/skills/linkedin-post-writer and .opencode/skills/linkedin-post-writer in your project.

What does Linkedin Post Writer need to run?

SKILL.md names no scripts, command-line tools or credentials: Linkedin Post Writer is instructions for the agent only.

Does Linkedin Post Writer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Linkedin Post Writer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Linkedin Post Writer use?

Linkedin Post Writer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Linkedin Post Writer use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Linkedin Post Writer?

Skills that share tags, products or a category with Linkedin Post Writer: Social (coreyhaines31/marketingskills, 54k stars), Social Content (freekmurze/dotfiles, 1k stars), Linkedin Marketing (sergebulaev/linkedin-skills, 4.4k stars) and Linkedin Content Planner (sergebulaev/linkedin-skills, 4.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linkedin Post Writer?

aakashg (a GitHub user) maintains it in aakashg/pm-claude-skills, which has 112 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on August 8, 2026.

Source: aakashg/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.