Token导航 LogoToken导航

Agent Skill · 研究检索

social-listening(社交聆听)

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

social-listening 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 21,159。

总安装 4,945周安装 204GitHub Stars 85下载 1,616核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于关键词搜索、任务场景匹配或来源线索追踪等研究检索场景。通过 npx skills add 命令从指定 GitHub 仓库安装并使用。安装前需确认权限范围、维护状态,以及是否涉及联网或文件操作。

social-listening 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/social-listening

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/guia-matthieu/clawfu-skills --skill social-lis…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

social-listening 怎么安装?

在终端执行 npx skills add https://github.com/guia-matthieu/clawfu-skills --skill social-listening。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

social-listening 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

social-listening 需要什么权限?

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

social-listening 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

social-listening 用的人多吗?

公开数据是累计安装 4,945 次,近一周安装 204 次,下载 1,616 次,GitHub 85 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

social-listening 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
social-listening

社交聆听 · 本页

4,94585只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Social Listening

Systematically monitor social media and online conversations to track brand sentiment, identify emerging issues, and spot opportunities.

When to Use This Skill

  • Brand health monitoring
  • Crisis early warning
  • Competitor tracking
  • Campaign performance
  • Customer insight gathering

Methodology Foundation

Based on Sprout Social methodology and Brandwatch analytics, combining:

  • Keyword monitoring
  • Sentiment analysis
  • Trend identification
  • Influencer tracking

What Claude Does vs What You Decide

Claude DoesYou Decide
Designs monitoring strategyTool selection
Creates keyword listsAlert thresholds
Analyzes sentiment patternsResponse strategy
Identifies trendsResource allocation
Suggests response approachesEscalation calls

Instructions

Step 1: Define Monitoring Scope

Monitoring Categories:

CategoryWhat to TrackExamples
BrandCompany name, products"@CompanyName", "CompanyProduct"
PeopleExecutives, spokespeopleCEO name, founder
IndustrySector terms, trendsIndustry keywords
CompetitorsCompetitor mentionsCompetitor names
IssuesPotential crisesProduct issues, service complaints

Step 2: Build Keyword Matrix

Keyword Types:

TypePurposeExamples
PrimaryDirect brand mentionsBrand name, product names
SecondaryRelated conversationsIndustry terms, use cases
NegativeCrisis indicators"problem", "issue", "broken"
CompetitorCompetitive intelligenceCompetitor names, comparison

Step 3: Set Up Alerts

Alert Levels:

LevelTriggerResponse Time
GreenNormal volume, positive/neutralDaily review
YellowElevated volume, mixed sentimentSame-day review
OrangeHigh volume spike, negative trendHours
RedViral negative, crisis indicatorsImmediate

Step 4: Analyze Findings

Analysis Framework:

  • Volume trends (up/down/stable)
  • Sentiment distribution (positive/neutral/negative)
  • Key themes and topics
  • Influential voices
  • Geographic patterns

Step 5: Report and Act

Reporting Cadence:

ReportFrequencyAudience
Real-time alertsAs triggeredCrisis team
Daily digestDailyMarketing
Weekly summaryWeeklyLeadership
Monthly deep diveMonthlyStrategy

Examples

Example 1: Social Listening Strategy

Input:

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

Output:

## 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

Social Listening Daily Digest

Date: [Date]

Volume Summary

MetricTodayvs. Yesterdayvs. 7-Day Avg
Total MentionsX+/-Y%+/-Z%
Brand MentionsX+/-Y%+/-Z%
Sentiment ScoreX+/-Y+/-Z

Sentiment Breakdown

  • Positive: X%
  • Neutral: Y%
  • Negative: Z%

Top Conversations

  1. [Summary + Link]
  2. [Summary + Link]
  3. [Summary + Link]

Competitor Activity

  • Asana: [Notable activity]
  • Monday: [Notable activity]
  • Notion: [Notable activity]

Action Items

  • [Action if needed]

Alert Status: GREEN/YELLOW/ORANGE/RED

---

### 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?

Example 2: Quick Sentiment Analysis

Input:

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%"

Output:

## 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], thanks for the feedback. Just to clarify—our recent update increased [specific] pricing by [X%], not 40%. Here's what changed and why: [link]

Happy to discuss if you have questions.

**If price increase was accurate:**

Hi [Name], we hear you. We know pricing changes are never easy to absorb. Here's why we made this decision and what you're getting in return: [link]

Our team is available if you'd like to discuss your account.

---

### Escalation Watch

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

Skill Boundaries

What This Skill Does Well

  • Designing monitoring strategies
  • Creating keyword frameworks
  • Analyzing sentiment patterns
  • Structuring alert systems

What This Skill Cannot Do

  • Access social platforms
  • Monitor in real-time
  • Automatically respond
  • Know your specific tools

Iteration Guide

Follow-up Prompts:

  • "Create response templates for [scenario]"
  • "How should we handle [specific mention]?"
  • "Design a competitor monitoring dashboard"
  • "What should we track for [campaign]?"

References

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

Related Skills

  • crisis-detector - Early warning escalation
  • response-coordinator - Crisis response
  • reputation-recovery - Post-crisis rebuild

Skill Metadata

  • Domain: Crisis / Marketing
  • Complexity: Intermediate
  • Mode: cyborg
  • Time to Value: 1-2 hours for strategy
  • Prerequisites: Platform access, brand context

平台分布

Codex

34.89%
按下载量换算564

Claude

28.59%
按下载量换算462

Cursor

19.05%
按下载量换算308

Gemini CLI

8.81%
按下载量换算142

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills