agentleFS
07001ec010shnk-svg07001ec010shnk-svg/linkedin-agent-skills/skills/linkedin-employee-advocacy/SKILL.md

linkedin-employee-advocacy

Skill0 starsChanged 32 days agoMITView on GitHub

Designs, launches, and governs a high-ROI company-wide employee LinkedIn advocacy program with a 14-day rollout roadmap, compliance guardrails, and attribution tracking.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Day 12: CRM Attribution Setup: Add referral UTM tags and CRM lead source dropdowns for employee-sourced deals.

    line 62
  2. Distinctive:

    Never share unreleased roadmap code, customer NDA data, unredacted financial metrics, or internal salary numbers.

    line 73
  3. Distinctive:

    Always supply fill-in-the-blank prompt angles, never copy-paste blocks.

    line 78
  4. Very specific:

    When executing linkedin-employee-advocacy, follow these operational stages:

    line 125

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

LinkedIn Employee Advocacy (linkedin-employee-advocacy)

The linkedin-employee-advocacy skill empowers companies to mobilize their internal team into an organic distribution powerhouse on LinkedIn. Built on the reality that employee profiles generate 8x to 10x higher organic reach and 3x higher click-through rates than corporate company pages, this skill provides a structured 14-day launch plan, role-based posting playbooks, brand governance rules, and executive ROI attribution models.


When to use this skill

Ideal Use Cases:

  • Rolling out an advocacy program for a startup or scaleup team (10 to 250 employees).
  • Enabling engineering, sales, customer success, and product teams to post without fear of violating compliance.
  • Replacing sterile corporate announcements with authentic employee-led storytelling.
  • Measuring company-wide organic reach, talent recruiting pipeline, and inbound demo attribution.
  • Training non-marketing team members on how to express domain expertise publicly.

Disambiguation ('Not for X, use Y'):

  • Not for rewriting a single executive profile -> use linkedin-profile-optimizer.
  • Not for writing a single founder post -> use linkedin-post-writer.
  • Not for managing inbound replies on an individual post -> use linkedin-reply-handler.
  • Not for building a personal 7-day calendar -> use linkedin-content-planner.
  • Not for conducting founder storytelling interviews -> use linkedin-interviewer.

Why Employee Advocacy Fails (And How to Fix It)

Most corporate advocacy initiatives collapse within 30 days due to 3 fatal errors:

  1. The Copy-Paste Trap: Marketing sends a company press release and tells everyone to share the exact same text. LinkedIn’s duplicate-content filter throttles it, and employees feel like corporate spambots.
    • The Solution: Provide fill-in-the-blank narrative angles; never provide pre-written copy-paste text.
  2. The "What’s in It for Me?" Vacuum: Employees assume advocacy is uncompensated marketing labor.
    • The Solution: Position advocacy as personal career capital. A strong personal brand makes engineers, product managers, and sales reps more valuable in the industry.
  3. The Compliance Paralysis: Employees are terrified of leaking trade secrets or saying something wrong.
    • The Solution: Provide a crystal-clear, 1-page green-light / red-light policy.

The 14-Day Advocacy Launch Roadmap

Phase 1: Foundations & Profile Alignment (Days 1–3)

  • Day 1: Kickoff Workshop (45 Mins): Explain "What’s in it for the employee" (career capital, personal brand, industry recognition).
  • Day 2: Profile Makeover Sprint: Distribute company banner assets and optimized headline templates using linkedin-profile-optimizer.
  • Day 3: Policy & Comfort Guardrails: Deliver the 1-page "No-Fear Social Media Policy" detailing what is encouraged vs what is confidential.

Phase 2: Role-Based Content Prompting (Days 4–7)

  • Day 4: Engineering Prompts: Distribute frameworks for "Lessons learned from our last sprint / bug post-mortem."
  • Day 5: Product & Design Prompts: Distribute frameworks for "Why we designed Feature X this way / User feedback revelation."
  • Day 6: Sales & CS Prompts: Distribute frameworks for "The most common question buyers ask us / Customer turnaround story."
  • Day 7: The First Pilot Cohort: Launch the first 5 pilot posts across volunteers in different departments.

Phase 3: The Internal Engagement Rhythm (Days 8–10)

  • Day 8: Setting Up #linkedin-crew Slack Channel: Automatic alerts when a teammate posts so colleagues can leave authentic comments in the first 60 minutes.
  • Day 9: Commenting Training: Teach team members the 3 comment frameworks (Additive, Contrarian, Question-forward) to replace generic "Congrats!" comments.
  • Day 10: Weekly Office Hours (20 Mins): Review top-performing posts, discuss friction, and rewrite drafted hooks live.

Phase 4: Gamification & Executive Attribution (Days 11–14)

  • Day 11: Leaderboard Launch: Track engagement points (not just vanity shares) with recognition and monthly rewards.
  • Day 12: CRM Attribution Setup: Add referral UTM tags and CRM lead source dropdowns for employee-sourced deals.
  • Day 13: Talent Pipeline Integration: Tag open job requisitions inside high-performing employee technical breakdowns.
  • Day 14: Program Review & Scale: Present 14-day aggregate reach to executive leadership and expand to the entire company.

Brand Governance & Safety Guardrails

To prevent corporate PR nightmares while giving employees genuine creative autonomy, enforce these 4 governance rules:

  1. The Confidentiality Redline:
    • Never share unreleased roadmap code, customer NDA data, unredacted financial metrics, or internal salary numbers.
    • Screenshots of internal dashboards must blur customer identifiers and private API keys.
  2. The "No Copy-Paste" Mandate:
    • Strictly prohibit employees from copy-pasting identical marketing copy. LinkedIn’s duplicate-content filter demotes identical posts, and readers recognize corporate astro-turfing instantly.
    • Always supply fill-in-the-blank prompt angles, never copy-paste blocks.
  3. External Link Discipline:
    • Posts never include raw marketing links in the post body. Employees instruct readers: "Link to our open-source repo in the first comment."
  4. Constructive Tone:
    • Critiquing industry technology or methodologies is welcomed; disparaging competitors by name or engaging in toxic social drama is forbidden.

Role-Based Content Prompt Bank

Equip different departments with native narrative angles:

For Software Engineers:

  • The hardest bug our team hunted down this week (and the 2 lines of code that fixed it).
  • What our architecture looked like at 1,000 users vs 100,000 users.
  • An open-source tool that made our development workflow 2x faster.

For Product Managers & Designers:

  • A feature our customers begged for that we intentionally refused to build (and why).
  • How we reduced user onboarding friction from 6 steps to 2 steps.
  • The UX teardown of a workflow we redesigned after watching 20 user session recordings.

For Customer Success & Solutions Engineers:

  • The exact operational problem an enterprise buyer was trying to solve when they onboarded.
  • 3 misconceptions buyers have about implementing our category of software.
  • How a client turned an imminent project delay into an early go-live milestone.

Measuring ROI: Earned Media Value & Pipeline Attribution

Track performance across three executive KPIs:

  1. Earned Media Value (EMV):
    EMV = (Total Employee Impressions / 1,000) * Benchmark LinkedIn Sponsored CPM ($35)
  2. Inbound Pipeline Influenced:
    • Track inbound demo form submissions containing: "Discovered via [Employee Name]'s LinkedIn post".
  3. Talent Recruiting Savings:
    • Direct engineering hires sourced via employee technical posts (saving $20k–$35k in recruiter agency fees per hire).

How It Works Step-by-Step

When executing linkedin-employee-advocacy, follow these operational stages:

  1. Company Scope & Culture Assessment:
    • Ingest company size, key departments, current executive social presence, and compliance sensitivities.
  2. Program Architecture Customization:
    • Tailor the 14-day schedule and role-based prompt banks to the company's specific vertical.
  3. Governance & Guidelines Generation:
    • Produce a 1-page plain-English social media policy with explicit green-light and red-light examples.
  4. Internal Slack & Attribution Setup:
    • Define the Slack #advocacy bot workflow and CRM attribution tracking taxonomy (UTM parameters).
  5. Approval Staging & Rollout:
    • Present the comprehensive program documentation for executive sign-off.

Approval Gate

Deploying company-wide advocacy playbooks requires explicit executive authorization:

[EMPLOYEE ADVOCACY PROGRAM STAGED]
Company: DevScale Technologies (42 employees)
Launch Scope: 14-Day Pilot (Engineering & Sales Cohort: 8 participants)

Deliverables Generated:
1. 14-Day Step-by-Step Program Launch Roadmap
2. 1-Page Plain-English Brand Governance Policy
3. Department Prompt Banks (Engineering, Product, Customer Success)
4. Slack Engagement Channel Blueprint & Leaderboard Rules
5. CRM UTM Attribution Schema

Approval Token: 9811ab22-44cc-40aa-b123-556677889900
Status: PENDING EXECUTIVE SIGN-OFF.
Command: Approve token to finalize program launch assets.

Examples

Example 1: 1-Page Plain-English Social Media Policy

### DevScale Social Media Guidelines: Speak Your Mind, Protect the Fortress

**Our Philosophy:** We want you to build a massive personal reputation in tech. When you grow, DevScale grows.

#### The Green Light (Do This Often):
- Share your technical breakthroughs, architecture lessons, and debugging stories.
- Talk about the cultural norms and workflows that make our engineering team fast.
- Share credit with teammates who unblocked you.
- Disagree respectfully with industry conventional wisdom.

#### The Red Light (Strictly Off-Limits):
- Never share client company names without written marketing approval.
- Never screenshot dashboards showing customer email addresses, API tokens, or server IPs.
- Never share confidential revenue, churn, or fundraising numbers before public press release.
- Never disparage a competitor or customer personally.

**Questions?** Drop a draft in `#linkedin-crew` on Slack for quick friendly peer feedback!

Example 2: Engineering Advocacy Post (Prompt Output)

Employee: Alex Miller (Senior Infrastructure Engineer) Prompt Used: "The hardest bug we fixed this week"

Our staging Kubernetes cluster began throwing random 504 gateway timeouts at 3 PM on Tuesday.
No code had been deployed for 6 hours.
CPU was under 15%. Memory was clean.

It took 3 engineers 4 hours to find the culprit:
A subtle DNS connection limit inside our CoreDNS daemon that quietly starved outgoing database connections once our pod count passed 120.

The fix was a 2-line config change in our CoreDNS upstream forwarder:
`max_concurrent 1000`

Two lessons our team took away:
1. Never assume network infrastructure scales automatically just because your cloud provider manages the master node.
2. High-latency 504s are almost always DNS lookups in disguise.

What’s the strangest infrastructure ghost your team hunted down this quarter?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.