Skip to content

borghei/Claude-Skills / tools/linkedin/linkedin-employee-advocacy

linkedin-employee-advocacy

Verified

Designs and runs an employee advocacy programme: who posts what and how often, review rules, and what is never scripted. Use when getting a team posting, writing an advocacy policy, or fixing a programme that has stalled.

assets/advocacy_charter_template.md

View on GitHub
# Advocacy Programme Charter

Fill in every bracket. Share the finished charter with each person before they
decide whether to join. Have counsel confirm sections 4, 5 and 8 for each
country the team works in.

Programme name: [ ]
Owner: [name and role]
Sponsor: [name and role]
Version and date: [ ]
Next review: [date, no more than one quarter out]

## 1. Purpose

Goal (one only): [pipeline / hiring / reputation / category]

What success would look like in two quarters, in one or two sentences:

[ ]

What this programme is not for:

[ ]

## 2. Taking part

- Taking part is voluntary. You join by telling [owner] yourself.
- You can pause or leave at any time by telling [owner]. You do not need to
  give a reason.
- Whether you take part, how often you post and how your posts perform are
  not part of performance reviews, pay, promotion or team targets.
- Your account, your connections and your posts are yours, and stay yours if
  you leave [company].
- Nobody at [company] will ask for your login or post from your account.

## 3. What the company provides

| Provided | By whom | When |
|----------|---------|------|
| Weekly note: what happened, what is cleared for public use, source material, possible angles | [ ] | [day] |
| Time: the hours agreed with you and your manager | [ ] | Weekly |
| Someone to talk a draft through with, if you want | [ ] | On request |
| Answers to "can I say this?" | The checker for that trigger (section 6) | Within one working day |

The company does not provide posts to paste.

## 4. What is never scripted

Nobody will write these for you, and you should not accept them if offered:

- your opinions and your personal stories;
- praise for [company] or its products;
- reviews, ratings or testimonials;
- comments or reactions on colleagues' posts, or a schedule for making them;
- replies to criticism of [company];
- statements about competitors;
- text identical to what a colleague is posting.

Additions specific to [company]: [ ]

## 5. Saying where you work

When a post is about [company], its products, customers or openings:

- Your profile shows [company] as your current employer.
- The post itself makes the connection plain. Examples you can adapt:
  - "[example phrasing 1, confirmed with counsel]"
  - "[example phrasing 2]"
  - "[example phrasing 3]"
- If you received anything for posting beyond your normal pay, say so in the
  post.

## 6. Check before posting: triggers

Most posts need no check. If your draft contains any of the following, send it
to the named person first. They answer one question and do not edit your
style.

| If your draft includes | Send to | They answer |
|------------------------|---------|-------------|
| A customer, partner or supplier, named or identifiable | [ ] | Have they agreed to this mention? |
| A figure from internal systems | [ ] | Is it public and correct? |
| Anything not yet announced | [ ] | Is it public yet, or when? |
| A named competitor | [ ] | Is it factual and fair? |
| A legal, regulatory, safety or medical claim | [ ] | Is it accurate and permitted? |
| A colleague, named or pictured | That colleague | Do they agree? |
| An ongoing incident, dispute or investigation | [ ] | Should this wait? |
| [company-specific trigger] | [ ] | [ ] |

Answer time: within [one working day]. If you have not heard by then, send it
to [owner], who will answer the same day. No reply does not mean yes.

A checker may say yes, say no with a reason, ask for a fact to be corrected or
made less specific, or ask you to wait until a date. A checker may not rewrite
your opening, change your tone or add marketing language.

## 7. Restricted roles

| Person or role | Why restricted | Who checks posts about the business |
|----------------|----------------|-------------------------------------|
| [ ] | [ ] | [ ] |

## 8. Pausing during an incident

- Who can call a pause: [ ]
- What a pause covers: posts and comments about [company] and the incident.
  Your unrelated personal posting is not affected.
- How you will be told: [channel]
- What to say if someone asks you publicly: "[agreed line pointing to the official statement]"
- Who gives the all-clear: [ ]

You will never be asked to post in the company's defence.

## 9. Drafting tools

- You may use a writing assistant to draft or edit.
- You read, correct and own every sentence you publish.
- Confidential material goes only into tools on this approved list: [ ]

## 10. If you leave

Your account and audience go with you. You will be removed from the weekly
note on your last day. We will not ask you to delete posts unless one
disclosed something it should not have.

## 11. How we measure

- We report team totals, never a ranking of people.
- Sharing your own post figures is optional.
- We keep a log of outcomes (conversations, applications, introductions) with
  a note of how we know.
- We review the programme every [four] weeks with members and every quarter
  with [sponsor].

## 12. Agreed plans

Each member's row from the planner, as they accepted it.

| Member | Topics (their own) | Posts per week | Comments per week | Hours agreed | Stage | Accepted on |
|--------|--------------------|----------------|-------------------|--------------|-------|-------------|
| | | | | | | |
| | | | | | | |
| | | | | | | |

## 13. Sign-off

| Role | Name | Date |
|------|------|------|
| Owner | | |
| Sponsor | | |
| Legal review of sections 4, 5 and 8 | | |
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 323kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies 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.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide 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).Stars: 198kUpdated Claude CodeCodexVerifiedInstall