Agent skill · Content & Marketing

linkedin-post-generator

Converts any content, blog post URL, pasted article, GitHub PR description, or a description of something built, into a formatted LinkedIn post with proper hook, story arc, and formatting. Optionally posts directly to LinkedIn via Composio. Use when asked to write a LinkedIn post, turn a blog into a LinkedIn update, announce a shipped feature, share a case study on LinkedIn, or post something professionally. Trigger when a user mentions LinkedIn, wants to share content professionally, says "post this to LinkedIn", or asks to repurpose a blog/article/PR for social media.

Varnan-Techgithub.com/Varnan-TechGitHub ↗
claude-codecopilotMIT
Install
npx skills add Varnan-Tech/opendirectory --skill linkedin-post-generator --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 10 KB
Bundled scripts: none
Version: 1.0.0
Declared author: OpenDirectory
Requires: [claude-code, gemini-cli, github-copilot]
Path: skills/linkedin-post-generator/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 571
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# linkedin-post-generator You are a content strategist who specialises in technical and founder LinkedIn content. Your job is to convert raw input into a high-performing LinkedIn post that follows the platform's proven content patterns. DO NOT INVENT SPECIFICS. Metrics, numbers, company names, product names, and outcomes must come directly from the source material. Never fabricate results or claims. Before starting: Confirm you have input material. Accepted inputs: - A URL to a blog post or article - Pasted article, case study, or tutorial text - A GitHub PR URL or PR description - A description of what was built or shipped If no input was provided, ask: "What would you like to turn into a LinkedIn post? Give me a blog URL, paste article text, share a GitHub PR, or describe what you built." --- ## Writing Style Apply these rules to every post you generate. They override any default writing tendencies. Active voice only. No passive constructions. Short sentences. One idea per sentence. If a sentence needs two clauses to work, split it. No em dashes. Replace with a period or a comma. No semicolons. No hashtags. No markdown formatting. No bold, no italic, no asterisks. LinkedIn render

What's inside
Steps it walks through
  1. Writing Style
  2. Workflow
  3. Step 1: Detect Input Type and Fetch Content
  4. Step 2: Audience and Positioning
  5. Step 3: Choose Post Format
  6. Step 4: Select Hook Formula
  7. Step 5: Read Format Rules
  8. Step 6: Generate the Post
  9. Step 7: Self-QA
  10. Step 8: Post via Composio or Output to User
  11. What Good Output Looks Like
  12. What Bad Output Looks Like
Ships with 5 files
  • .env.example
  • README.md
  • evals/evals.json
  • references/linkedin-format.md
  • references/output-template.md
More from opendirectory
All skills →
About this skill
What does the linkedin-post-generator skill do?

Converts any content, blog post URL, pasted article, GitHub PR description, or a description of something built, into a formatted LinkedIn post with proper hook, story arc, and formatting. Optionally posts directly to LinkedIn via Composio. Use when asked to write a LinkedIn post, turn a blog into a LinkedIn update, announce a shipped feature, share a case study on LinkedIn, or post something professionally. Trigger when a user mentions LinkedIn, wants to share content professionally, says "post this to LinkedIn", or asks to repurpose a blog/article/PR for social media.

How do I install it?

Run `npx skills add Varnan-Tech/opendirectory --skill linkedin-post-generator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Varnan-Tech/opendirectory, a repository with 571 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going