sergebulaev/linkedin-skills / .codex-marketplace/linkedin-skills/skills/linkedin-employee-advocacy
linkedin-employee-advocacy
VerifiedStand 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).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.1 KB |
| references/advocacy-principles.md | markdown | 3.4 KB |
| references/governance-playbook.md | markdown | 5.4 KB |
| references/team-cadence-matrix.md | markdown | 3.7 KB |
references/team-cadence-matrix.md
View on GitHub# Team Cadence Matrix — Realistic posting & comment volume by role and seniority
Use this matrix to set per-person targets that survive contact with calendars. The numbers below assume a 40-hour week; halve them for part-time. All cadences are **per-week** unless stated otherwise.
## Why role + seniority
A founder posting 5x/week is signaling "this is my channel." A senior IC posting 5x/week is leaking attention away from delivery work. Cadence has to be set so each person has a sustainable surplus, not a debt.
## The matrix
| Role | Seniority | Posts/wk | Comments/wk | Reposts /wk | Time budget /wk |
|---|---|---|---|---|---|
| Founder / CEO | n/a | 3-5 | 30-60 | 2-3 | 3-5 hr |
| CMO / VP Marketing | senior | 2-3 | 20-40 | 1-2 | 2-3 hr |
| Director (Marketing / Sales / Product) | senior | 1-2 | 15-25 | 1-2 | 1.5-2 hr |
| IC Marketing (content / brand) | senior | 2-3 | 15-30 | 1-2 | 2-3 hr |
| IC Marketing | mid | 1-2 | 10-20 | 1 | 1-2 hr |
| IC Marketing | junior | 1 | 5-15 | 1 | 1 hr |
| IC Sales (AE / SDR) | senior | 1-2 | 25-50 | 1 | 1.5-2 hr |
| IC Sales | mid | 1 | 15-30 | 1 | 1 hr |
| IC Sales | junior | 0-1 | 10-20 | 0-1 | 0.5-1 hr |
| IC Product / Engineering | senior | 1 | 5-10 | 1 | 1 hr |
| IC Product / Engineering | mid | 0-1 | 3-8 | 0-1 | 0.5 hr |
| IC Customer Success | senior | 1 | 10-20 | 1 | 1 hr |
| IC Customer Success | mid | 0-1 | 5-15 | 0-1 | 0.5-1 hr |
## Reading the table
- **Posts/wk** is original content (text, carousel, poll, video). Reposts and "thoughts on this" reshares don't count.
- **Comments/wk** is substantive comments on posts by people outside the team — peer founders, prospects, aspirational creators. Internal team comments don't count.
- **Reposts/wk** is amplification of a teammate's post (with a 1-2 sentence personal angle, not bare reshare).
- **Time budget** assumes the program supplies prompts, voice-capture, and humanizer-passed drafts. Without that scaffolding, double the budget.
## Floor and ceiling rules
- **Floor:** any seat below 1 post/week + 5 comments/week is not "on the program" and doesn't count toward team reach. Either skip them or pair them with someone who is.
- **Ceiling:** no IC should be at 5+ posts/week. That's a content-creator role, not an advocate role. If they want that, change their job title.
- **Founders are the only seat where the ceiling can stretch** to 5 posts/week, because LinkedIn's algorithm rewards founder voice ~6x company-page reach.
## Cadence ramp-up (first 60 days)
Don't start any seat at the steady-state target. Ramp:
| Week | All seats post at | All seats comment at |
|---|---|---|
| 1-2 | 0 | 5/wk (just engage) |
| 3-4 | 1/wk (a single low-stakes "intro" post) | 8-10/wk |
| 5-8 | 50% of steady-state target | 75% of steady-state target |
| 9+ | Steady-state | Steady-state |
Rationale: voice calibration takes 2-3 weeks. Posting at full cadence before voice is calibrated creates a cleanup tax later.
## When to adjust
Down-shift when:
- Engagement rate (reactions+comments / impressions) drops below 2% for 3 consecutive weeks
- Author replies to their own thread within 60 minutes drops below 60%
- Seat is consistently missing >25% of weekly target
Up-shift when:
- Author-reply-to-comment ratio is above 30% (high audience interest)
- Profile views are growing >10% week-over-week
- Inbound DMs from posts cross 2/week
## Out-of-band events
- **Conference / event week:** suspend cadence for the team going. Replace with shared event recap on the team's slowest day the following week.
- **Crisis week** (PR issue, outage): only the designated incident comm voice posts. Everyone else is in comment mode for 5-7 days.
- **Hiring sprint:** Talent Acquisition can spike to 4-5 posts/week temporarily. Other seats stay at baseline.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |