CtrlK
BlogDocsLog inGet started
Tessl Logo

youtube-analytics

YouTube Analytics integration. Manage Channels, Comments, AnalyticsReports. Use when the user wants to interact with YouTube Analytics data.

62

Quality

73%

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 ./skills/youtube-analytics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable with executable commands and a well-sequenced connection workflow including state-based branching. Conciseness is strong with minor domain-knowledge padding, and progressive disclosure is good though everything is inlined.

Suggestions

Trim the opening overview paragraph that explains what YouTube Analytics is, since this is domain knowledge Claude already has.

Add an explicit validation/confirmation checkpoint before running destructive or batch actions (delete-group, remove-group-item) to satisfy the destructive-operation workflow cap.

Consider moving the popular-actions catalog and proxy flag reference into a bundled reference file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable bash commands and minimal conceptual padding, though the overview paragraph explaining what YouTube Analytics is restates domain knowledge Claude already has and could be trimmed.

4 / 5

Actionability

It provides copy-paste ready bash commands for install, login, connection ensure, action list/run, and proxy requests with concrete flags and a parameterized JSON example, fully covering the common integration cases.

5 / 5

Workflow Clarity

The connection setup is a clear sequence with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling guidance, but destructive/batch operations like delete-group and remove-group-item lack explicit validation or confirmation steps, which is a minor checkpoint gap.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy) with inline popular-actions table; with no bundle files present everything is inline at one level, which is acceptable for this length but the actions catalog could be split out.

4 / 5

Total

17

/

20

Passed

Description

66%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 states a clear niche and includes an explicit 'Use when' trigger, but it relies on the generic verb 'Manage' rather than enumerating concrete actions, limiting specificity. Trigger term coverage is decent but missing common natural variations.

Suggestions

Replace the generic 'Manage' with concrete actions the skill performs, e.g. 'List and query analytics reports, moderate comments, retrieve channel metrics'.

Add natural user-facing trigger terms and synonyms such as 'video stats', 'watch time', 'channel performance', or 'views'.

DimensionReasoningScore

Specificity

Names the domain ('YouTube Analytics integration') and the concrete entities Channels, Comments, AnalyticsReports, but lists no concrete actions beyond 'Manage', which is generic rather than a comprehensive set of specific operations.

3 / 5

Completeness

Has a clear 'what' (manage Channels/Comments/AnalyticsReports) and an explicit 'Use when...' trigger clause ('Use when the user wants to interact with YouTube Analytics data'), satisfying both dimensions, though the 'when' is somewhat broad.

4 / 5

Trigger Term Quality

Contains 'YouTube Analytics' and 'data' as natural keywords, but lacks common synonyms a user might say (e.g. 'video stats', 'channel performance', 'views', 'watch time') and omits file extension–style variants.

3 / 5

Distinctiveness Conflict Risk

The narrow YouTube Analytics niche with explicit entity triggers ('Channels, Comments, AnalyticsReports') makes it clearly distinguishable and unlikely to trigger for unrelated skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.