Skip to content

sergebulaev/linkedin-skills / .codex-marketplace/linkedin-skills/skills/linkedin-employee-advocacy

linkedin-employee-advocacy

Verified

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

references/advocacy-principles.md

View on GitHub
# Employee Advocacy — Four Operating Principles

Source: https://co.actor/use-cases/marketing-teams + 2026 practitioner research

## 1. Scale authentically

Individuals compose in **their own voice**, not corporate language.

- Team-written copy that sounds like the brand = 3x lower engagement than personal voice
- Use a short voice-capture interview at onboarding (5-10 min) to document each person's tone
- Don't normalize — keep the variance. The person who curses occasionally stays that way. The one who writes in technical prose stays that way.

**Litmus test:** if someone reads 5 random posts from your team and can tell which person wrote each one, you're doing it right.

## 2. Maintain control

Brand guidelines integrated into the workflow. Review step is **optional, not blocking**.

- High-trust roles (VPs, Directors) bypass review entirely
- Mid-trust roles (Managers, ICs) route to a 4-hour review window
- New hires default to review, earn bypass after 4 weeks of clean posts

**What the review catches:**
- Factual errors about products / customers
- Confidential info leaks
- Regulatory issues (finance, health, disclosure rules)

**What the review does NOT change:**
- Voice, tone, formatting
- Opinions the team member has about their own work
- Topic selection (within pillars)
- Hashtags, emoji

## 3. Remove friction

Per-post time budget: **5 minutes**. Anything more and the program dies by week 3.

- AI does heavy lifting: ideation, drafts, visual suggestions
- Team member reviews, edits, approves, publishes
- Approval workflow is async and <4h SLA
- Mobile posting is a first-class path (not desktop-only)

**Math:** 5 min/post × 3 posts/week × 11 people = **2.75 hrs total team time per week** for full program output.

## 4. Prove ROI

Track team reach, engagement, and pipeline impact. Without attribution, the program gets cut at the first budget review.

### The 3 KPIs

- **Team reach** — sum of impressions across all creators
- **Team engagement** — comments + reactions + shares
- **Pipeline impact** — inbound DMs, meetings booked, closed-won deals with LinkedIn as first-touch

### What NOT to use as primary KPI

- Follower count (vanity, slow-moving)
- Post frequency (effort, not outcome)
- Hashtag performance (not a business metric)

## Benchmarks (2026)

- Launch → first team post: **14 days** target
- Active team size: **8-11** members for meaningful output
- Team output: **70+ posts/week** at 8 members (~10 per person per 4 weeks)
- Per-post time: **5 min** max
- Team touchpoints: **40,000/month** at 11 people × 3 posts/week
- Per-post impression floor: **300** (anything lower, audit profile/hook)
- Employee vs. brand page: **8x engagement**, **6-8x reach**

## Example team config

```yaml
team:
  VP Marketing (author: Alice):
    cadence: 2 posts/week
    review: bypass
    pillars: [thought leadership, contrarian takes]
  Senior PMM (author: Bob):
    cadence: 3 posts/week
    review: bypass
    pillars: [product positioning, competitive teardowns]
  Marketing Manager (author: Carol):
    cadence: 3 posts/week
    review: 4h SLA
    pillars: [campaign recaps, customer wins]
  Content Writer (author: Dan):
    cadence: 4 posts/week
    review: 4h SLA
    pillars: [industry analysis, frameworks]
  ... (5 more team members)

weekly_output: 23 posts total from 8 members
weekly_time_cost: 1.9 hours
target_team_reach: 15,000 impressions/week (growing toward 40,000/month)
```
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall