sentiment-analysis
Analyze user feedback data to identify segments with sentiment scores, JTBD, and product satisfaction insights. Use when analyzing user feedback at scale, running sentiment analysis on reviews or surveys, or identifying satisfaction patterns.
What this skill does
# 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)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.