CtrlK
BlogDocsLog inGet started
Tessl Logo

youtube-automation

Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools first for current schemas.

57

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/youtube-automation/SKILL.md

The canonical home for this skill is youtube-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-structured and actionable with concrete tool names and parameter limits, but it repeats pitfalls across sections and lacks validation/verification checkpoints for its batch and destructive operations. As a single inline file with no bundle references, it misses progressive-disclosure opportunities.

Suggestions

Add validation/verification checkpoints to batch and destructive workflows (e.g., confirm upload succeeded before further steps, verify a video was added to a playlist).

Deduplicate pitfalls — keep them either inline per workflow or consolidated under 'Known Pitfalls', not both — to tighten the token budget.

Move the detailed pitfalls and Quick Reference into separate reference files (e.g., references/quick-reference.md) and link to them from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient — no padding explaining what YouTube is — but pitfalls are repeated across workflow sections and consolidated again in 'Known Pitfalls', and the Quick Reference table re-lists tool slugs and params, so it could be tightened.

3 / 5

Actionability

Provides concrete tool names, specific parameters with limits (e.g., videoFilePath object, maxResults 1-50, 5000-byte description), and numeric quota costs; minor gaps where several Quick Reference rows say '(check schema)' instead of listing params.

4 / 5

Workflow Clarity

Tool sequences are clearly numbered, but batch operations (batch video details, large-playlist pagination) and destructive operations (upload, unsubscribe) lack result-verification checkpoints, capping workflow clarity at 3 per the batch/destructive validation rule.

3 / 5

Progressive Disclosure

Well-organized into clear sections but all content is inlined in a single ~214-line file with no bundle files; the detailed pitfalls and Quick Reference table could be split into separate reference files for better navigation.

3 / 5

Total

13

/

20

Passed

Description

75%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 specific and distinct, naming five concrete YouTube actions, but it omits an explicit 'Use when...' trigger clause, which caps completeness. Trigger term coverage is good but lacks synonym/variant breadth.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when the user wants to upload or manage YouTube videos, search YouTube, get channel/video analytics, or moderate comments').

Broaden trigger terms with common synonyms and variants users say, such as 'YouTube videos', 'channel', 'subscribe', and 'playlists'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'upload videos, manage playlists, search content, get analytics, and handle comments' — giving comprehensive coverage of the YouTube domain.

5 / 5

Completeness

Clearly states what the skill does, but lacks an explicit 'Use when...' trigger clause; 'Always search tools first' is operational instruction, not usage trigger guidance, capping completeness at 3.

3 / 5

Trigger Term Quality

Includes natural phrases users say ('upload videos', 'manage playlists', 'get analytics', 'comments') but misses common synonyms and variants like 'channel', 'subscribe', or 'YouTube videos'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (YouTube automation via Rube MCP) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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.

Validation — 15 / 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
administrakt0r/AI-Agents-Safe-Coding-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.