CtrlK
BlogDocsLog inGet started
Tessl Logo

poi-discovery-briefing

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

60

Quality

70%

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

Quality

Content

72%

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

The content is concise, well-structured, and actionable for most steps, naming concrete tools throughout. Its weaknesses are the abstract HTML-synthesis step and the absence of a validation checkpoint before publishing the final report.

Suggestions

Add an explicit validation step before delivery, e.g. preview/verify the HTML renders and that timestamp links resolve before calling publish_file.

Provide a concrete HTML template or structure for the BD Briefing so the synthesis step is copy-paste ready rather than abstract.

Clarify how to derive 'Audience Sentiment' from comments (e.g. classify positive/negative mentions) so that step is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean — a short objective followed by numbered steps that name specific tools (search_youtube, get_video_transcript, generate_timestamp_url, publish_file) with minimal conceptual padding, matching the score-3 anchor for efficient content where every token earns its place.

3 / 3

Actionability

Provides concrete tool calls and output specifics (timestamp <a href> links, publish_file with explicit filename) but the HTML synthesis step is left abstract ('format this data into a professional HTML document') with no template, matching the score-2 anchor of some concrete guidance that is incomplete.

2 / 3

Workflow Clarity

A clear 6-step numbered sequence exists, but the workflow publishes the HTML to the cloud with no validation checkpoint before delivery; per the guidelines, missing validation for a publish/batch operation caps workflow clarity at 2.

2 / 3

Progressive Disclosure

No bundle files exist and the skill is under 50 lines, single-purpose, and well-organized into an Objective plus numbered Execution Steps, so per the scoring notes a simple skill with well-organized sections scores 3.

3 / 3

Total

10

/

12

Passed

Description

67%

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 well-differentiated, clearly naming concrete actions and a distinct niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause and limited coverage of natural user phrasings.

Suggestions

Add an explicit trigger clause, e.g. 'Use when preparing business-development briefings on local activities around a point of interest from travel vlogs.'

Include natural user phrasings such as 'things to do near [POI]', 'travel vlog recommendations', or 'POI activity report' to improve trigger-term coverage.

Consider naming the primary tool surface (e.g. YouTube vlog analysis) so the description signals its scope more concretely.

DimensionReasoningScore

Specificity

Quotes multiple concrete actions — 'Extracts specific local activity recommendations', 'sentiment from travel vlogs', 'into a shareable HTML BD report' — matching the score-3 anchor for listing several specific actions rather than just naming a domain.

3 / 3

Completeness

Clearly states what it does but omits any 'Use when...' trigger guidance, so per the judging guidelines completeness is capped at 2 for missing explicit when-to-use guidance.

2 / 3

Trigger Term Quality

Contains relevant natural keywords ('travel vlogs', 'activity recommendations', 'sentiment') but lacks common variations a user would actually say ('things to do', 'POI', 'business development'), matching the score-2 anchor of some relevant keywords missing common variations.

2 / 3

Distinctiveness Conflict Risk

Targets a narrow niche (travel-vlog POI briefing for BD teams) with distinctive triggers, unlikely to conflict with other skills, matching the score-3 anchor for a clear niche.

3 / 3

Total

10

/

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.