CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

youtube-publish

Load to draft a YouTube upload, comment or reply, or send a draft after the user's recorded approval.

Quality

76%

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 ./.agents/skills/youtube-publish/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.

A disciplined, security-conscious instruction-only skill body: lean token use, concrete env vars/scopes/commands, and unusually strong validation and consent checkpoints for a destructive publishing operation. Its main defect is that the central drafting workflow is delegated to workflows/publish.md, which is missing from the bundle, leaving the most important procedure unreachable.

Suggestions

Ship or restore workflows/publish.md in the bundle (or inline the drafting steps into SKILL.md) so the 'follow workflows/publish.md' link resolves — the core procedure is currently unreachable.

Add one complete example invocation, e.g. `scripts/youtube-publish publish --draft draft.json`, showing how the executable subcommand, draft path, and env vars combine.

Turn the post-failure guidance into an explicit recovery loop (check channel state via channels.list → report result to user → re-approve if needed) so interrupted-write handling matches the precision of the pre-write checks.

DimensionReasoningScore

Conciseness

The body (~30 lines) is lean and operational throughout — 'The consumer supplies YOUTUBE_CHANNEL_ID and YOUTUBE_APPROVER_EMAIL in the command environment', 'Use youtube.force-ssl for comments and replies' — with no padding and no explanation of concepts Claude already knows; every sentence carries a constraint, env var, scope, or policy pointer.

5 / 5

Actionability

Concrete, near-executable guidance is present: named env vars, exact OAuth scopes ('youtube.upload', 'youtube.readonly', 'youtube.force-ssl'), the executable path 'scripts/youtube-publish' (verified to exist), and the command 'Run publish --draft PATH only after that yes'. Minor gaps keep it below 5: no full example invocation, and the drafting procedure itself is delegated to workflows/publish.md, which is absent from the bundle.

4 / 5

Workflow Clarity

The draft → approval_record comment → publish sequence is clear with real validation checkpoints for a destructive operation: 'The script checks the token's channel with channels.list before a write', 'It checks the author, decision, item and digest before any YouTube request', and the error-recovery rule 'Stop and check the channel with the user before any new attempt. Do not repeat a successful request'. It is not 5 because the drafting steps themselves live in the missing workflows/publish.md and recovery is stop-and-check rather than an explicit validate-fix-retry loop.

4 / 5

Progressive Disclosure

Sections are well-organized and the body correctly stays an overview, but the single key reference — 'follow [workflows/publish.md](workflows/publish.md)' — points to a file that does not exist in the bundle (only scripts/youtube-publish and scripts/youtube-publish.py are present), breaking navigation to the core workflow. This is more than the 'minor organization gaps' of a 4, so it lands at 3.

3 / 5

Total

16

/

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.

A concise, third-person description with concrete actions and good natural trigger terms ('YouTube upload', 'comment', 'reply', 'draft'). Its main weakness is the missing explicit 'when to use' guidance, which both caps completeness and leaves the trigger situation implied rather than stated.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to draft or publish a YouTube video, post a comment or reply, or asks to send an already-approved upload.'

Include common synonyms such as 'publish', 'post', and 'video' alongside 'upload' so the full range of natural user phrasings matches.

State the distinguishing approval-gated workflow in trigger form ('after the user records approval on the tracker') to sharpen separation from generic YouTube posting skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'draft a YouTube upload, comment or reply' and 'send a draft after the user's recorded approval' — which is specific rather than generic. It stops short of the comprehensive 5 because coverage has minor gaps (no mention of the channel check, visibility reporting, or the tracker-based approval mechanism that defines the skill).

4 / 5

Completeness

The 'what' is clear (draft uploads/comments/replies; send a draft after recorded approval), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. The 'when' is only weakly implied by the action verbs.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'YouTube upload', 'comment', 'reply', 'draft' are terms users would actually say when needing this skill. A few natural variants are missing — 'publish' (ironically the skill's name), 'post a video', 'video' — keeping it below the comprehensive-synonym level 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — YouTube upload/comment/reply drafting with a recorded-approval gate — and unlikely to trigger for unrelated skills, with distinct trigger terms like 'YouTube upload'. It is not 5 because a generic YouTube-posting or video-publishing skill would still overlap on these terms, and the approval framing is stated as a capability rather than a distinct trigger.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/youtube-publish/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.