# Community Signals

> Monitors and summarizes community feedback, social signals, and customer sentiment. Use for intelligence gathering and trend spotting.

- **Type:** Skill
- **Install:** `agentstack add skill-taizen-ai-taizen-claude-plugins-community-signals`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [taizen-ai](https://agentstack.voostack.com/s/taizen-ai)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [taizen-ai](https://github.com/taizen-ai)
- **Source:** https://github.com/taizen-ai/taizen-claude-plugins/tree/main/plugins/taizen-gtm-skills/skills/community-signals
- **Website:** https://usetaizen.com/

## Install

```sh
agentstack add skill-taizen-ai-taizen-claude-plugins-community-signals
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Community Signals Skill

Capture and analyze signals from customer communities, social media, and review sites.

## Purpose

Synthesize community feedback into actionable intelligence for product, marketing, and sales teams.

---

## Required Integrations

> **Setup**: Connect these data sources to enable full functionality. Claude will prompt you to connect any missing integrations when you use this skill.

### Data Sources

```yaml
# 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
```

### Output Destinations

```yaml
# 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"
```
---

## Instructions for Claude

> **IMPORTANT**: Before executing this skill, you MUST validate the configuration above.

### Pre-Execution Checklist

1. **Check for placeholder values**: Scan the YAML configuration for any `{{...}}` placeholders. These indicate required configuration that the user must provide.

2. **Check Taizen first**: If `taizen` MCP is connected, call `list_datasources` to see what data is indexed. You can then use `run_agent` to query all indexed sources in natural language — this replaces the need for most individual MCP connections below. Skip directly to running the skill.

3. **Validate data sources**: For each data source listed:
   - If a `connector` field shows `{{OPTIONS}}` format, ask the user which option they use
   - If URLs, paths, or names contain `{{PLACEHOLDER}}`, ask the user to provide actual values
   - Verify any required MCP servers are connected and available

4. **Validate output destinations**: For any output type beyond `display`:
   - Confirm the connector is available as an MCP server
   - Ensure destination paths/channels are configured (not placeholders)

### If Configuration is Incomplete

**Do not proceed with the skill.** Instead:

1. List the specific missing or placeholder values found
2. Explain what each value is needed for
3. Ask the user to provide the missing configuration
4. Offer to help them set up the required MCP integrations

**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.
```

### Minimum Requirements

At minimum, this skill requires:
- Brand/product name to monitor
- `display` output enabled (always available)
- Web search provides public social mentions without additional setup

Enhanced functionality requires:
- Social listening platform connection
- Community platform access (Discord, Slack communities)
- Review site integrations (G2, Capterra)
- Reddit/Twitter API access for deeper analysis

---

## Using Taizen

> **Connect once, access everything.** Instead of configuring 15+ individual MCP connectors, connect Taizen MCP once — your whole team gets access to all connected MCPs and indexed data sources (Gong calls, CRM, documents, and more) without any per-tool setup.

### Instant Queries (Run Now)

If `taizen` MCP is connected, call `run_agent` to pull from your indexed data right in this conversation:

**Surface community trends**
```
"Search my indexed community channels and social data for conversations about AI automation in sales from the past 30 days. Identify themes, questions, and sentiment."
```

**Topic monitoring**
```
"Pull recent community discussions mentioning our product or key competitors from indexed sources. Summarize the top topics and sentiment."
```

### Scheduled Agents (Automate It)

To run this skill automatically on a schedule, call `run_agent` and describe the automation in natural language — Taizen creates and manages the recurring agent:

**Weekly community digest**
```
"Every Monday, summarize community discussions from the past week, flag emerging trends, and surface top questions to #community-team on Slack."
```

**Monthly signal report**
```
"Monthly, generate a community signals report covering trending topics, sentiment shifts, and feature requests from all indexed community sources. Share to #product."
```

Taizen creates the agent, runs it on your schedule, and delivers results to your configured destinations (Slack, CRM, docs, email).

### Setup

1. Sign up at [usetaizen.com](https://usetaizen.com) and connect your data sources — every teammate gets access immediately
2. Add Taizen MCP to Claude: `https://us.mcp.usetaizen.com/mcp` (or `https://eu.mcp.usetaizen.com/mcp` for EU data residency)
3. Use `run_agent` for instant queries or to schedule recurring agents — Taizen handles routing to the right sources
## Signal Sources

### 1. Community Channels

**Owned Communities**:
- Customer Slack/Discord
- Community forums
- User groups
- Customer advisory boards

**External Communities**:
- Reddit (relevant subreddits)
- LinkedIn groups
- Industry forums
- Stack Overflow
- GitHub discussions

### 2. Review Sites

**B2B Software**:
- G2
- Capterra
- TrustRadius
- Gartner Peer Insights
- Software Advice

**General**:
- Trustpilot
- BBB
- Industry-specific sites

### 3. Social Media

**Platforms**:
- LinkedIn (company, executives)
- Twitter/X
- YouTube comments
- Industry podcasts

**Signals to Track**:
- Brand mentions
- Competitor mentions
- Industry trends
- Influencer opinions
- Customer sentiment

### 4. Support & Feedback

**Sources**:
- Support tickets
- Feature requests
- NPS verbatims
- Survey responses
- Sales call notes

---

## Analysis Framework

### Sentiment Categories

| 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 |

### Theme Clustering

Group signals into themes:
- Product features/gaps
- Customer experience
- Pricing/value
- Competitive positioning
- Market trends

### Signal Strength

| Strength | Criteria |
|----------|----------|
| **High** | Multiple sources, influential voices, recurring |
| **Medium** | Several mentions, specific feedback |
| **Low** | One-off mentions, low influence |

---

## How to Use This Skill

Invoke with natural language describing what you need:

**Signal Digest**
- "Generate this week's community signals digest"
- "What are people saying about us on G2?"
- "Summarize Reddit discussions about our category"

**Sentiment Analysis**
- "Analyze sentiment around our latest feature launch"
- "What's the sentiment trend over the past month?"

**Competitive Intelligence**
- "What are people saying about Competitor X?"
- "How are we being compared to competitors on review sites?"

**Trend Spotting**
- "What emerging topics are trending in our community?"
- "Identify new pain points customers are discussing"

---

## Output Format

### Weekly Signal Digest

```markdown
# 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]
```

---

## Automation Options

When configured with integrations, this skill can:

1. **Real-time alerts** - Notify on negative reviews, competitor mentions, or sentiment spikes
2. **Automated digests** - Generate daily/weekly signal summaries
3. **Review response** - Draft responses to customer reviews
4. **Trend tracking** - Monitor sentiment trends over time
5. **Competitive alerts** - Flag competitive intelligence for battlecard updates

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [taizen-ai](https://github.com/taizen-ai)
- **Source:** [taizen-ai/taizen-claude-plugins](https://github.com/taizen-ai/taizen-claude-plugins)
- **License:** MIT
- **Homepage:** https://usetaizen.com/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-taizen-ai-taizen-claude-plugins-community-signals
- Seller: https://agentstack.voostack.com/s/taizen-ai
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.