MCP HubMCP Hub
Retour aux compétences

social-listening

guia-matthieu
Mis à jour 2 days ago
7 vues
111
20
111
Voir sur GitHub
Autregeneral

À propos

Cette compétence permet une surveillance automatisée des médias sociaux et des mentions en ligne pour suivre le sentiment de la marque, identifier les problèmes émergents et analyser les tendances de conversation. Elle est conçue pour la surveillance de la santé de la marque, l'alerte précoce en cas de crise et le suivi des concurrents, en utilisant la surveillance par mots-clés et l'analyse des sentiments. Les développeurs peuvent l'exploiter pour recueillir des insights clients et éclairer les stratégies de réponse sur la base d'analyses systématiques.

Installation rapide

Claude Code

Recommandé
Principal
npx skills add guia-matthieu/clawfu-skills -a claude-code
Commande PluginAlternatif
/plugin add https://github.com/guia-matthieu/clawfu-skills
Git CloneAlternatif
git clone https://github.com/guia-matthieu/clawfu-skills.git ~/.claude/skills/social-listening

Copiez et collez cette commande dans Claude Code pour installer cette compétence

Documentation

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

Dépôt GitHub

guia-matthieu/clawfu-skills
Chemin: skills/crisis/social-listening
0
ai-skillsanthropicclaude-codeclaude-skillsmarketingmcp-server

Compétences associées

llamaguard

Autre

LlamaGuard est le modèle de Meta, doté de 7 à 8 milliards de paramètres, conçu pour modérer les entrées et sorties des LLM selon six catégories de sécurité comme la violence et les discours haineux. Il offre une précision de 94 à 95 % et peut être déployé avec vLLM, Hugging Face ou Amazon SageMaker. Utilisez cette compétence pour intégrer facilement le filtrage de contenu et des garde-fous de sécurité dans vos applications d'IA.

Voir la compétence

cost-optimization

Autre

Cette compétence de Claude aide les développeurs à optimiser les coûts du cloud grâce au redimensionnement des ressources, aux stratégies d'étiquetage et à l'analyse des dépenses. Elle fournit un cadre pour réduire les dépenses cloud et mettre en œuvre une gouvernance des coûts sur AWS, Azure et GCP. Utilisez-la lorsque vous devez analyser les coûts d'infrastructure, redimensionner les ressources ou respecter des contraintes budgétaires.

Voir la compétence

quantizing-models-bitsandbytes

Autre

Cette compétence quantifie les LLMs en précision 8 bits ou 4 bits à l'aide de bitsandbytes, permettant une réduction de 50 à 75 % de la mémoire utilisée avec une perte de précision minime. Elle est idéale pour exécuter des modèles plus volumineux sur une mémoire GPU limitée ou pour accélérer l'inférence, prenant en charge des formats comme INT8, NF4 et FP4. La compétence s'intègre à HuggingFace Transformers et permet l'entraînement QLoRA ainsi que l'utilisation d'optimiseurs en 8 bits.

Voir la compétence

dispatching-parallel-agents

Autre

Cette compétence Claude déploie plusieurs agents pour enquêter et résoudre simultanément 3 problèmes indépendants ou plus. Elle est conçue pour des scénarios impliquant des défaillances non liées qui peuvent être résolues sans état partagé ni dépendances. La capacité fondamentale est la résolution de problèmes en parallèle, en assignant un agent par domaine problématique indépendant afin de maximiser l'efficacité.

Voir la compétence