daily-briefing

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

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, highly actionable with specific tool calls and parameters, and well-organized into clear sections. Its main gap is workflow clarity: the sequence is sound but lacks explicit validation/error-recovery checkpoints for failure cases like empty searches or missing transcripts.

Suggestions

Add explicit fallback/validation checkpoints, e.g. 'If search_youtube returns <5 relevant results, broaden region_code or expand the date range before proceeding.'

Specify handling for missing transcripts (step 4) so the workflow degrades gracefully rather than silently relying on titles.

Note the required parameter values up front (e.g. a country-code hint or how to derive the RFC 3339 cutoff) to remove ambiguity in step 1-2.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized into Objective, Execution Steps, and Next Actions; it assumes Claude's competence and does not pad with explanations of concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	It names exact tools and parameters (search_youtube with published_after, region_code, relevance_language; get_video_details; calculate_engagement_metrics; get_video_transcript) and concrete deliverable specs (2-sentence summaries, timestamped URLs), giving copy-paste-ready executable guidance for an instruction-only skill.	3 / 3
Workflow Clarity	The five steps are clearly sequenced and step 3 acts as a quality gate, but there are no explicit validation checkpoints or error-recovery feedback loops (e.g. what to do if search returns nothing or transcripts are unavailable), so checkpoints remain implicit.	2 / 3
Progressive Disclosure	This is a single under-50-line skill with no bundle files and no need for external references; the content is well-organized into clearly labeled sections, which per the rubric warrants a 3 for progressive disclosure.	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 is third-person, specific to a clear niche, and avoids fluff, but it stops short of listing multiple concrete actions and omits an explicit 'Use when...' trigger clause, leaving the 'when to use' question only implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks what happened in a place over a time period, or wants a news/event briefing for a location.'

Broaden trigger terms to natural phrasings users actually say ('what happened in', 'news briefing', 'today in', 'this week in').

Surface one or two more concrete actions (e.g. 'summarizes, ranks by engagement, and links primary video sources') to lift specificity toward a multi-action list.

Dimension	Reasoning	Score
Specificity	Names the domain ('briefing on events in a specific location and timeframe') and the action ('Provides a high-signal briefing') plus backing sources ('primary video sources and transcripts'), but does not enumerate multiple distinct concrete actions; it is one composite action rather than a list like 'extract, fill, merge'.	2 / 3
Completeness	It clearly states what the skill does, but the 'when' is only implied — there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Includes some relevant natural terms ('briefing', 'events', 'location', 'timeframe', 'video sources', 'transcripts') but lacks common user variations such as 'what happened in', 'news', 'today', or location names, and there is no explicit trigger clause.	2 / 3
Distinctiveness Conflict Risk	The niche is clear and narrow (a location-and-timeframe briefing backed by primary video sources and transcripts), giving it distinct triggers that are unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: google/adk-samples
Path: python/agents/youtube-analyst/youtube_analyst/skills/daily-briefing/SKILL.md
Commit: a862ebc

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

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.