CtrlK
BlogDocsLog inGet started
Tessl Logo

industry-landscape-briefing

Equips sellers with macro industry trends by analyzing trending data and specific analyst/competitor channels.

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/industry-landscape-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-structured execution playbook with concrete tool usage and a clear deliverable format. Its main gap is the absence of explicit validation or verification checkpoints within the workflow.

Suggestions

Add a verification checkpoint before the Deliver step (e.g., confirm 2-3 transcript-derived shifts exist and timestamp links resolve before presenting the dashboard).

Tighten editorial lines like "Go beyond keyword spam and find actual industry movements" and "Do not just read titles" into direct imperatives to recover a few tokens.

Make the Time Context step more concrete by stating the default range to use when the user does not specify one.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with only minor editorial padding such as "Go beyond keyword spam and find actual industry movements" that could be trimmed.

4 / 5

Actionability

Provides concrete tool calls with real parameters (get_trending_videos with video_category_id "20"/"28", region_code, search_channel_videos, generate_timestamp_url), though a few steps like "Determine the timeframe" remain open-ended.

4 / 5

Workflow Clarity

A clear five-step sequence (Time Context, Trending Analysis, Analyst Channel Audit, Ingest, Deliver) with a defined Executive Dashboard deliverable, but no explicit validation or feedback-loop checkpoints.

4 / 5

Progressive Disclosure

Well-organized into Objective, Execution Steps, and Next Actions; under 50 lines with no need for external references, satisfying the simple-skill exception for a top score.

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 the skill's purpose and domain but omits any explicit "when to use it" trigger guidance, which caps its completeness. It is reasonably specific and distinct, though the trigger terms lean slightly formal rather than natural.

Suggestions

Add an explicit "Use when..." clause naming concrete trigger phrases a seller would say (e.g., "Use when preparing for a client meeting in an unfamiliar industry or when the user asks for a competitive landscape briefing").

Broaden trigger terms to include natural synonyms like "industry briefing", "competitive landscape", or "market trends before a meeting".

List one or two more concrete actions (e.g., synthesize trends, generate timestamped proof links) to raise specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("analyzing trending data", pulling from "analyst/competitor channels") but is not comprehensive, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

Has a clear "what" but no "when" clause — no "Use when..." trigger guidance is present, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Contains some relevant keywords ("macro industry trends", "trending data", "analyst/competitor channels") but is missing common natural variations a seller would actually say.

3 / 5

Distinctiveness Conflict Risk

The seller-focused macro-trend niche with analyst/competitor channels is mostly distinct with only minor overlap risk against general research skills.

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.