CtrlK
BlogDocsLog inGet started
Tessl Logo

sentiment-analysis

Extracts the true audience mood and key feedback by analyzing comment sentiment and keyword frequency.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./python/agents/youtube-analyst/youtube_analyst/skills/sentiment-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

The content is a lean, well-structured three-step workflow with concrete tool references and clear sequencing. Its main gap is the absence of executable code examples and explicit validation/edge-case handling.

Suggestions

Add a short example showing the exact invocation format for `get_video_comments` and `analyze_sentiment_heuristic` so guidance is copy-paste ready.

Include a validation checkpoint in the Analyze step (e.g., if fewer than ~20 comments are returned, fetch more or note low confidence).

Specify how to weight semantic understanding versus the heuristic when they disagree, to remove ambiguity in the Analyze step.

DimensionReasoningScore

Conciseness

Lean and efficient at under 20 lines with no over-explanation of concepts Claude already knows; every line carries actionable guidance. Minor editorial phrasing ('true audience reaction') is negligible.

5 / 5

Actionability

Names concrete tools (`get_video_comments`, `analyze_sentiment_heuristic`) with specific parameters ('top 20-50 comments', 'Positive/Neutral/Negative'); not 5 because tool calls are described rather than shown as executable code examples.

4 / 5

Workflow Clarity

A clear three-step sequence (Fetch, Analyze, Synthesize) with concrete per-step instructions; not 5 because there are no explicit validation checkpoints or edge-case handling (e.g., too few comments fetched).

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and no bundle files present; the body is well-organized into Objective, Execution Steps, and Next Actions sections, satisfying the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

66%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.

The description is specific and reasonably distinctive, naming concrete analysis actions and natural keywords, but it lacks an explicit 'Use when...' trigger clause, which caps completeness. Adding a trigger phrase would lift it into the top band.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user wants to gauge audience reaction to a video, product, or creator from comments.'

Replace the slightly abstract 'true audience mood' with concrete outputs (e.g. 'overall sentiment label and top recurring themes').

Add natural synonyms like 'tone' or 'audience reaction' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the sentiment-analysis domain and several concrete actions ('analyzing comment sentiment', 'keyword frequency', 'extracts...mood and key feedback'); falls short of 5 because 'true audience mood' is mildly abstract and coverage is not comprehensive.

4 / 5

Completeness

Has a clear 'what' (extract mood/feedback via sentiment and keyword-frequency analysis) but no explicit 'Use when...' trigger clause, so per the guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural user terms ('sentiment', 'comment', 'mood', 'feedback', 'keyword frequency') but is missing common synonyms like 'audience reaction' or 'tone'; not 3 because keyword coverage is genuinely good.

4 / 5

Distinctiveness Conflict Risk

Targets a clear comment-sentiment niche with distinct triggers and only minor overlap risk with general data-analysis skills; not 5 because the description omits the video/social context that would fully bound it.

4 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
google/adk-samples
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.