analyze-feedback
SkillSynthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.
Install
git clone https://github.com/amplitude/mcp-marketplace.git ~/.claude/skills/analyze-feedbackWhat is analyze-feedback?
Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.
What this can do
Capabilities declared in this component's own frontmatter — not inferred.
Inherit all session tools
Declares no tool restrictions — inherits every session tool
~62 tokens of context used while enabled, before you invoke anything
Trust
83/100 · Excellent2 factors scored below maximum
Documentation
README · ~2 min readAnalyze Feedback
Perform comprehensive feedback reviews, investigate specific feature requests, understand customer sentiment, then prepare concise but actionable voice-of-customer presentations
Instructions
Step 1: Understand Available Sources
Use Amplitude:get_feedback_sources to see which feedback channels are connected (surveys, support, app reviews, etc.).
Step 2: Get Themed Insights
Use Amplitude:get_feedback_insights with appropriate filters:
- Filter by types:
request,complaint,lovedFeature,bug,painPoint - Filter by date range for recent feedback
- Filter by source for channel-specific analysis
Reviews
Log in to leave a review.
No reviews yet — be the first.
Explore related
Other things in this space — across every part of the ecosystem, not just skills.
Skillssimilar to this one
All skills →ui-ux-pro-max-skill
An AI SKILL that provide design intelligence for building professional UI/UX multiple platforms
111.3K stars
impeccable
The design language that makes your AI harness better at design.
52.5K stars
obsidian-skills
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
43.6K stars
Plugins
All plugins →hookify
Easily create custom hooks to prevent unwanted behaviors by analyzing conversation patterns or from explicit instructions. Define rules via simple markdown files.
32.9K stars
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics.
32.9K stars
playground
Creates interactive HTML playgrounds — self-contained single-file explorers with visual controls, live preview, and prompt output with copy button. Includes templates for design playgrounds, data explorers, concept maps, and document critique.
32.9K stars
Commands
All commands →modernize-extract-rules
Mine business logic from legacy code into testable, human-readable rule specifications
32.8K stars
create-plugin
Guided end-to-end plugin creation workflow with component design, implementation, and validation
32.8K stars
release-testing
Run automated UAT tests (UI or API) using a test profile on the AWS DevOps Agent
2.2K stars
MCP Servers
All mcp servers →Figma-Context-MCP
MCP server to provide Figma layout information to AI coding agents like Cursor
15.5K stars
notion-mcp-server
Official Notion MCP Server
4.6K stars
linear-mcp-server
A server that integrates Linear's project management system with the Model Context Protocol (MCP) to allow LLMs to interact with Linear.
347 stars
Subagents
All subagents →patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.
32.8K stars
code-architect
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences
32.8K stars
plugin-validator
Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples: <example> Context: User f
32.8K stars