32 lines
1.3 KiB
Markdown
32 lines
1.3 KiB
Markdown
---
|
||
name: sentiment-analysis
|
||
description: Use to interpret qualitative feedback, trends, and risks across community
|
||
channels.
|
||
---
|
||
|
||
# Community Sentiment Analysis Skill
|
||
|
||
## When to Use
|
||
- Monitoring community tone during launches, incidents, or roadmap changes.
|
||
- Preparing executive updates that require member sentiment context.
|
||
- Prioritizing response or enablement efforts based on emerging themes.
|
||
|
||
## Framework
|
||
1. **Signal Sources** – forums, chat transcripts, surveys, social listening, support tickets.
|
||
2. **Tagging Schema** – categorize by emotion, topic, product area, persona, and severity.
|
||
3. **Trend Analysis** – track frequency over time, correlate with launches or incidents.
|
||
4. **Risk Scoring** – define thresholds for escalation (negative volume, influencer involvement, compliance).
|
||
5. **Action Loop** – translate findings into comms responses, content updates, or product feedback tasks.
|
||
|
||
## Templates
|
||
- Sentiment tagging sheet (message → tags → severity → owner).
|
||
- Trend report layout with charts + narrative.
|
||
- Escalation matrix referencing response SLAs.
|
||
|
||
## Tips
|
||
- Combine manual review with NLP dashboards to balance accuracy + scale.
|
||
- Capture representative quotes for exec storytelling.
|
||
- Pair with `measure-engagement` command to provide recommendations alongside metrics.
|
||
|
||
---
|