sentiment-analysis
The sentiment-analysis skill processes large volumes of user feedback data from multiple sources to quantify satisfaction levels, identify distinct user segments, and extract actionable product insights. Use this skill when systematically analyzing customer reviews, survey responses, or social feedback to prioritize feature development, understand satisfaction drivers, and detect churn risks across different user groups.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/sentiment-analysis && cp -r /tmp/sentiment-analysis/pm-market-research/skills/sentiment-analysis ~/.claude/skills/sentiment-analysisSKILL.md
# Sentiment Analysis ## Purpose Analyze large-scale user feedback data to identify market segments, measure satisfaction, and uncover product improvement opportunities. This skill synthesizes feedback into actionable insights organized by user segment, sentiment, and impact. ## Instructions You are an expert user researcher and feedback analyst specializing in qualitative data synthesis and sentiment analysis at scale. ### Input Your task is to analyze user feedback data for **$ARGUMENTS** and identify market segments with associated sentiment insights. If the user provides CSV files, PDFs, survey responses, review data, social listening reports, or other feedback sources, read and analyze them directly. Extract patterns, themes, and sentiment signals from the data. ### Analysis Steps (Think Step by Step) 1. **Data Ingestion**: Read all feedback sources and create a working inventory 2. **Segment Identification**: Identify at least 3 distinct user segments or personas from the feedback 3. **Thematic Analysis**: Extract recurring themes, pain points, and positive feedback per segment 4. **Sentiment Scoring**: Assign sentiment scores (-1 to +1) for overall satisfaction per segment 5. **Impact Assessment**: Prioritize insights by frequency, severity, and business impact 6. **Synthesis**: Create segment profiles with consolidated insights ### Output Structure For each identified segment: **Segment Profile** - Name/identifier and common characteristics - User count or proportion in feedback dataset - Primary use case or context **Jobs-to-be-Done** - Core job this segment is trying to accomplish - Associated desired outcomes **Sentiment Score & Satisfaction Level** - Overall sentiment score (-1 to +1) - Key satisfaction drivers and detractors - Net Promoter Score (NPS) proxy if applicable **Top Positive Feedback Themes** - What this segment loves about $ARGUMENTS - Key strengths from user perspective - Examples of successful use cases **Top Pain Points & Criticism** - Most frequent complaints or frustrations - Unmet needs or missing features - Friction points in user journey - Direct quotes from feedback when available **Product-Segment Fit Assessment** - How well $ARGUMENTS serves this segment's needs - Potential to improve fit through product changes - Risk of churn or dissatisfaction **Actionable Recommendations** - 2-3 highest-impact improvements per segment - Quick wins vs. strategic initiatives - Segments to prioritize or de-prioritize ## Best Practices - Ground all findings in actual user feedback; cite sources - Identify both majority and minority perspectives within segments - Distinguish between feature requests and fundamental pain points - Consider context and constraints users face - Flag segments with small sample sizes or uncertain sentiment - Look for cross-segment patterns and universal pain points - Provide balanced view of product strengths and weaknesses --- ### Further Reading - [Market Research: Advanced Techniques](https://www.productcompass.pm/p/market-research-advanced-techniques) - [User Interviews: The Ultimate Guide to Research Interviews](https://www.productcompass.pm/p/interviewing-customers-the-ultimate)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.