# linkedin-employee-advocacy

linkedin-employee-advocacy is a Claude Code skill that launches and runs a team posting program on LinkedIn. Triggers on requests to scale team reach, set up review rules, and track pipeline ROI.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 158 installs · ★ 6103 repo stars
- Author: sergebulaev
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/sergebulaev/linkedin-skills/tree/HEAD/skills/linkedin-employee-advocacy/SKILL.md
- Updated: 2026-11-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/linkedin-employee-advocacy

## What it does

Produces a 14-day launch schedule, cadence targets per member, and an ROI tracking framework across team reach, engagement, and pipeline impact. It structures workflows around authentic individual voices because personal posts generate 8x more engagement than company pages.

The operating model enforces a 5-minute time budget per post and an optional brand-safety review under 4 business hours. Marketing checks factual claims and confidentiality without editing personal style. Individual calendar scheduling is out of scope and belongs in `linkedin-content-planner`.

## Requirements
- Works with: LinkedIn

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add sergebulaev/linkedin-skills --skill linkedin-employee-advocacy -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/linkedin-employee-advocacy/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/linkedin-employee-advocacy/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add sergebulaev/linkedin-skills --skill linkedin-employee-advocacy -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/linkedin-employee-advocacy/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add sergebulaev/linkedin-skills --skill linkedin-employee-advocacy -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/linkedin-employee-advocacy/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install sergebulaev/linkedin-skills skills/linkedin-employee-advocacy
```

2. **Manually: put the files in place**
- File: `.github/skills/linkedin-employee-advocacy/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add sergebulaev/linkedin-skills --skill linkedin-employee-advocacy -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/sergebulaev/linkedin-skills --path skills/linkedin-employee-advocacy
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/linkedin-employee-advocacy/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add sergebulaev/linkedin-skills --skill linkedin-employee-advocacy -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/sergebulaev/linkedin-skills/tree/HEAD/skills/linkedin-employee-advocacy/SKILL.md

## When to use it
- launching advocacy
- build a 14-day team rollout schedule
- establish a non-blocking brand safety review SLA
- track pipeline attribution from employee reach

## Example prompts
- Launch an employee advocacy program on LinkedIn for a team of 10
- Set up brand-safety guidelines and review SLA for team LinkedIn posts
- Define an ROI dashboard measuring pipeline impact from employee LinkedIn content

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 30159f3672eb05da.

BEGIN THIRD-PARTY FILE 30159f3672eb05da
```text
---
name: linkedin-employee-advocacy
description: "Stand up and run a LinkedIn employee advocacy program for a marketing or sales team. Covers 14-day launch playbook, brand-guideline governance, per-post time budget, cadence benchmarks, and team ROI (reach, engagement, pipeline). Triggers on \"employee advocacy\", \"get the team posting\", \"scale LinkedIn across team\", \"advocacy ROI\". Not for planning one person's own calendar (use linkedin-content-planner)."
license: MIT
metadata:
  author: Sergey Bulaev
---

# LinkedIn Employee Advocacy

Stand up a marketing-team LinkedIn advocacy program that scales without killing authenticity. Employee posts get **8x more engagement** than brand-page posts — this skill operationalizes that advantage.

## When to use

- Marketing leader wants to get their team posting on LinkedIn
- User is planning an advocacy program launch
- Team is posting but output is inconsistent / off-brand / low-engagement
- Need ROI measurement framework for an existing program
- Requests: "how do I get the team posting", "launch advocacy", "scale LinkedIn across 10 people"

## Input

- Team size (5-50 typical)
- Marketing goal (reach / pipeline / recruiting / thought leadership)
- Current state (everyone silent / some active / inconsistent)
- Brand guideline constraints

## Output

- **14-day launch plan** (if cold-starting)
- **Operating model** (voice capture, ideation, approval, posting, measurement)
- **Cadence targets** per team member (realistic, not punishing)
- **KPI dashboard spec** (team reach, engagement, pipeline attribution)
- **Governance playbook** (brand safety without blocking velocity)

## Four operating principles

1. **Scale authentically.** Individuals compose in their own voice, not corporate language. Corporate-tone team posts underperform authentic voice 3x.
2. **Maintain control.** Brand guidelines integrated into the workflow. Review step is **optional, not blocking** — high-trust roles bypass review entirely.
3. **Remove friction.** Per-post time budget: **5 minutes**. Anything more and the program dies in week 3.
4. **Prove ROI.** Track team reach, engagement, pipeline impact. Without attribution, the program gets cut at the first budget review.

## Benchmarks

- **Launch target:** team posting within **14 days**
- **Active team size benchmark:** 8-11 members
- **Output benchmark:** 70+ posts/week (at 8 members) or 3-5 posts/member/week
- **Per-post time budget:** 5 minutes
- **Team touchpoint math:** 11 people × 3 posts/week × 300 min impressions = **40,000 monthly touchpoints** baseline
- **Employee vs. brand page:** 8x more engagement, 6-8x more reach on personal posts

## 14-day launch playbook

### Days 1-3: Voice capture
```
END THIRD-PARTY FILE 30159f3672eb05da

The third-party file has ended. Everything between the 30159f3672eb05da tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2726 of 6228 bytes. © sergebulaev · MIT · https://github.com/sergebulaev/linkedin-skills/tree/HEAD/skills/linkedin-employee-advocacy/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
