playbooks

home / skills / gtmagents / gtm-agents / community-sentiment-dashboard

community-sentiment-dashboard skill

/plugins/social-media-marketing/skills/community-sentiment-dashboard

This skill provides a weekly social sentiment dashboard that tracks signals, risk, and advocacy to inform executive updates and operational actions.

npx playbooks add skill gtmagents/gtm-agents --skill community-sentiment-dashboard

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.3 KB
---
name: community-sentiment-dashboard
description: Reporting template for tracking sentiment, risks, and advocacy signals
  across social + community channels.
---

# Community Sentiment Dashboard Skill

## When to Use
- Weekly/monthly social listening readouts.
- Real-time monitoring during launches, incidents, or crisis scenarios.
- Executive updates that require quantified sentiment + qualitative insights.

## Framework
1. **Signal Sources** – social listening feeds, community platforms, support tags, surveys.
2. **Sentiment Stack** – volume, sentiment %, topics, influencer tiers, escalation status.
3. **Risk/Opportunity Board** – flagged issues, severity, owners, response progress.
4. **Advocacy Spotlight** – top advocates, UGC, partnership opportunities.
5. **Action Register** – follow-ups routed to comms, product, support, leadership.

## Templates
- Dashboard slide layout (KPI tiles + trend graphs + highlights/lowlights).
- Escalation tracker with severity, owner, due date, next update.
- Advocate tracker with contact info, potential activation ideas.

## Tips
- Set alert thresholds per channel to avoid noise fatigue.
- Pair qualitative snippets with data visuals for executive context.
- Use with `monitor-community-sentiment` for automated packet generation.

---

Overview

This skill provides a production-ready reporting template for tracking community and social sentiment, surface risks, and highlight advocacy signals across channels. It combines quantitative metrics and qualitative snippets into slide-ready dashboards and trackers to support decision-making during routine reporting and high-stakes incidents. Use it to standardize readouts, speed escalation, and convert insights into actionable follow-ups.

How this skill works

The skill ingests signal sources such as social listening feeds, community platforms, support tags, and survey results, and maps them into a sentiment stack containing volume, sentiment percentage, topical breakdowns, influencer tiers, and escalation status. It generates a suite of templates: KPI tiles and trend graphs for dashboards, an escalation tracker with severity and owners, an advocate tracker, and an action register linking follow-ups to teams. Outputs are slide-ready and structured for weekly/monthly reports or real-time monitoring.

When to use it

  • Weekly or monthly social listening and community readouts for leadership.
  • Real-time monitoring during product launches, incidents, or PR crises.
  • Prep for executive briefings that need quantified sentiment plus qualitative context.
  • Operational handoffs between comms, product, and support teams.
  • Tracking and activating top advocates or user-generated content opportunities.

Best practices

  • Define channel-specific alert thresholds to reduce noise and prevent alert fatigue.
  • Combine short qualitative excerpts with visual metrics to give context to executives.
  • Classify and tag items by severity and owner immediately to ensure accountability.
  • Keep the escalation tracker minimal—severity, owner, due date, and next update.
  • Refresh top-advocate lists regularly with contact status and activation ideas.

Example use cases

  • Weekly dashboard for marketing and customer success summarizing sentiment trends and top topics.
  • Incident response pack that flags high-severity posts, assigns owners, and tracks mitigations.
  • Executive one-pager showing net sentiment, volume changes, top risks, and advocacy highlights.
  • Advocacy program brief that lists top advocates, recent UGC, and proposed activation opportunities.
  • Cross-functional action register that routes follow-ups to comms, product, support, and leadership.

FAQ

What signal sources should I connect first?

Prioritize high-volume public channels and support tags, then add closed community platforms and survey feeds to round out context.

How do I avoid dashboard noise?

Set per-channel thresholds, focus on topic-level aggregation, and surface only items above a defined severity or engagement metric.