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'.

37

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

12%

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

The body is verbose filler that explains concepts Claude already knows and provides no executable guidance, while entirely failing to reference the bundled analysis script and report template that would make the skill actionable. It reads as a template-generated placeholder rather than operational instructions.

Suggestions

Cut the filler sections (Overview prose, generic Instructions, Output, Resources) and replace them with a concise workflow that invokes scripts/analyze_sentiment.py with concrete example commands.

Reference the bundled materials explicitly, e.g., "See [scripts/analyze_sentiment.py](scripts/analyze_sentiment.py) for the analysis implementation" and "Use [assets/sentiment_analysis_report_template.md](assets/sentiment_analysis_report_template.md) to format results".

Add a concrete worked example with real input text, the exact command to run, and the expected sentiment score/classification output, plus a validation step for edge cases like sarcasm or mixed sentiment.

DimensionReasoningScore

Conciseness

The body explains sentiment-analysis concepts Claude already knows ("empowers Claude to perform sentiment analysis... providing insights into the emotional content and polarity", "By leveraging AI/ML techniques") and is padded with filler sections like "The skill produces structured output relevant to the task" and "Project documentation", matching the score-1 anchor for verbosity and unnecessary context.

1 / 3

Actionability

There is no executable code or concrete command anywhere in the body; it only describes ("processes the text using a pre-trained sentiment analysis model") and gives abstract instructions ("Provide necessary context and parameters", "Apply modifications as needed"), matching the score-1 anchor of describing rather than instructing with no concrete guidance.

1 / 3

Workflow Clarity

It lists a sequenced 3-stage process (Text Input → Sentiment Analysis → Result Output), but these are conceptual stages rather than an operational workflow and there are no validation checkpoints or feedback loops, matching the score-2 anchor of steps present with missing checkpoints.

2 / 3

Progressive Disclosure

Despite bundled files existing (scripts/analyze_sentiment.py, assets/sentiment_analysis_report_template.md), the body never references any of them and instead presents a monolithic wall of generic filler sections with no navigation to the real materials, matching the score-1 anchor.

1 / 3

Total

5

/

12

Passed

Description

60%

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 what the skill does and includes an explicit trigger clause, but it is grammatically broken ("Execute this skill enables...", truncated "emoti..."), uses third-person-inconsistent voice, and leans on generic verbs plus a misleading "analyzing code or data" clause that creates high conflict risk.

Suggestions

Rewrite in clean third person (e.g., "Analyzes the sentiment of text and classifies it as positive, negative, or neutral") and remove the broken "Execute this skill enables" / "emoti..." fragments.

Replace the generic triggers ("analyze", "review", "examine") and the misleading "Use when analyzing code or data" with sentiment-specific triggers such as "Use when a user asks to analyze sentiment, determine the tone of text, or mine opinions from reviews, posts, or survey responses."

Add natural keyword variations users would actually say (e.g., "tone", "emotion", "positive/negative") to improve trigger coverage.

DimensionReasoningScore

Specificity

It names the domain and concrete actions ("analyze the sentiment of text data", "classifying it as positive, negative, or neutral", "opinion mining"), but describes essentially one classification capability rather than multiple distinct concrete actions, matching the score-2 anchor of naming a domain and some actions without being comprehensive.

2 / 3

Completeness

It explicitly answers both 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"), with an explicit "Use when..." trigger clause present, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

It includes relevant natural keywords ("sentiment analysis", "opinion mining"), but the trigger phrases ("analyze", "review", "examine") are overly generic and "analyzing code or data" is misdirected, so coverage is partial and missing natural variations like "tone" or "is this positive/negative".

2 / 3

Distinctiveness Conflict Risk

The triggers "analyze", "review", "examine" and the clause "Use when analyzing code or data" are generic and actively misdirected for a sentiment skill, so it would conflict with many other skills (code review, data analysis, document review), matching the score-1 anchor.

1 / 3

Total

8

/

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.