Token导航 LogoToken导航TokenDH.com
开发只读clawhub未标认证来源可访问clear审计通过

linkedin-employee-advocacyLinkedIn 员工倡导

Agent Skill

linkedin-employee-advocacy 用于辅助安全审计、权限检查和凭据风险排查,适合在 OpenClaw 中需要复核安全边界、认证流程或敏感配置时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,305

周安装

97

GitHub Stars

公开资料未说明

下载量

807
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:linkedin-employee-advocacy(LinkedIn 员工倡导)
来源仓库:https://github.com/sergebulaev/linkedin-employee-advocacy
安装命令:
openclaw skills install linkedin-employee-advocacy
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install linkedin-employee-advocacy

简介

规划员工倡导计划实施方案。安装时按仓库提供的命令执行,建议先在测试环境验证依赖、命令权限和文件改动范围。

  • 涵盖 14 天发布手册和品牌推广。
  • 支持大规模真实语音发布。适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。
  • 需 HR 与营销团队协作执行。
  • linkedin-employee-advocacy 属于开发类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

name
linkedin-employee-advocacy
description
Plan, launch, and operate a LinkedIn employee advocacy program for a marketing team. Covers 14-day launch playbook, authentic-voice posting at scale, brand guideline governance with optional review, per-post time budgeting, team posting cadence benchmarks, and ROI measurement (team reach, engagement, pipeline impact). Triggers on "employee advocacy", "team posting program", "scale LinkedIn across marketing team", "brand amplification", "advocacy ROI", "get the team posting", "employee-generated content".

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

Related skills

  • 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-engagement — track which team members' comments drive inbound

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

78.8%
按下载量换算636

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills