mcpField
S
social-listening

social-listening

github.com/guia-matthieu营销与增长150411 次安装4 周前更新
代码仓库

关于 social-listening

social-listening 是面向营销和传播团队的策略与分析技能,可通过关键词框架、情绪分析、趋势梳理和警报规划组织线上讨论监测;它不会访问平台或实时监测。

主要功能

  1. 01定义监测范围与目标
  2. 02建立关键词矩阵
  3. 03分析情绪与讨论趋势
  4. 04规划警报级别和报告
  5. 05提出回应思路

适用场景

  1. 01规划品牌健康监测
  2. 02为危机预警制定监测方案
  3. 03跟踪竞争对手提及
  4. 04分析营销活动讨论与反馈

安装

复制下面的命令,在终端中运行。

$npx skills add https://github.com/guia-matthieu/clawfu-skills --skill social-listening

安装后在 Claude Code 中输入/social-listening确认已加载。

详细介绍

社交媒体监听

系统地监控社交媒体和在线对话,以追踪品牌情绪、识别新出现的问题并发现机会。

何时使用此技能

  • 品牌健康度监控
  • 危机预警
  • 竞争对手追踪
  • 活动效果
  • 收集客户洞察

方法论基础

基于 Sprout Social methodology 和 Brandwatch analytics,结合:

  • 关键词监控
  • 情绪分析
  • 趋势识别
  • 影响者追踪

Claude 负责什么,哪些由你决定

Claude 负责你决定
设计监控策略工具选择
创建关键词列表警报阈值
分析情绪模式响应策略
识别趋势资源分配
建议响应方式升级处理决策

说明

第 1 步:定义监控范围

监控类别:

类别追踪内容示例
品牌公司名称、产品"@CompanyName"、“CompanyProduct”
人物高管、发言人CEO 姓名、创始人
行业行业术语、趋势行业关键词
竞争对手竞争对手相关提及竞争对手名称
问题潜在危机产品问题、服务投诉
第 2 步:建立关键词矩阵

关键词类型:

类型用途示例
主要直接提及品牌品牌名称、产品名称
次要相关对话行业术语、使用场景
负面危机指标“problem”、“issue”、“broken”
竞争对手竞争情报竞争对手名称、对比内容
第 3 步:设置警报

警报级别:

级别触发条件响应时间
绿色互动量正常,情绪积极/中性每日审核
黄色互动量上升,情绪参杂当日审核
橙色互动量激增,负面趋势数小时内
红色负面内容广泛传播,出现危机指标立即
第 4 步:分析发现

分析框架:

  • 互动量趋势(上升/下降/稳定)
  • 情绪分布(积极/中性/消极)
  • 主要主题和话题
  • 有影响力的声音
  • 地理模式
第 5 步:报告并采取行动

报告频率:

报告频率受众
实时警报触发时危机团队
每日摘要每日营销团队
每周摘要每周管理层
每月深入分析每月战略团队

示例

示例 1:社交媒体监听策略

输入:

Create a social listening strategy for:
- B2B SaaS company (project management)
- Main competitors: Asana, Monday, Notion
- Recent product launch: AI features

输出:

## Social Listening Strategy: Project Management SaaS

### Monitoring Objectives

| Objective | Priority | Key Questions |
|-----------|----------|---------------|
| Brand health | High | How are we perceived? |
| Product feedback | High | What do users say about AI features? |
| Competitive intel | Medium | What are competitors doing? |
| Industry trends | Medium | Where is PM software heading? |
| Crisis detection | High | Any emerging issues? |

---

### Keyword Matrix

#### Brand Keywords

| Category | Keywords | Platforms |
|----------|----------|-----------|
| Company Name | "[Company]", "@company" | All |
| Product Name | "[Product]", "[Product] app" | All |
| Misspellings | Common variants | All |
| Hashtags | #[Company], #[Product] | Twitter, LinkedIn |

#### Product Keywords

| Category | Keywords | Why Monitor |
|----------|----------|-------------|
| AI Features | "[Company] AI", "AI project management" | Launch feedback |
| Core Features | "[Company] tasks", "[Company] boards" | Product sentiment |
| Integrations | "[Company] Slack", "[Company] integration" | Partnership health |

#### Competitive Keywords

| Competitor | Keywords | What to Track |
|------------|----------|---------------|
| Asana | "Asana vs [Company]", "switching from Asana" | Win/loss signals |
| Monday | "Monday.com", "Monday vs [Company]" | Competitive positioning |
| Notion | "Notion for projects", "Notion PM" | Category overlap |
| General | "best project management", "PM tool 2026" | Category conversations |

#### Crisis Keywords

| Category | Keywords | Alert Level |
|----------|----------|-------------|
| Outage | "[Company] down", "[Company] not working" | Red |
| Security | "[Company] hack", "[Company] breach" | Red |
| Pricing | "[Company] expensive", "[Company] price increase" | Orange |
| Churn | "leaving [Company]", "cancelled [Company]" | Yellow |
| Bugs | "[Company] bug", "[Company] broken" | Yellow |

---

### Platform Strategy

| Platform | Focus | Keywords | Frequency |
|----------|-------|----------|-----------|
| Twitter/X | Real-time sentiment | All brand, crisis | Continuous |
| LinkedIn | B2B discussions | Industry, competitor | Daily |
| Reddit | Deep user feedback | r/projectmanagement, product | Daily |
| G2/Capterra | Review sentiment | Product reviews | Weekly |
| Hacker News | Tech community | Product, competitor | As trending |

---

### Alert Configuration

#### Red Alerts (Immediate Response)

**Triggers:**
- Volume spike >300% normal
- Sentiment shift >50% negative
- Viral post (>1000 engagements)
- Keywords: "outage", "down", "breach", "hack"

**Response:**
- Slack #crisis-alerts channel
- SMS to on-call team
- Auto-pause scheduled posts

---

#### Orange Alerts (Same-Day Response)

**Triggers:**
- Volume spike >100% normal
- Negative sentiment >30%
- Trending competitor comparison
- Keywords: "expensive", "worse", "frustrated"

**Response:**
- Slack #social-alerts
- Email to marketing lead
- Review within 4 hours

---

#### Yellow Alerts (Next-Day Review)

**Triggers:**
- Volume spike >50% normal
- Notable influencer mention
- Competitor activity spike
- Keywords: "considering", "alternative", "switching"

**Response:**
- Daily digest inclusion
- Assign for monitoring
- Review within 24 hours

---

### Analysis Template

#### Daily Report

社交媒体监听每日摘要

日期:[Date]

互动量摘要
指标今天与昨天相比与 7 天平均值相比
总提及数X+/-Y%+/-Z%
品牌提及数X+/-Y%+/-Z%
情绪得分X+/-Y+/-Z
情绪细分
  • 积极:X%
  • 中性:Y%
  • 消极:Z%
热门对话
  1. [摘要 + 链接]
  2. [摘要 + 链接]
  3. [摘要 + 链接]
竞争对手动态
  • Asana:[值得关注的动态]
  • Monday:[值得关注的动态]
  • Notion:[值得关注的动态]
行动事项
  • [需要时采取的行动]
警报状态:绿色/黄色/橙色/红色

---

### AI Feature Launch Monitoring

**Specific Keywords:**
- "[Company] AI"
- "AI project management"
- "[Company] automation"
- "AI features PM tool"

**What to Track:**
| Metric | Target | Alert If |
|--------|--------|----------|
| Mention volume | 2x normal | <50% or >300% |
| Sentiment | >60% positive | <40% positive |
| Feature requests | Document all | - |
| Bug reports | <5/day | >10/day |

**Competitor Response Monitoring:**
- Are competitors announcing similar features?
- How is our positioning being compared?
- What gaps are users identifying?
示例 2:快速情绪分析

输入:

Analyze this week's social mentions:
- Total mentions: 450 (up 30%)
- Positive: 40%
- Neutral: 35%
- Negative: 25%
- Top negative theme: "pricing"
- One viral tweet (15K RT): "Just discovered [Company] raised prices 40%"

输出:

## Quick Sentiment Analysis

### Alert Level: ORANGE

---

### Summary

| Metric | Value | Status |
|--------|-------|--------|
| Volume | 450 (+30%) | Elevated |
| Sentiment | 40% positive | Below target |
| Negative | 25% | Above normal |
| Viral Content | Yes | Action needed |

---

### Key Finding

**Pricing is dominating the conversation**

The viral tweet about 40% price increase is:
- Driving 30% volume spike
- Shifting sentiment negative
- Spreading misinformation (if price increase was different)

---

### Immediate Actions

| Action | Owner | Timeline |
|--------|-------|----------|
| Verify price increase details | Product/Biz | Immediate |
| Draft response to viral tweet | Comms | 2 hours |
| Prepare pricing FAQ | Support | Today |
| Monitor for escalation | Social | Ongoing |

---

### Response Options

**If price increase was less than 40%:**

Hi [Name],感谢你的反馈。澄清一下——我们最近的更新将 [specific] 的价格提高了 [X%],而不是 40%。 以下是具体变更及原因:[link]

如果你有疑问,我们很乐意进一步讨论。


**If price increase was accurate:**

Hi [Name],我们理解你的感受。我们知道,价格变动总是难以接受。以下是我们做出这一决定的原因,以及你将获得的回报:[link]

如果你想讨论自己的账户,我们的团队随时可以提供帮助。


---

### Escalation Watch

Monitor for:
- Influencer pile-on
- Media pickup
- Support ticket spike
- Churn mentions

技能边界

此技能擅长的事项
  • 设计监控策略
  • 创建关键词框架
  • 分析情绪模式
  • 构建警报系统
此技能无法做到的事
  • 访问社交平台
  • 实时监控
  • 自动回复
  • 了解你的具体工具

迭代指南

后续提示词:

  • “为 [scenario] 创建回复模板”
  • “我们应如何处理 [specific mention]?”
  • “设计一个竞争对手监控仪表板”
  • “我们应该追踪 [campaign] 的哪些内容?”

参考资料

  • Sprout Social Listening Guide
  • Brandwatch Analytics Methodology
  • Hootsuite Social Listening
  • Meltwater Media Intelligence

相关技能

  • crisis-detector - 早期预警升级
  • response-coordinator - 危机响应
  • reputation-recovery - 危机后重建

技能元数据

  • 领域:危机 / 营销
  • 复杂度:中级
  • 模式:cyborg
  • 价值实现时间:制定策略需 1-2 小时
  • 前置条件:平台访问权限、品牌背景

评论

支持 Markdown