CtrlK
BlogDocsLog inGet started
Tessl Logo

daily-briefing

Provides a high-signal briefing on events in a specific location and timeframe, backed by primary video sources and transcripts.

58

Quality

66%

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/daily-briefing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, well-sequenced instruction-only workflow with named tools, concrete parameters, and a built-in verification step, assuming Claude's competence throughout. The main gap is the absence of explicit error-recovery feedback loops for failure cases such as no search results or unavailable transcripts.

Suggestions

Add a short feedback loop for the most likely failure modes, e.g. 'If search_youtube returns no relevant results, broaden the timeframe or relax region_code before reporting nothing found' and 'If a transcript is unavailable, fall back to get_video_details metadata rather than skipping the event.'

Optionally show the exact parameter shape for the key call (e.g. a one-line search_youtube invocation with published_after, region_code, relevance_language filled in) to push actionability from mostly-executable to copy-paste ready.

Trim emphasis padding ('CRITICAL', 'MUST aggressively') in favor of a single clear imperative per step to nudge conciseness toward 5.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (it never explains what YouTube, transcripts, or engagement metrics are), with only minor emphasis padding ('CRITICAL', 'MUST aggressively', 'Optional but Preferred') that could be trimmed, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Guidance names specific tools and parameters (search_youtube with published_after, region_code 'HK', relevance_language; get_video_transcript; calculate_engagement_metrics) plus concrete counts (top 2-3 clips, 3-5 events, 2-sentence summaries), which is mostly executable; it stops short of anchor 5 only because no literal command/code syntax is given.

4 / 5

Workflow Clarity

A clear numbered 1-5 sequence (Time Context, Locate, Filter & Rank, Ingest, Deliver) with a verification checkpoint in step 3 that discards spam/clickbait; the batch-processing validation cap at 3 does not apply because verification is present, but it lacks explicit feedback loops for edge cases like zero results or missing transcripts, so it stays at 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and has no external references, with well-organized sections (Objective, Execution Steps, Next Actions), meeting the simple-skill exception that lets progressive disclosure score 5 on well-organized sections alone.

5 / 5

Total

17

/

20

Passed

Description

53%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 clearly states what the skill does and occupies a distinct niche, but it lacks an explicit 'Use when...' trigger clause and offers only one concrete action, which cap both completeness and specificity. Trigger-term coverage is relevant but misses the natural phrasings a user would actually say.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user asks for a news briefing, a summary of what happened in a specific place and time, or a daily update on events in a location.'

List the concrete actions the skill performs (e.g. 'searches YouTube for recent location-specific videos, ranks them by engagement, ingests transcripts, and summarizes the top events') to lift specificity above a single action.

Include natural user synonyms such as 'news', 'update', 'what happened', and 'summary' alongside 'briefing' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('briefing on events in a specific location and timeframe') and one concrete action ('Provides a... briefing'), with 'backed by primary video sources and transcripts' describing sources rather than listing several distinct actions, so it lands at 'domain + 1-2 actions' rather than the multi-action anchor 4.

3 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3 ('clear what, when missing or weakly implied').

3 / 5

Trigger Term Quality

Relevant keywords like 'briefing' and 'events' are present and somewhat natural, but common user phrasings such as 'news', 'what happened in [place]', 'update', or 'summary' are missing, matching 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The location/timeframe/video-source framing carves a fairly distinct niche with only minor overlap risk against general news or YouTube-search skills, fitting 'mostly distinct; minor overlap risk' rather than the fully distinct anchor 5.

4 / 5

Total

13

/

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.