CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-youtube-thumbnail

Design a high-CTR YouTube thumbnail — striking imagery, bold text placement, and emotional face/subject if needed.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/muapi-youtube-thumbnail/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 an efficient, actionable recipe: a clear input contract, a three-phase generation workflow with concrete muapi CLI commands, a curl fallback, and genuinely useful practical notes (avoid rendering text in the image, add text in post-production). Weaknesses are minor — some thumbnail-design knowledge padding, a described rather than fully specified generation call, and small structural duplication.

DimensionReasoningScore

Conciseness

The body is tight and mostly earns its tokens: an inputs table, three short phases, and operational notes with concrete commands. Minor over-explanation remains — Phase A restates thumbnail-design principles Claude already knows ("thumbnails compete in a grid — they must pop", bold text = high CTR), and the description is repeated verbatim as the opening line. Efficient with minor trimmable instances matches anchor 4; not anchor 5 because of that padding, not anchor 3 since verbosity is slight.

4 / 5

Actionability

Concrete executable guidance dominates: "Call `muapi image generate` (model=gpt-image-2-text-to-image, aspect_ratio=16:9)", "muapi auth configure first if MUAPI_API_KEY is unset", a copy-pasteable curl fallback with polling via "muapi predict wait <request_id>", and explicit prompt-building steps with {{placeholder}} substitution. Not anchor 5: the primary generation call is described rather than given as a complete copy-paste command with payload, leaving a minor gap.

4 / 5

Workflow Clarity

A clear Phase A (plan composition) → Phase B (generate) → Phase C (overlay guidance) sequence, with input-gathering and auth/polling checkpoints in the agent notes. Not anchor 5: no explicit verification of the generated output or error-recovery loop (e.g. what to do when generation fails or returns poor composition). Not anchor 3: the sequence is complete and checkpoints are mostly present; the destructive/batch cap does not apply since this is a single generation task.

4 / 5

Progressive Disclosure

The skill has no bundle files and does not need them; content is well organized into an Inputs table, phased Steps, Notes, and Trigger Keywords sections, qualifying for high marks under the simple-skill guidance. Not anchor 5: slight organization noise — the description is duplicated as the opening line, and the trailing "Notes for the Executing Agent" scaffolding sits behind a stray horizontal rule, leaving minor gaps versus a cleanly split overview.

4 / 5

Total

16

/

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 is specific about the domain and design elements but reads as a task label rather than a complete skill description: it states only one action verb and omits any 'Use when...' trigger guidance. Trigger coverage is thin — one natural keyword ("YouTube thumbnail") without common variations, even though the body contains a fuller Trigger Keywords list that the description does not leverage.

Suggestions

Add an explicit trigger clause to the description, e.g. "Use when the user asks for a YouTube thumbnail, channel art, or video cover image" — this lifts completeness above the cap of 3.

Fold the body's natural trigger variations ("yt thumbnail", "video thumbnail", "youtube cover") into the description so trigger coverage is not limited to a single keyword.

Name the concrete actions the skill performs beyond the end artifact, e.g. "generates the 16:9 image and recommends overlay text and placement" — this moves specificity from one action verb toward several specific actions.

DimensionReasoningScore

Specificity

The description names the domain ("Design a high-CTR YouTube thumbnail") and lists concrete design attributes ("striking imagery, bold text placement, and emotional face/subject"), but 'Design' is the only action verb and coverage is not comprehensive — no mention of image generation, text-overlay guidance, or A/B variants. This matches anchor 3 (domain plus 1-2 concrete actions) rather than anchor 4, which expects several distinct actions.

3 / 5

Completeness

The 'what' is clear (design a high-CTR YouTube thumbnail with striking imagery, bold text, emotional subject), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description. Per judging guidelines, a missing 'when' clause caps completeness at 3, matching the anchor-3 example of a clear 'what' with 'when' only weakly implied.

3 / 5

Trigger Term Quality

"YouTube thumbnail" is a natural phrase users would say, but it is essentially the only keyword; "high-CTR" is jargon and common variations ("yt thumbnail", "video thumbnail", "thumbnail") are absent from the description. Anchor 3 (some relevant keywords, missing common variations) is the best fit — not 2 since the term is specific and natural, not 4 since coverage is thin.

3 / 5

Distinctiveness Conflict Risk

"Design a high-CTR YouTube thumbnail" carves out a clear niche that is easy to distinguish from most skills, with only minor overlap risk against generic image-generation or graphic-design skills. This sits between anchor 4 (mostly distinct, minor overlap) and anchor 5 (clear niche with distinct triggers); anchor 4 fits best because the description lacks the explicit trigger phrases that anchor 5's example includes.

4 / 5

Total

13

/

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

SamurAIGPT/Generative-Media-Skills

Path

.opencode/skills/muapi-youtube-thumbnail/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.