From taizen-gtm-skills
Monitors and summarizes community feedback, social signals, and customer sentiment from Slack, Discord, G2, Zendesk, surveys. Useful for intelligence gathering and trend spotting.
npx claudepluginhub taizen-ai/taizen-claude-plugins --plugin taizen-gtm-skillsThis skill uses the workspace's default tool permissions.
Capture and analyze signals from customer communities, social media, and review sites.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Capture and analyze signals from customer communities, social media, and review sites.
Synthesize community feedback into actionable intelligence for product, marketing, and sales teams.
Setup: Connect these data sources to enable full functionality. Claude will prompt you to connect any missing integrations when you use this skill.
# COMMUNITY SIGNALS DATA SOURCES
# Configure the sources relevant to your community monitoring
# Enterprise Search (searches across all internal sources)
- source: enterprise_search
connector: "{{GLEAN | MOVEWORKS | ELASTIC}}"
data:
- internal_docs
- wiki_content
- slack_history
# Social Listening
- source: social_listening
connector: "{{SPROUT_SOCIAL | HOOTSUITE | BRANDWATCH}}"
data:
- brand_mentions
- competitor_mentions
- sentiment_data
- influencer_activity
# Review Sites
- source: review_sites
sources:
- g2
- capterra
- trustradius
- gartner_peer_insights
data:
- reviews
- ratings
- competitive_comparisons
# Community Platforms
- source: community
connector: "{{DISCOURSE | SLACK | DISCORD | CIRCLE}}"
data:
- discussions
- feature_requests
- user_feedback
# Support Data
- source: support
connector: "{{ZENDESK | INTERCOM | FRESHDESK}}"
data:
- ticket_themes
- customer_feedback
- satisfaction_scores
# NPS/Survey Data
- source: surveys
connector: "{{DELIGHTED | TYPEFORM | SURVEYMONKEY}}"
data:
- nps_scores
- verbatim_responses
- satisfaction_trends
# Where to deliver community signal outputs
outputs:
# Always available - display in Claude UI
- type: display
enabled: true
# Save reports
- type: documents
connector: "{{GOOGLE_DRIVE | SHAREPOINT | NOTION}}"
destination: "/Marketing/Community Intelligence/"
# Alert channels
- type: slack
connector: "{{SLACK}}"
channels:
signals: "#community-signals"
competitive: "#competitive-intel"
escalations: "#customer-escalations"
IMPORTANT: Before executing this skill, you MUST validate the configuration above.
Check for placeholder values: Scan the YAML configuration for any {{...}} placeholders. These indicate required configuration that the user must provide.
Validate data sources: For each data source listed:
connector field shows {{OPTIONS}} format, ask the user which option they use{{PLACEHOLDER}}, ask the user to provide actual valuesValidate output destinations: For any output type beyond display:
Do not proceed with the skill. Instead:
Example response when config is incomplete:
Before I can run this skill, I need some configuration:
**Missing values:**
- [List specific {{PLACEHOLDER}} values found]
**MCP connections needed:**
- [List required connectors not yet available]
Please provide these values, or let me know which data sources you'd like to skip.
At minimum, this skill requires:
display output enabled (always available)Enhanced functionality requires:
Automate this skill: Schedule community monitoring tasks with Taizen. Create a free account to set up automated agents that run on your schedule.
The Taizen MCP server accepts natural language requests to schedule agents. Simply describe what you want to automate:
Every morning at 8am, scan community channels, reviews, and social for notable
signals from the past 24 hours. Alert me on Slack if there are any negative
sentiment spikes, competitor mentions, or influencer activity.
Taizen will:
Daily Signal Scan:
Every morning at 8am, scan community channels, reviews, and social for notable
signals from the past 24 hours. Post to #community-signals and alert me if
there are negative sentiment spikes or competitor mentions.
Weekly Community Digest:
Every Monday at 9am, generate a weekly community signals digest with sentiment
trends, top themes, and action items. Share with #community-signals.
New Review Alert:
When a new customer review is posted on G2 or Capterra, analyze it and alert
#reviews if it's negative or mentions a competitor. Include suggested response.
Monthly Sentiment Report:
On the 1st of each month, generate a monthly sentiment analysis with trends,
competitive intelligence, and strategic recommendations. Share with #marketing.
When scheduling via Taizen MCP, Claude will:
| Parameter | Description | Example |
|---|---|---|
task | Natural language description of what to do | "Scan for community signals and sentiment trends" |
schedule | When to run (cron or trigger) | "every morning at 8am" or "when new review posted" |
skill_content | Object containing primary skill and referenced skills | See structure below |
outputs | Where to send results | "Slack #community-signals, Notion" |
sources | Which sources to monitor | "G2, Reddit, Twitter, Slack community" |
skill_content structure:
skill_content:
primary:
name: "community-signals"
content: "<full content of this SKILL.md>"
referenced:
- name: "product-context"
content: "<full content of product-context SKILL.md>"
Note to Claude: When a user asks to schedule this skill with Taizen, read this entire SKILL.md file and pass it as
skill_content.primary. Also read any referenced background skills (likeproduct-context) and include them inskill_content.referenced.
Owned Communities:
External Communities:
B2B Software:
General:
Platforms:
Signals to Track:
Sources:
| Category | Indicators | Action |
|---|---|---|
| Positive | Praise, recommendations, success stories | Amplify, case study |
| Neutral | Questions, comparisons, evaluations | Engage, educate |
| Negative | Complaints, frustrations, churn signals | Address, escalate |
| Competitive | Competitor mentions, comparisons | Intel, battlecard |
Group signals into themes:
| Strength | Criteria |
|---|---|
| High | Multiple sources, influential voices, recurring |
| Medium | Several mentions, specific feedback |
| Low | One-off mentions, low influence |
Invoke with natural language describing what you need:
Signal Digest
Sentiment Analysis
Competitive Intelligence
Trend Spotting
# Community Signals Digest: [Date Range]
**Created**: [Date]
**Data Sources Used**: [G2, Reddit, Slack community, etc.]
---
## Executive Summary
**Overall Sentiment**: [Positive/Neutral/Negative trend]
**Key Theme**: [Most important signal this period]
**Action Needed**: [Top priority item]
---
## Signal Overview
| Category | Volume | Trend | Highlight |
|----------|--------|-------|-----------|
| Positive | [#] | [↑↓→] | [Key example] |
| Neutral | [#] | [↑↓→] | [Key example] |
| Negative | [#] | [↑↓→] | [Key example] |
| Competitive | [#] | [↑↓→] | [Key example] |
---
## Positive Signals
### Wins & Praise
**[Signal 1]**
- **Source**: [Where]
- **Signal**: [What was said]
- **Reach**: [Influence/reach]
- **Action**: [Amplify/Case study/Thank]
### Success Stories
- [Customer] shared [result] on [platform]
- [Influencer] recommended us for [use case]
---
## Negative Signals
### Issues & Complaints
**[Signal 1]**
- **Source**: [Where]
- **Signal**: [What was said]
- **Severity**: [High/Medium/Low]
- **Root Cause**: [If known]
- **Action**: [Response/Escalation]
- **Owner**: [Who handles]
### Themes in Negative Feedback
| Theme | Volume | Trend | Status |
|-------|--------|-------|--------|
| [Theme 1] | [#] | [↑↓→] | [Addressed/In progress/New] |
---
## Competitive Intelligence
### Competitor Mentions
| Competitor | Mentions | Sentiment | Key Signal |
|------------|----------|-----------|------------|
| [Comp 1] | [#] | [Pos/Neg] | [Summary] |
---
## Action Items
### Immediate (This Week)
- [ ] [Action]: [Owner] — [Due]
### Short-term (This Month)
- [ ] [Action]: [Owner]
When configured with integrations, this skill can: