linkedin-employee-advocacy
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).
Install / Use
npx skills add sergebulaev/linkedin-skills --skill linkedin-employee-advocacyInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of linkedin-employee-advocacy
linkedin-employee-advocacy scores 87/100 on our quality scale, 1649th of 2,780 Automation skills we index.
Its SKILL.md is 6.0 KB long, well organised into 19 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 5,507 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 20 days ago, so linkedin-employee-advocacy is actively maintained.
- Our last check on 2026-11-01 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
linkedin-employee-advocacy compared with similar skills
All 4 of these similar skills score higher than linkedin-employee-advocacy; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| linkedin-employee-advocacy (this skill)by sergebulaev | 87 | 5.5k | 20d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install linkedin-employee-advocacy?
- Run
npx skills add sergebulaev/linkedin-skills --skill linkedin-employee-advocacy. The install tabs above show the steps for each supported agent. - Which AI agents does linkedin-employee-advocacy work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is linkedin-employee-advocacy safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is linkedin-employee-advocacy still maintained?
- The repository was last updated 20 days ago, so linkedin-employee-advocacy is actively maintained.
Skill content
View source on GitHubname: 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)."
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
- Scale authentically. Individuals compose in their own voice, not corporate language. Corporate-tone team posts underperform authentic voice 3x.
- Maintain control. Brand guidelines integrated into the workflow. Review step is optional, not blocking — high-trust roles bypass review entirely.
- Remove friction. Per-post time budget: 5 minutes. Anything more and the program dies in week 3.
- 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
- Short interview with each team member (5-10 min) to extract their actual voice
- Identify their domain expertise and 2-3 content pillars
- Set realistic individual cadence (some commit to 1/week, some 3/week — don't force uniformity)
Days 4-7: First posts
- Everyone ships their first post, drafted in their voice
- Marketing reviews only for brand safety (never for style)
- Celebrate every first post internally — social proof unlocks the next team member
Days 8-10: Ideation pipeline
- Set up a shared ideation source (newsletter digest, trending-topics feed, internal wins)
- Each team member gets 5-10 topic suggestions per week
- They pick, not assigned
Days 11-14: Rhythm lock
- Establish cadence: each team member publishes on fixed days/times
- Set up KPI dashboard (see below)
- Run first weekly review
Governance: brand-safe without being blocked
What marketing reviews:
- Factual claims about the company / products / customers
- Confidential info
- Legal/compliance issues (finance, health, regulated industries)
What marketing does NOT review:
- Personal voice, tone, style
- Opinions the team member has about their own work
- Formatting, hashtags, emoji choices
- Topic selection (within pillars)
The review SLA: <4 business hours. Anything longer and the post is dead (posts go stale in the news cycle).
ROI measurement
Per-person metrics (content quality)
- Impressions per post
- Engagement rate (reactions + comments + shares / impressions)
- Comments (depth signal)
- Profile views attributed to post
Team-level metrics (program health)
- Total team reach
- Total team engagement
- Individual contribution rank (leaderboard)
- Active members / total members (participation rate)
Business metrics (pipeline impact)
- Inbound DMs sourced from LinkedIn content
- Meetings booked from LinkedIn
- Closed-won deals with LinkedIn as first-touch channel
- Employee referrals sourced from LinkedIn (if recruiting is a goal)
Anti-patterns
- Copy-paste corporate posts across team accounts — LinkedIn detects this, suppresses all of them
- Ghostwriting that erases the writer's voice — reads as fake
- Mandatory posting cadence without individual calibration — program dies in 6 weeks
- Approval loops >24h — makes the program feel like work
- Measuring only vanity metrics — program gets cut without pipeline attribution
- All-same pillars across team — redundancy kills team reach (360Brew penalizes clustering)
Resources
references/advocacy-principles.md— the 4 operating principles with examplesreferences/team-cadence-matrix.md— realistic cadence by role + seniorityreferences/governance-playbook.md— what to review, what not to, SLA
Related skills
linkedin-post-writer— each team member uses this for individual draftslinkedin-profile-optimizer— team profiles should match before the program launches (otherwise profile clicks convert poorly)linkedin-content-planner— each team member gets their own pillar mixlinkedin-thread-monitor— track which team members' comments drive author replieslinkedin-engager-analytics— see who's engaging with each team member's postslinkedin-comment-drafter— its reshare mode is how team members amplify a brand or colleague post to their own feed with a short take (lib.repost(post_url, commentary)on approval); the cleanest advocacy action after an original post
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
