poi-discovery-briefing

Extracts specific local activity recommendations and sentiment from travel vlogs into a shareable HTML BD report.

Quality

68%

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/poi-discovery-briefing/SKILL.md

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 body is a tight, well-sequenced instruction-only workflow with concrete tool calls and a clear deliverable structure. Its main weaknesses are minor padding and the absence of validation/feedback steps (e.g., handling missing transcripts or confirming the published URL).

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but contains minor over-explanation that could be trimmed: 'Crucially,' in step 3, 'Travel vloggers often list 10+ activities in a single video', and 'to make it visually appealing' in step 5. This fits anchor 4 (efficient, minor instances of over-explanation) rather than anchor 5's every-token-earns-its-place.	4 / 5
Actionability	Concrete tool names with example queries ('Mount Fuji travel vlog'), explicit report fields, and a fully-parameterized 'publish_file(content=html_string, filename="poi_briefing.html")' call make the guidance mostly executable. It stops short of anchor 5 because argument formats for get_video_transcript, get_video_comments, and get_video_details are not shown, leaving minor gaps.	4 / 5
Workflow Clarity	The 6-step numbered sequence is clear and explicitly sequenced with a defined deliverable (HTML briefing with per-activity rows and a published URL). It is not a 5 because there are no explicit validation checkpoints or feedback loops — e.g., verifying the published URL or handling vlogs without transcripts.	4 / 5
Progressive Disclosure	The skill is under 50 lines, self-contained with no external references needed, and well-organized into a labeled Objective and numbered Execution Steps. Per the rubric's simple-skill guideline, this warrants a 5 with just well-organized sections.	5 / 5
	Total	17 / 20 Passed

Description

58%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 concrete and appropriately concise, clearly stating what the skill produces, but it omits any 'when to use' trigger guidance and lacks natural synonym coverage (YouTube, video, things to do, POI). Adding an explicit use-when clause would raise both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks about things to do near a destination, wants activity recommendations from YouTube travel vlogs, or needs a POI briefing for a BD team.'

Add natural synonyms users would actually say — 'YouTube videos', 'things to do', 'points of interest (POI)' — to improve trigger-term coverage.

Mention the timestamp-link deliverable briefly (e.g., 'with direct timestamp links to each recommendation') to close the specificity gap without adding length.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions — 'Extracts specific local activity recommendations', 'sentiment', 'into a shareable HTML BD report' — with only minor gaps in coverage (e.g., timestamp links and video sourcing are unstated). It goes beyond the 1-2 actions of anchor 3 but is not comprehensive enough for anchor 5.	4 / 5
Completeness	The 'what' is clear, but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline. It is not a 2 because the 'what' is specific and concrete, and not a 4 because 'when' is entirely absent rather than weakly implied.	3 / 5
Trigger Term Quality	Relevant keywords like 'travel vlogs', 'local activity recommendations', and 'sentiment' are present, but common natural variations users would say are missing ('YouTube', 'video', 'things to do', 'POI'). This matches anchor 3 (some relevant keywords, missing synonyms) rather than anchor 4's fuller coverage.	3 / 5
Distinctiveness Conflict Risk	The travel-vlog activity-analysis niche with a 'BD report' deliverable is mostly distinct with clear domain-specific triggers. It is not a 5 because 'recommendations' and 'sentiment' could mildly overlap with generic video- or review-analysis skills.	4 / 5
	Total	14 / 20 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/poi-discovery-briefing/SKILL.md
Commit: 2f902cb

Reviewed: 5 days 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.