community-pulse
Scannednpx machina-cli add skill fusengine/agents/community-pulse --openclawFiles (1)
SKILL.md
1.5 KB
Community Pulse Skill
Overview
Gathers and analyzes community feedback about Claude Code using Exa search tools.
Modes
- Quick (default): Exa web_search for recent mentions
- Deep (--deep): Exa deep_researcher for comprehensive analysis
Search Categories
| Category | Exa Query | Priority |
|---|---|---|
| Updates | "Claude Code" release OR update 2026 | HIGH |
| Bugs | "Claude Code" bug OR issue OR broken | HIGH |
| Plugins | "Claude Code" plugin OR hooks experience | MEDIUM |
| Comparison | "Claude Code" vs Cursor OR Windsurf | LOW |
| Tips | "Claude Code" tips OR workflow OR best practices | MEDIUM |
Workflow
- Search using category-specific Exa queries
- Filter for recent results (last 30 days)
- Analyze sentiment (positive/neutral/negative)
- Extract actionable insights
- Report with sources and recommendations
Sentiment Classification
| Signal | Classification |
|---|---|
| "love", "amazing", "game changer" | Positive |
| "update", "released", "changed" | Neutral |
| "broken", "bug", "regression", "worse" | Negative |
References
Source
git clone https://github.com/fusengine/agents/blob/main/plugins/changelog-watcher/skills/community-pulse/SKILL.mdView on GitHub Overview
Gathers and analyzes community feedback about Claude Code from blogs, forums, and social media using Exa search tools. It surfaces sentiment, real-world usage patterns, bug reports, and feature requests to inform product decisions and prioritization.
How This Skill Works
The skill runs category-specific Exa queries (Updates, Bugs, Plugins, Comparison, Tips), then filters results to the last 30 days, analyzes sentiment (positive/neutral/negative), extracts actionable insights, and reports with sources and recommendations. Quick uses Exa web_search for recent mentions; Deep uses Exa deep_researcher for a comprehensive analysis.
When to Use It
- After a new Claude Code release to gauge overall reception and identify immediate concerns
- When bug reports or negative feedback surge on blogs, forums, or social media
- To evaluate plugin experiences and integration issues raised by users
- To compare Claude Code with rivals (Cursor or Windsurf) and note strengths/weaknesses
- To collect user tips, workflows, and best practices for future improvements
Quick Start
- Step 1: Run Quick search using Updates, Bugs, Plugins queries to capture recent mentions
- Step 2: Filter results to last 30 days and run sentiment analysis
- Step 3: Generate a Pulse Report with sources and recommended actions
Best Practices
- Use Quick for rapid sentiment snapshots and Deep for thorough analysis
- Filter results to the last 30 days to reflect current feedback
- Tag insights by category (Updates, Bugs, Plugins, Tips) and sentiment
- Cross-check findings against official release notes and changelogs
- Generate reports with clear sources and concrete recommendations for engineers
Example Use Cases
- Detected a spike in negative sentiment about a plugin during a recent release cycle
- Identified common bug reports and their preferred workarounds from forums
- Uncovered user workflow tips that improved Claude Code integration with existing tooling
- Compared Claude Code vs Cursor, revealing neutral to positive sentiment with notable feature gaps
- Produced a pulse report highlighting action items for QA and product teams
Frequently Asked Questions
Add this skill to your agents
