본문으로 건너뛰기
cccskills
무료GitHub에 공개

social-listening

Monitor social media and online mentions for brand sentiment, emerging issues, and conversation trends

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

guia-matthieu/clawfu-skills스타 150(GitHub 150 + cccskills 0)

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md10.1 KB

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Measure and optimize growth using the AARRR (Pirate Metrics) framework with stage-specific KPIs and funnel analysis

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

guia-matthieu/clawfu-skills1502026년 10월 1일 업데이트

Calculate A/B test statistical significance. Use when: determining if test results are significant; calculating required sample size; estimating test duration; analyzing conversion experiments; making data-driven decisions

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

guia-matthieu/clawfu-skills1502026년 10월 1일 업데이트

Assess customer account health using product usage, support sentiment, payment status, and relationship signals

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

guia-matthieu/clawfu-skills1502026년 10월 1일 업데이트

Analyze paid advertising performance across channels and recommend budget reallocation to maximize ROAS and minimize CAC. Use when: planning quarterly ad budget allocation, diagnosing underperforming ad channels, deciding whether to scale spend on a channel, calculating marginal ROI across Google Ads, Meta, LinkedIn, or TikTok, rebalancing media mix after performance shifts, or setting up a test-and-scale framework for new channels.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

guia-matthieu/clawfu-skills1502026년 10월 1일 업데이트

Use when testing skills, commands, or agents for quality. Use after creating new skills, before deploying agents, or when debugging inconsistent agent behavior. Triggers on "evaluate", "test quality", "is this skill working", or QA of AI workflows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

guia-matthieu/clawfu-skills1502026년 10월 1일 업데이트

Use when analyzing server logs to understand how AI crawlers (GPTBot, ClaudeBot, PerplexityBot) interact with your site. Use when optimizing content placement for LLM retrieval, diagnosing why AI search isn't citing your content, or auditing crawl patterns to find optimization gaps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

guia-matthieu/clawfu-skills1502026년 10월 1일 업데이트

guia-matthieu의 스킬 모두 보기

이 스킬의 문제 신고