community-sentiment-dashboard

31 stars 7 forks

Reporting template for tracking sentiment, risks, and advocacy signals across social + community channels.

Marketplace

Also in: ci cd networking data analysis

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →

Claude Code (CLI) Fast

skilz install gtmagents/gtm-agents/community-sentiment-dashboard

OpenCode (CLI) Fast

skilz install gtmagents/gtm-agents/community-sentiment-dashboard --agent opencode

OpenAI Codex (CLI) Native

skilz install gtmagents/gtm-agents/community-sentiment-dashboard --agent codex

Gemini CLI (Project) Project

skilz install gtmagents/gtm-agents/community-sentiment-dashboard --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents

For Claude Desktop Easy

Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

Manual Installation

1. Clone the repository:

git clone https://github.com/gtmagents/gtm-agents

2. Copy the agent skill directory:

cp -r gtm-agents/plugins/social-media-marketing/skills/community-sentiment-dashboard ~/.claude/skills/

Owner: gtmagents (GitHub)
Repository: gtm-agents
Stars: 31
Forks: 7
Type: Non-Technical
Meta-Domain: media
Primary Domain: monitoring
Market Score: 28

Agentic Skill Grades →

Agent Skill Grade

Score: 62/100 Click to see breakdown

Score Breakdown

Spec Compliance

11/15

PDA Architecture

17/30

Ease of Use

15/25

Writing Style

7/10

Utility

11/20

Modifiers: +1

Areas to Improve

Description needs trigger phrases
Missing Template Files
Weak Trigger Terms in Description

Recommendations

Focus on improving Pda (currently 17/30)
Focus on improving Utility (currently 11/20)
Address 3 high-severity issues first

Graded: 2026-01-24

Developer Feedback

I found your community-sentiment-dashboard skill and noticed it's tackling a really useful problem—real-time sentiment tracking across communities—but the implementation feels like it's caught between a few different architectural directions. With a 62/100, there's solid potential here, but I'd like to dig into what's holding it back.

Links:

The TL;DR

You're at 62/100, which lands you in D territory. This is based on Anthropic's five-pillar framework for agentic skills. Your Spec Compliance is actually solid (11/15), but Utility is dragging things down (11/20)—you've got the structure, just missing the substance.

What's Working Well

Valid frontmatter – Your YAML is clean and follows conventions. Hyphen-case naming is correct.
Clear problem domain – The five-component framework (Signal Sources, Sentiment Stack, Risk Board, Advocates, Actions) is a sensible way to slice sentiment tracking.
grep-friendly structure – The skill file is organized in a way that's easy to search and navigate.

The Big One: Missing Templates and Examples

Here's the thing: you mention templates but they don't actually exist. Your Templates section lists "Dashboard slide layout (KPI tiles + trend graphs + highlights/lowlights)" and "Escalation tracker" and "Advocate tracker," but users get nothing concrete to work with.

Why it matters: Without actual examples, users can't visualize what the output looks like or understand the exact shape of data they're building. That's a quick +8 point swing right there (hitting PDA layering, reference depth, and utility all at once).

The fix: Create reference files—references/dashboard-template.md with an actual slide l...

Browse Category

More media Agentic Skills

Report Security Issue

Found a security vulnerability in this agent skill?