CtrlK
BlogDocsLog inGet started
Tessl Logo

analyzing-text-sentiment

Execute this skill enables AI assistant to analyze the sentiment of text data. it identifies the emotional tone expressed in text, classifying it as positive, negative, or neutral. use this skill when a user requests sentiment analysis, opinion mining, or emoti... Use when analyzing code or data. Trigger with phrases like 'analyze', 'review', or 'examine'.

42

Quality

43%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/ai-ml/sentiment-analysis-tool/skills/analyzing-text-sentiment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

20%

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

The body is a verbose conceptual overview with no executable guidance and no links to the actual bundled script or template, leaving Claude without concrete instructions despite the bundle containing the tools to do the work.

Suggestions

Replace the conceptual Overview/How It Works prose with a concrete quick-start example that invokes the bundled analyze_sentiment.py with real arguments and shows expected output.

Cut generic filler (Best Practices platitudes, Integration, Resources placeholders) that restates concepts Claude already knows.

Add clearly signaled references to the bundle, e.g., 'Report template: See assets/sentiment_analysis_report_template.md', and include a validate/review checkpoint for the analysis result.

DimensionReasoningScore

Conciseness

The body restates what sentiment analysis is ('Sentiment Analysis: The skill processes the text using a pre-trained sentiment analysis model') and pads sections like Overview, Best Practices, Integration, and Resources with content Claude already knows, wasting the token budget.

1 / 3

Actionability

There is no executable code, command, named library/model, or copy-paste guidance; the bundled analyze_sentiment.py script is never referenced, and steps merely describe ('The skill processes the text') rather than instruct.

1 / 3

Workflow Clarity

'How It Works' lists a 3-step sequence (Text Input, Sentiment Analysis, Result Output), but the steps are abstract with no validation checkpoints, no concrete commands, and no feedback loop for the analysis output.

2 / 3

Progressive Disclosure

Sections provide some structure, but the real bundle files (analyze_sentiment.py, sentiment_analysis_report_template.md) are never signaled from the body, and 'Resources' merely lists placeholders ('Project documentation', 'Related skills and commands') rather than clear one-level-deep references.

2 / 3

Total

6

/

12

Passed

Description

67%

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

The description covers both the capability and explicit usage triggers, but suffers from a conflicting off-domain trigger ('analyzing code or data'), a truncated phrase, and generic terms that invite collisions with other skills.

Suggestions

Remove or replace 'Use when analyzing code or data' with sentiment-specific triggers to avoid conflicting with code-analysis skills.

Complete the truncated 'emoti...' phrase and drop generic verbs like 'review'/'examine' that are not sentiment-specific.

Tighten to third person and list more concrete actions (e.g., scoring polarity, batch-classifying reviews, exporting labeled results) to reach full specificity.

DimensionReasoningScore

Specificity

It names the sentiment-analysis domain and concrete actions like 'identifies the emotional tone' and 'classifying it as positive, negative, or neutral', but stops short of listing multiple specific concrete actions as a score-3 anchor would.

2 / 3

Completeness

It explicitly answers what ('analyze the sentiment of text data... classifying it as positive, negative, or neutral') and when ('use this skill when a user requests sentiment analysis, opinion mining', 'Trigger with phrases like...'), satisfying both halves.

3 / 3

Trigger Term Quality

Natural terms appear ('sentiment analysis', 'opinion mining', 'analyze', 'review', 'examine'), but the trigger 'Use when analyzing code or data' is generic and off-domain, and 'emoti...' is truncated, leaving common variations missing or misleading.

2 / 3

Distinctiveness Conflict Risk

The phrase 'Use when analyzing code or data' and generic triggers like 'review' or 'examine' would cause overlap with many unrelated skills, so it is only somewhat specific and could trigger the wrong skill.

2 / 3

Total

9

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.