CtrlK
BlogDocsLog inGet started
Tessl Logo

debate-synthesizer

Extracts the strongest arguments from heated YouTube comment threads, identifying key battlegrounds and community consensus.

62

Quality

72%

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/debate-synthesizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The body is concise and highly actionable, with specific tool calls and thresholds driving a clear six-step workflow. Its main gap is the absence of any verification step confirming the synthesized debate brief is accurate before delivery.

Suggestions

Add a validation checkpoint before the Deliver step, e.g. confirm each Pro/Con argument traces back to a specific reply and that no side is underrepresented.

Specify how to handle edge cases such as no high-reply comments being found or a thread where one side has no substantive arguments, to make the workflow more robust.

DimensionReasoningScore

Conciseness

The body is lean and action-oriented with no exposition of concepts Claude already knows; every section (Objective, Execution Steps, HTML Publishing Rule, Next Actions) earns its place.

3 / 3

Actionability

It names concrete tools with parameters (search_youtube, get_video_comments with order="relevance", get_comment_replies(comment_id), get_video_details, publish_file) and specific thresholds ("top 1 or 2 videos," "2 or 3 comments," "top 3 strongest arguments"), giving copy-ready executable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

The six steps are clearly sequenced, but the batch fetch-and-synthesize flow has no validation or verification checkpoint to confirm the debate was correctly identified or the arguments faithfully grouped, which caps workflow clarity at 2.

2 / 3

Progressive Disclosure

At roughly 20 lines with no need for external references, the well-organized sections (Objective, Execution Steps, HTML Publishing Rule, Next Actions) satisfy the simple-skill allowance for a top progressive-disclosure score.

3 / 3

Total

11

/

12

Passed

Description

57%

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 clearly conveys a distinctive niche and what the skill does, but it omits an explicit "Use when..." trigger clause and relies on somewhat abstract action language. Adding natural trigger terms would lift completeness and trigger-term quality.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when the user wants a summary of arguments in a YouTube comment debate or mentions controversy in a video's comments."

Replace abstract phrases like "key battlegrounds" and "community consensus" with concrete terms a user would actually say, such as "top replies," "both sides," and "points of disagreement."

List the concrete actions performed (fetch top comments, pull replies, group into Pro/Con) to raise specificity toward the multi-action anchor.

DimensionReasoningScore

Specificity

Names actions like "Extracts the strongest arguments" and "identifying key battlegrounds and community consensus," but these are abstract rather than a comprehensive list of multiple concrete actions, so it sits below the multi-action anchor of 3.

2 / 3

Completeness

It clearly states what the skill does but lacks any "Use when..." or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

"YouTube comment threads" and "arguments" are relevant terms a user might say, but common variations like "comments," "debate," or "controversy" are missing and "battlegrounds"/"community consensus" lean toward jargon.

2 / 3

Distinctiveness Conflict Risk

The YouTube comment debate niche is specific and clearly distinguishable, making it unlikely to trigger for the wrong skill, matching the clear-niche anchor.

3 / 3

Total

9

/

12

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.