CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instruction-only skill with a concrete, sequenced analysis workflow and a detailed output specification. Its main gaps are minor: no worked example of the final deliverable, no explicit verification step, and light padding in the Purpose and persona lines.

DimensionReasoningScore

Conciseness

The body is lean with terse bullets and no explanations of concepts Claude already knows; the Purpose section duplicates the frontmatter description and the 'You are an expert user researcher' persona line is light padding that could be trimmed.

4 / 5

Actionability

Concrete, specific guidance throughout: 'at least 3 distinct user segments', 'sentiment scores (-1 to +1)', '2-3 highest-impact improvements per segment', and a full output template. It falls short of 5 only because no worked example of a finished segment profile is provided.

4 / 5

Workflow Clarity

Six numbered, named phases (Data Ingestion → Segment Identification → Thematic Analysis → Sentiment Scoring → Impact Assessment → Synthesis) give an explicit sequence, with implicit checkpoints like 'Flag segments with small sample sizes' and 'Ground all findings in actual user feedback'. No explicit verification step for findings keeps it below 5.

4 / 5

Progressive Disclosure

A single well-sectioned file with clear headers and a clearly signaled 'Further Reading' section; no bundle files exist to reference. The ~78-line body exceeds the short-skill threshold where a single file alone scores 5, and the ~35-line output template could be split into a reference file.

4 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly states concrete capabilities and multiple natural trigger conditions in third person. Its only weaknesses are incomplete coverage of the skill's outputs and minor trigger overlap with adjacent analytics/research skills.

DimensionReasoningScore

Specificity

'identify segments with sentiment scores, JTBD, and product satisfaction insights' lists several concrete actions in the feedback-analysis domain. Minor gaps in coverage (e.g., pain-point and recommendation outputs from the body are absent) keep it below the comprehensive 5 anchor.

4 / 5

Completeness

It clearly answers both what ('Analyze user feedback data to identify segments with sentiment scores, JTBD, and product satisfaction insights') and when ('Use when analyzing user feedback at scale, running sentiment analysis on reviews or surveys, or identifying satisfaction patterns') with concrete trigger phrases, matching the anchor-5 example structure. The when-clause is already explicit and specific, so 4 does not fit.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: 'user feedback at scale', 'sentiment analysis on reviews or surveys', 'satisfaction patterns'. A few natural terms are missing (NPS, customer feedback, complaint analysis), which matches the good-but-not-comprehensive 4 anchor rather than 5.

4 / 5

Distinctiveness Conflict Risk

'sentiment analysis', 'JTBD', and 'reviews or surveys' define a distinct PM/user-research niche. Broader triggers like 'satisfaction patterns' and 'user feedback' create minor overlap risk with generic data-analysis or market-research skills, placing it at mostly-distinct (4) rather than minimal-conflict (5).

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phuryn/pm-skills

Path

pm-market-research/skills/sentiment-analysis/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.