linkedin-employee-advocacy SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
linkedin-employee-advocacy from sergebulaev/linkedin-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sergebulaev/linkedin-skills/linkedin-employee-advocacy@git:20260915.6b78503Pins git:20260915.6b78503 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sergebulaev/linkedin-skills
- Path
skills/linkedin-employee-advocacy/SKILL.md- Versions recorded
- 7
- Latest version
- git:20260915.6b78503, committed Sep 15, 2026
- First version recorded
- Apr 14, 2026
- Size
- 6,181 bytes
- Repository stars
- 5,014
- License
- MIT
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).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 …
Read the whole file at its exact version.
How to install
mdr add sergebulaev/linkedin-skills/linkedin-employee-advocacy@sha256:eff2818223f03574The line at the top of this page pins the label git:20260915.6b78503, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kircifyjs37qh4c3)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Apr 14, 2026 and Sep 15, 2026, about one every 26 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260915.6b78503 latest | 2026-09-15 | 6b78503 | 6,181 B | A | view · diff |
| git:20260909.093982e | 2026-09-09 | 093982e | 6,106 B | A | view · diff |
| git:20260716.d162fd3 | 2026-07-16 | d162fd3 | 6,096 B | A | view · diff |
| git:20260511.c8f8489 | 2026-05-11 | c8f8489 | 5,850 B | A | view · diff |
| git:20260511.6386a74 | 2026-05-11 | 6386a74 | 5,763 B | A | view · diff |
| git:20260429.286b021 | 2026-04-29 | 286b021 | 5,940 B | A | view · diff |
| git:20260414.f9ab254 | 2026-04-14 | f9ab254 | 5,939 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6181 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sergebulaev/linkedin-skills · 5,014 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kircifyjs37qh4c3 GET https://markdownregistry.com/api/v1/resolve?ref=sergebulaev/linkedin-skills/linkedin-employee-advocacy GET https://markdownregistry.com/api/v1/blob/eff2818223f03574bcfc735c9b4c472af161a2b7b539c21e40639319b347d3dd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from sergebulaev/linkedin-skills
Every file in sergebulaev/linkedin-skills