CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

baoyu-cover-image

Generates article cover images with 5 dimensions (type, palette, rendering, text, mood) combining 11 color palettes and 7 rendering styles. Supports cinematic (2.35:1), widescreen (16:9), and square (1:1) aspects. Use when user asks to "generate cover image", "create article cover", or "make cover".

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 well-engineered instruction skill: the body stays an actionable overview with hard gates, exact commands, and file conventions, while details live one link deep in a well-organized 34-file bundle. Remaining gaps are small: a missing output-verification step in the workflow, slight repetition of policy caveats, and one orphaned bundle file.

Suggestions

Add an explicit post-generation validation step in Step 4 (e.g., verify cover.png exists and its dimensions match the confirmed aspect ratio) and pair the auto-retry with a brief diagnose-and-adjust loop.

Either link references/base-prompt.md from the body (e.g., from Step 3 or the prompt-template reference) or remove it, so no bundle content is unreachable from SKILL.md.

Drop the duplicated tool-substitution caveats (stated in both 'User Input Tools' and 'Image Generation Tools') into one line to save tokens.

DimensionReasoningScore

Conciseness

The body is dense and skill-specific throughout — tables for options, dimensions, and file structure; no explanations of concepts Claude already knows — e.g., the backend resolution list and "⛔ Raster only" / "⛔ No bitmap text patching" rules state policy in minimal tokens. Minor trimming is possible (the tool-substitution caveat is stated twice: "Concrete AskUserQuestion references below are examples" and "Tool names above are examples; use the local equivalent in other runtimes"; the Confirmation Policy is restated at Step 2), which keeps it at anchor 4 rather than 5.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact commands ("Skill with skill: 'imagegen'", "baoyu-image-gen --provider codex-cli", "test -f refs/ref-NN-{slug}.{ext}"), exact file-naming patterns ("prompts/NN-{type}-[slug].md"), concrete directory layouts, and a copy-ready completion-report template. Anchor 5's 'specific examples cover the common cases' is met, with prompt details correctly delegated to workflow/prompt-template.md.

5 / 5

Workflow Clarity

Steps 0-5 are clearly sequenced with a progress checklist, explicit gates ("⛔ BLOCKING unless --quick", "Hard gate per the Confirmation Policy"), a backup-before-regenerate rule, and an error-recovery path ("On failure: auto-retry once") — matching anchor 4's 'clear sequence with most checkpoints present'. It falls short of anchor 5 because there is no post-generation verification step (e.g., confirming cover.png exists / matches the requested aspect) and the retry loop has no diagnose-and-fix phase.

4 / 5

Progressive Disclosure

The body is a genuine overview: every detail domain is one clearly-signaled link away (types.md, palettes/, renderings/, dimensions/*.md, workflow/*.md, config/*.md), all 18 referenced paths resolve to real files, and cross-links between reference files are navigational rather than content-burying. One organization gap keeps it from anchor 5: references/base-prompt.md (~100 lines of base-prompt scaffold) is orphaned — linked from neither SKILL.md nor any other bundle file.

4 / 5

Total

17

/

20

Passed

Description

83%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 strong description: concrete, third-person, and specific about the capability surface (dimensions, palettes, renderings, aspect ratios), with an explicit 'Use when' trigger clause containing natural quoted phrases. The only gaps are missing common synonyms for cover-image requests, which slightly limit trigger coverage and distinctiveness from general image skills.

DimensionReasoningScore

Specificity

"Generates article cover images with 5 dimensions (type, palette, rendering, text, mood) combining 11 color palettes and 7 rendering styles" and "Supports cinematic (2.35:1), widescreen (16:9), and square (1:1) aspects" enumerate a concrete capability surface rather than generic claims. It sits above anchor 3 (which expects only 1-2 concrete actions with no parameter detail) but below anchor 5, which requires multiple distinct actions (generate, extract, fill, merge) rather than one action with rich parameters.

4 / 5

Completeness

It clearly answers both questions: the 'what' is concrete ("Generates article cover images with 5 dimensions... 11 color palettes and 7 rendering styles") and the 'when' is an explicit "Use when user asks to..." clause with quoted trigger phrases, exactly matching anchor 5. Anchor 4 would apply only if the 'when' were vague or implicit, which it is not.

5 / 5

Trigger Term Quality

"Use when user asks to 'generate cover image', 'create article cover', or 'make cover'" provides natural phrases a user would actually say, matching anchor 4's 'good keyword coverage; a few natural terms missing'. Not anchor 5 because common synonyms such as 'cover art', 'header image', 'hero image', or 'OG image' are absent.

4 / 5

Distinctiveness Conflict Risk

"article cover images" with cover-specific triggers carves a clear niche, but the description overlaps minorly with general image-generation skills (e.g., a bare 'make cover' request could also match a generic image skill), matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills') rather than anchor 5's minimal-conflict profile.

4 / 5

Total

17

/

20

Passed

Validation

68%

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

Validation — 11 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 9 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 14 deeper-than-1-level

Warning

Total

11

/

16

Passed

Repository

JimLiu/baoyu-skills

Path

skills/baoyu-cover-image/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.