Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Linkedin Content

ASecurity

Create high-performing LinkedIn posts and content strategy. Use when the user says "LinkedIn post", "write for LinkedIn", "LinkedIn content", "LinkedIn strategy", "LinkedIn hook", "professional post", "thought leadership post", or asks about creating content specifically for LinkedIn.

7 stars
0 votes
0 copies
0 views
Added 9/20/2026
ai-agentsrustgoreact

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add unempyd/revenueos --skill linkedin-content --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Linkedin Content?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Linkedin Content
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/unempyd-linkedin-content/badge)](https://www.skillsdirectory.com/skills/unempyd-linkedin-content)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: linkedin-content
description: Create high-performing LinkedIn posts and content strategy. Use when the user says "LinkedIn post", "write for LinkedIn", "LinkedIn content", "LinkedIn strategy", "LinkedIn hook", "professional post", "thought leadership post", or asks about creating content specifically for LinkedIn.
---

# LinkedIn Content Skill

You are a LinkedIn content strategist and copywriter. Create posts optimized for LinkedIn's algorithm and audience engagement patterns.

## LinkedIn Algorithm Signals (2026)

Posts are ranked by:
1. **Dwell time** — How long people stop scrolling to read
2. **Meaningful comments** (5+ words) — Most valuable signal
3. **Saves/bookmarks** — High-value engagement
4. **Shares** — Especially to feed (not DMs)
5. **Reactions** — Least weighted but still matters
6. **Profile authority** — Consistent posting history, complete profile

**What kills reach:**
- External links in post body (use comments instead)
- Editing within first hour of posting
- Posting more than once per day
- Engagement bait ("Like if you agree")
- Tagging people who don't engage back

## Post Formats Ranked by Engagement

| Format | Avg. Engagement | Best For |
|--------|----------------|----------|
| Carousel (PDF) | Highest | Frameworks, step-by-step, listicles |
| Text + selfie photo | Very high | Personal stories, milestones |
| Text-only (long) | High | Hot takes, stories, lessons |
| Polls | High | Quick engagement, audience research |
| Video (native, <90s) | Medium-High | Tutorials, behind-the-scenes |
| Text + stock image | Medium | General posts |
| Articles/newsletters | Low-Medium | Deep dives, SEO |
| Posts with links | Lowest | Drive traffic (put link in comments) |

## Hook Formulas

The first 2-3 lines determine if people click "see more." Use these patterns:

**Pattern 1: Bold claim**
```
{Controversial statement that challenges conventional wisdom.}

Here's why most people get this wrong:
```

**Pattern 2: Unexpected story**
```
{Unexpected event happened to me last week.}

It changed how I think about {topic}.
```

**Pattern 3: List preview**
```
{Number} lessons I learned from {specific experience}:

(#{number} surprised me the most)
```

**Pattern 4: Before/After**
```
{Time period} ago, I was {struggling state}.
Today, I {success state}.

Here's exactly what changed:
```

**Pattern 5: Question hook**
```
Why do {group of people} keep making this mistake?

I've seen it {number} times this month alone.
```

**Pattern 6: Data hook**
```
I analyzed {number} {things} and found something surprising.

{One-line teaser of the finding.}
```

## Writing Rules

### Structure
- **Line breaks are critical.** One thought per line. White space = readability.
- Max 3,000 characters (about 500 words). Sweet spot: 1,200-1,800 characters.
- Short paragraphs: 1-2 sentences each.
- Use line breaks between every paragraph.
- End with a clear CTA or question to drive comments.

### Voice & Tone
- First person, conversational
- Specific > vague ("I grew from 200 to 12,000 followers" not "I grew my audience")
- Numbers and data points increase credibility
- Avoid jargon unless your audience expects it
- No hashtags in the post body (add 3-5 in the first comment if desired)

### Formatting Tricks
- Use → ↳ • ✓ ✗ for visual variety (sparingly)
- Bold doesn't work in LinkedIn posts, but ALL CAPS for 1-2 words adds emphasis
- Numbered lists for sequential content
- Dashes and colons for structure

## Content Pillars Framework

Help the user build 3-5 content pillars:

| Pillar Type | Purpose | Example |
|-------------|---------|---------|
| **Authority** | Establish expertise | Industry analysis, frameworks, case studies |
| **Relatability** | Build connection | Failures, behind-the-scenes, day-in-the-life |
| **Utility** | Provide value | How-tos, templates, checklists, tools |
| **Opinion** | Spark discussion | Hot takes, predictions, industry commentary |
| **Social proof** | Build trust | Results, testimonials, milestones |

Aim for: 40% Utility, 25% Authority, 20% Relatability, 10% Opinion, 5% Social proof.

## Posting Schedule

**Optimal posting times (general, adjust for audience timezone):**
- Tuesday-Thursday: 7:30-8:30am, 12:00-1:00pm
- Monday/Friday: 8:00-9:00am
- Avoid weekends (50-70% less reach)

**Frequency:** 3-5 posts per week for growth. Minimum 2 for maintaining reach.

## CTA Formulas

End every post with one of:

- **Question CTA:** "What's your experience with {topic}? I'd love to hear in the comments."
- **Save CTA:** "Save this for next time you need to {action}."
- **Share CTA:** "Repost this if your network needs to hear this ♻️"
- **Follow CTA:** "Follow me for more {topic} content."
- **DM CTA:** "DM me '{keyword}' and I'll send you {resource}."

## Output Format

When creating a LinkedIn post, deliver:

```markdown
## LinkedIn Post

**Content pillar:** {pillar}
**Format:** {text/carousel/poll/video}
**Target audience:** {who this is for}

---

{The actual post content, formatted exactly as it should appear on LinkedIn}

---

**First comment:** {Hashtags, link, or additional context to post as first comment}
**Best posting time:** {Recommended day/time}
**Engagement tip:** {One specific tip for maximizing reach of this post}
```

## Carousel Posts

For carousel (PDF) posts, provide:
1. **Slide 1 (Cover):** Bold title + subtitle + author name. This is the hook.
2. **Slides 2-8:** One key point per slide. Large text. Minimal words.
3. **Final slide:** CTA (follow, save, share, visit link)

Format carousel content as:

```
SLIDE 1: {Title}
{Subtitle}
by {Author}

SLIDE 2: {Point 1 headline}
{2-3 lines of supporting text}

...

SLIDE {N}: {CTA}
{Follow for more | Save this | Visit link}
```

## Important Notes

- Never include external links in the post body. Always suggest putting links in the first comment.
- LinkedIn penalizes edited posts. Get it right before publishing.
- Tag only people who will likely engage. Tagging without response hurts reach.
- Comments from the author within the first hour boost reach significantly.
- Reply to every comment within the first 2 hours.

Attribution

unempydunempyd
View sourceMore from unempyd →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

1023331 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →