정보
이 스킬은 소셜 미디어와 온라인 언급을 자동으로 모니터링하여 브랜드 감정을 추적하고, 신규 이슈를 식별하며, 대화 트렌드를 분석할 수 있게 합니다. 키워드 모니터링과 감정 분석을 활용하여 브랜드 건강 모니터링, 위기 조기 경보, 경쟁사 추적을 위해 설계되었습니다. 개발자는 이를 통해 체계적인 분석을 바탕으로 고객 인사이트를 수집하고 대응 전략을 수립할 수 있습니다.
빠른 설치
Claude Code
추천npx skills add guia-matthieu/clawfu-skills -a claude-code/plugin add https://github.com/guia-matthieu/clawfu-skillsgit clone https://github.com/guia-matthieu/clawfu-skills.git ~/.claude/skills/social-listeningClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
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 Does | You Decide |
|---|---|
| Designs monitoring strategy | Tool selection |
| Creates keyword lists | Alert thresholds |
| Analyzes sentiment patterns | Response strategy |
| Identifies trends | Resource allocation |
| Suggests response approaches | Escalation calls |
Instructions
Step 1: Define Monitoring Scope
Monitoring Categories:
| Category | What to Track | Examples |
|---|---|---|
| Brand | Company name, products | "@CompanyName", "CompanyProduct" |
| People | Executives, spokespeople | CEO name, founder |
| Industry | Sector terms, trends | Industry keywords |
| Competitors | Competitor mentions | Competitor names |
| Issues | Potential crises | Product issues, service complaints |
Step 2: Build Keyword Matrix
Keyword Types:
| Type | Purpose | Examples |
|---|---|---|
| Primary | Direct brand mentions | Brand name, product names |
| Secondary | Related conversations | Industry terms, use cases |
| Negative | Crisis indicators | "problem", "issue", "broken" |
| Competitor | Competitive intelligence | Competitor names, comparison |
Step 3: Set Up Alerts
Alert Levels:
| Level | Trigger | Response Time |
|---|---|---|
| Green | Normal volume, positive/neutral | Daily review |
| Yellow | Elevated volume, mixed sentiment | Same-day review |
| Orange | High volume spike, negative trend | Hours |
| Red | Viral negative, crisis indicators | Immediate |
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:
| Report | Frequency | Audience |
|---|---|---|
| Real-time alerts | As triggered | Crisis team |
| Daily digest | Daily | Marketing |
| Weekly summary | Weekly | Leadership |
| Monthly deep dive | Monthly | Strategy |
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
| Metric | Today | vs. Yesterday | vs. 7-Day Avg |
|---|---|---|---|
| Total Mentions | X | +/-Y% | +/-Z% |
| Brand Mentions | X | +/-Y% | +/-Z% |
| Sentiment Score | X | +/-Y | +/-Z |
Sentiment Breakdown
- Positive: X%
- Neutral: Y%
- Negative: Z%
Top Conversations
- [Summary + Link]
- [Summary + Link]
- [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 escalationresponse-coordinator- Crisis responsereputation-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
GitHub 저장소
Frequently asked questions
What is the social-listening skill?
social-listening is a Claude Skill by guia-matthieu. Skills package instructions and resources that Claude loads on demand, so Claude can perform social-listening-related tasks without extra prompting.
How do I install social-listening?
Use the install commands on this page: add social-listening to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does social-listening belong to?
social-listening is in the Other category, tagged general.
Is social-listening free to use?
Yes. social-listening is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.
연관 스킬
LlamaGuard는 폭력 및 혐오 발언 등 6가지 안전 범주에서 LLM 입력과 출력을 조정하기 위한 Meta의 70-80억 파라미터 모델입니다. 94-95% 정확도를 제공하며 vLLM, Hugging Face 또는 Amazon SageMaker를 사용해 배포할 수 있습니다. 이 기술을 사용하여 AI 애플리케이션에 콘텐츠 필터링 및 안전 가드레일을 손쉽게 통합하세요.
이 Claude Skill은 리소스 적정화, 태깅 전략, 지출 분석을 통해 개발자들이 클라우드 비용을 최적화할 수 있도록 지원합니다. AWS, Azure, GCP에서 클라우드 비용을 절감하고 비용 거버넌스를 구현하기 위한 프레임워크를 제공합니다. 인프라 비용을 분석하거나, 리소스를 적정화하거나, 예산 제약을 충족해야 할 때 사용하세요.
이 Claude Skill은 스프레드, 오버/언더, 프로프 베트를 포함한 스포츠 베팅 시장을 분석합니다. 역사적 추이와 상황별 통계를 검토하여 가치 베트를 발견하고, 교육적 목적으로 실행 가능한 권장 사항이 담긴 구조화된 마크다운 결과를 제공합니다. 개발자는 이 기능을 스포츠 베팅 분석 도구에 활용할 수 있으며, 단순히 엔터테인먼트/교육 목적으로만 설계되었음을 유의해야 합니다.
이 스킬은 bitsandbytes를 사용하여 LLM을 8비트 또는 4비트 정밀도로 양자화하며, 최소한의 정확도 손실로 50-75%의 메모리 감소를 달성합니다. 제한된 GPU 메모리에서 더 큰 모델을 실행하거나 추론을 가속화하는 데 이상적이며, INT8, NF4, FP4와 같은 형식을 지원합니다. 이 스킬은 HuggingFace Transformers와 통합되어 QLoRA 학습 및 8비트 옵티마이저를 가능하게 합니다.
