Skill Introduction

Overview

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.

Core value

Turns reusable Development know-how into an installable skill, helping users complete github, community, agent-skill-repository, agent-skills work faster.

Target users

Developers, testers, and maintainers who handle Development tasks in Focus Code.
Teams that already trust workflows or content from phuryn.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

Tasks related to github, community, agent-skill-repository, agent-skills that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

Structured around Development, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, agent-skill-repository, agent-skills, so it can be filtered by concrete task intent.

Install and use

Install

Copy Install Command

focus install sentiment-analysis-4f5f97

View source

Detail Preview

SKILL.md

Primary filemarkdown4 KB

name: sentiment-analysis description: "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."

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)

Data Ingestion: Read all feedback sources and create a working inventory
Segment Identification: Identify at least 3 distinct user segments or personas from the feedback
Thematic Analysis: Extract recurring themes, pain points, and positive feedback per segment
Sentiment Scoring: Assign sentiment scores (-1 to +1) for overall satisfaction per segment
Impact Assessment: Prioritize insights by frequency, severity, and business impact
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

sentiment analysis