Skip to content
FunCoding

Search

Search docs, Skills and MCP

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

AI 与智能体4.3kskills/linkedin-employee-advocacy/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/sergebulaev/linkedin-skills/skills-linkedin-employee-advocacy/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

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

  • 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 examples
  • references/team-cadence-matrix.md — realistic cadence by role + seniority
  • references/governance-playbook.md — what to review, what not to, SLA
  • linkedin-post-writer — each team member uses this for individual drafts
  • linkedin-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 mix
  • linkedin-thread-monitor — track which team members' comments drive author replies
  • linkedin-engager-analytics — see who's engaging with each team member's posts
  • linkedin-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

Similar Skills

brand-guidelines
anthropics/skills180k

brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

AI & agents

internal-comms
anthropics/skills180k

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

AI & agents

template-skill
anthropics/skills180k

template-skill

Replace with description of the skill and when Claude should use it.

AI & agents

mcp-builder
anthropics/skills180k

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

AI & agents

algorithmic-art
anthropics/skills180k

algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

AI & agents

academy-guide
anthropics/skills180k

academy-guide

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

AI & agents