CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

72%

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-automation/SKILL.md
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 rich in concrete, non-obvious operational knowledge (quota math, ID conversions, pagination and parsing pitfalls) and each workflow is easy to follow, but it is undercut by redundancy (duplicative quick-reference table, filler 'When to Use' section), missing verification steps around destructive/batch operations, and no progressive disclosure of the bulk reference material into separate files.

Suggestions

Add validation checkpoints to destructive/batch workflows, e.g. after YOUTUBE_UPLOAD_VIDEO verify via YOUTUBE_VIDEO_DETAILS that title/privacyStatus landed, and on GET_VIDEO_DETAILS_BATCH handle fewer items than requested by retrying missing IDs.

Move the per-workflow parameter/pitfall detail or the Quick Reference table into a references/ file (e.g., references/tool-reference.md) and keep SKILL.md as an overview, cutting the duplicative table and the empty '## When to Use' section.

Remove the redundant 'Get Rube MCP' paragraph that repeats the Prerequisites bullets, and replace '(check schema)' table entries with the actual key parameters.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious operational detail (quota costs, ID-format quirks, byte-vs-character limits), but the Quick Reference table largely re-lists tools and parameters already given in the workflow sections, 'Get Rube MCP' repeats the Prerequisites bullets, and the '## When to Use' section is pure filler ('This skill is applicable to execute the workflow or actions described in the overview.'). Not 4 because the duplication and filler go beyond minor trimmable instances.

3 / 5

Actionability

Each workflow gives a concrete numbered tool sequence with named tool slugs, key parameters with types and limits, and specific pitfalls — mostly executable guidance. Not 5 because several Quick Reference rows punt with '(check schema)' and no example request payloads are shown for the trickier calls (e.g., videoFilePath's {name, mimetype, s3key} object).

4 / 5

Workflow Clarity

Sequences are clearly structured and setup includes a validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows'), but destructive and batch operations (upload at 1600 quota units, batch video details that 'may return fewer items than requested') have no post-operation verification or error-recovery loops. Per the judging guideline, missing validation in destructive/batch workflows caps this at 3.

3 / 5

Progressive Disclosure

The skill is a single ~215-line file with no references/ or other bundle files; all per-tool operational detail, including a 17-row quick-reference table, is inlined. This matches the anchor of substantial reference material that belongs in a separate file. Not 4 because nothing is split out and there is no navigation to detail files; not 2 because the content itself is well-sectioned with clear headers.

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.

A specific, well-scoped description with strong action coverage and low conflict risk, weakened only by the complete absence of a 'when to use' trigger clause and some missing natural trigger synonyms (channel, subscribe, thumbnails).

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to upload, search, or manage YouTube videos, playlists, channels, or comments.'

Include natural trigger variations users would actually say: 'channel', 'subscribe', 'thumbnail', 'video metadata'.

DimensionReasoningScore

Specificity

The description enumerates five concrete actions ('upload videos, manage playlists, search content, get analytics, and handle comments') with comprehensive coverage of the skill's domain, matching the top anchor's multi-action example. Not 4 because there is no meaningful gap in the action coverage.

5 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent trigger guidance — 'Always search tools first for current schemas' is operational instruction, not a when-to-use trigger. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural-term coverage ('upload videos', 'playlists', 'search', 'analytics', 'comments', 'YouTube'), but misses common variations users would say such as 'channel', 'subscribe', 'subscriptions', or 'thumbnails'. Not 5 because synonyms for several covered workflows are absent; not 3 because most natural trigger phrases are present.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (YouTube operations via a specific MCP server) with distinct triggers ('YouTube', 'upload videos', 'playlists'), so risk of firing for the wrong skill is minimal. Not 4 because no closely related skill would plausibly collide with these triggers.

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

Path

skills/youtube-automation/SKILL.md

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.