Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

sales-employee-advocacy销售员工宣传

Agent Skill

sales-employee-advocacy 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

441

周安装

18

GitHub Stars

13

下载量

141
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/sales-skills/sales --skill sales-employee-advocacy

简介

sales-employee-advocacy 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 当前顶部介绍:sales-employee-advocacy 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。
  • 可结合来源仓库、安装命令和原始 README 继续核验具体用法。

SKILL.md

Employee Advocacy Strategy

Helps the user design and run employee advocacy programs — turning employees into brand ambassadors on social media through content curation, gamification, compliance controls, and measurable ROI.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

  1. What do you need help with?

- A) Designing an employee advocacy program from scratch - B) Choosing an employee advocacy tool - C) Increasing employee participation in an existing program - D) Creating a content library for employees to share - E) Setting up compliance controls and brand guidelines - F) Measuring advocacy ROI and earned media value - G) Something else — describe it

  1. Company size and structure?

- A) Startup / small team (under 50 employees) - B) Mid-market (50-500 employees) - C) Enterprise (500+ employees) - D) Agency (managing for clients)

  1. Current state?

- A) No advocacy program yet - B) Informal — some employees share on their own - C) Have a program but low participation - D) Have a tool but want to switch or optimize

  1. Primary goal?

- A) Increase brand awareness and reach - B) Generate leads and pipeline - C) Support recruiting and employer brand - D) Amplify product launches and campaigns - E) All of the above

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end.

Step 2 — Route or answer directly

If the request maps to a platform-specific skill, route:

  • Sprout Social Employee Advocacy setup → /sales-sproutsocial
  • Social media management (publishing, scheduling) → /sales-social-media-management
  • Influencer marketing with external creators → /sales-influencer-marketing
  • Sales enablement content management → /sales-content
  • Content strategy and creation → /content-strategy

Otherwise, answer directly from the strategy knowledge below.

Step 3 — Employee advocacy strategy reference

Read references/platform-guide.md for detailed module documentation, pricing, integrations, and data model.

*You no longer need the platform guide details — focus on the user's specific situation.*

Step 4 — Actionable guidance

Based on the user's specific question:

  1. Program design — goals, pilot group, content guidelines, launch plan
  2. Tool selection — match to team size, existing tools, and budget
  3. Participation boost — gamification, executive buy-in, content quality, friction reduction
  4. Content library — what to include, how to curate, caption writing, refresh cadence
  5. Compliance — brand guidelines, regulated industry requirements, GDPR
  6. ROI measurement — EMV, adoption metrics, pipeline attribution

Gotchas

*Best-effort from research — review these, especially items about platform capabilities and pricing that may change.*

  • Mandatory participation backfires. Forcing employees to share makes content feel inauthentic and causes resentment. The best programs make sharing easy and rewarding, not required.
  • Content quality is the #1 participation driver. If employees wouldn't share the content on their own, gamification won't fix it. Invest in creating genuinely shareable content — industry insights, team wins, and thought leadership outperform press releases.
  • Executive participation is non-negotiable. If the CEO and VPs aren't sharing, employees won't either. Get leadership to commit before launching.
  • Don't expect instant scale. Start with 20-50 enthusiastic employees, prove value, then expand. Company-wide launches have high initial sign-ups and low sustained engagement.
  • Advocacy tools add cost on top of social management. Sprout Advocacy requires a Sprout subscription + advocacy add-on. DSMN8 is $5-8/user/month. For a 200-person program on DSMN8, that's $1,000-1,600/month. Budget accordingly.
  • Employees sharing identical content looks bad. If 20 people post the same LinkedIn post with the same caption, it's obviously corporate. Use tools that generate personalized variations (DSMN8) or strongly encourage employees to edit captions.
  • Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.

Before recommending a specific platform skill

This skill covers a strategy domain across many platforms. Before pointing the user to any specific platform skill (any /sales-{platform} listed in ## Related skills, e.g., /sales-mailshake, /sales-klaviyo, /sales-apollo), read that platform skill's actual SKILL.md first. The 1-line description in ## Related skills is enough to *identify* a candidate — it's not enough to *commit* to it or to write a prompt that invokes it well.

How to read it:

  • If ~/.claude/skills/{skill-name}/SKILL.md exists locally, Read it.
  • For sales-* skills, WebFetch directly from this repo: https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md — e.g., for sales-mailshake: https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md.
  • For non-sales-* skills (third-party), look up {org}/{repo} in ~/.claude/skills/sales-do/references/skill-sources.md if installed and fetch the same skills/{skill-name}/SKILL.md path under that repo.

After reading, ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its argument-hint shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's argument-hint. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.

Related skills

  • /sales-sproutsocial — Sprout Social platform help — includes Employee Advocacy module setup and config
  • /sales-social-media-management — Social media management strategy — publishing, scheduling, engagement, tool comparison
  • /sales-social-listening — Social listening strategy — monitor how employee advocacy impacts brand mentions
  • /sales-content — Sales content management — organize and distribute sales collateral
  • /sales-influencer-marketing — Influencer marketing with external creators (not employees)
  • /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do

Examples

Example 1: Design an employee advocacy program

User says: "I want to launch an employee advocacy program for our 200-person B2B company. Where do I start?" Skill does:

  1. Defines goals: brand awareness + lead generation
  2. Recommends pilot group of 25-30 across sales, marketing, and leadership
  3. Creates content guidelines and initial library of 20 shareable pieces
  4. Recommends DSMN8 or GaggleAMP for B2B-focused structured activities
  5. Outlines a 4-week launch plan with gamification Result: Complete advocacy program design with tool recommendation and launch timeline

Example 2: Boost low participation

User says: "We launched employee advocacy 3 months ago but only 15% of employees are sharing regularly" Skill does:

  1. Diagnoses common causes: content quality, executive participation, friction, awareness
  2. Audits current content library — is it genuinely shareable?
  3. Recommends quick wins: executive commitment, Slack integration, weekly leaderboard, content refresh
  4. Designs a re-launch campaign with a 2-week contest Result: Actionable plan to increase adoption from 15% to 30%+ within 6 weeks

Example 3: Choose an advocacy tool

User says: "We use Hootsuite for social management. Should we use Amplify or a separate advocacy tool?" Skill does:

  1. Compares Hootsuite Amplify (integrated, simpler) vs. DSMN8 (AI personalization) vs. GaggleAMP (structured activities)
  2. Evaluates trade-offs: integration convenience vs. feature depth
  3. Recommends Amplify if ease of adoption is the priority, DSMN8 if AI personalization matters
  4. Notes cost comparison: Amplify add-on vs. standalone tool pricing Result: Clear recommendation based on their existing tool stack and priorities

Troubleshooting

Low employee participation after launch

Symptom: Initial sign-ups were strong but weekly sharing has dropped to under 20% Cause: Content fatigue, no ongoing motivation, tool friction, or lack of visible leadership participation Solution: Refresh the content library with new formats (short posts, images, polls). Launch a 2-week competition with meaningful prizes. Get the CEO to post and share the leaderboard. Reduce friction with push notifications and one-click sharing from mobile. Reframe the value: "build your LinkedIn presence" resonates more than "help marketing".

Content looks robotic and corporate

Symptom: Employee posts all look identical, and connections are calling it out Cause: Employees sharing pre-written captions without personalization Solution: Switch to tools that generate unique caption variations per employee (DSMN8). Coach employees to add one personal sentence to every share. Remove the most corporate-sounding content from the library. Feature examples of good personalized shares.

Can't prove ROI to leadership

Symptom: Program is running but leadership questions the investment Cause: Not tracking the right metrics or connecting to business outcomes Solution: Set up UTM tracking on all advocacy links. Calculate EMV monthly (total reach × industry CPM). Track clicks-to-website and compare to paid social cost-per-click. For B2B, track which deals had an advocacy touchpoint in the buyer journey via CRM attribution.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.96%
按下载量换算48

Claude

30.76%
按下载量换算43

Cursor

16.53%
按下载量换算23

Gemini CLI

9.02%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

来源信息

继续浏览同类 Skills