CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-blog-header

Create a professional, eye-catching blog post header image sized for web (1200×628) with optional title composition guidance.

Quality

74%

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 ./library/visual/blog-header/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 compact, well-structured, largely executable skill body with a genuinely actionable step sequence. Its main defects are a minor aspect-ratio contradiction between steps 2 and 3 and the absence of a verification checkpoint for the negative-space requirement the deliverables rely on.

Suggestions

Resolve the aspect-ratio inconsistency: step 2 specifies 1.91:1 (matching the 1200×628 header size) while step 3 passes aspect_ratio=21:9 — pick one correct value for both places.

Include one complete copy-paste example of the muapi image generate invocation with placeholders substituted, so the executing agent doesn't have to assemble the command from fragments.

Add a quick post-generation check that the left half of the image is sufficiently uncluttered for title overlay before returning the title-placement guidance.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept explanations, just an inputs table, three numbered steps, deliverables, and brief notes. Minor trims exist: the description is duplicated verbatim as the bold header line, and the 'Leave empty space intentionally' note restates the 'ample negative space on the left side' already baked into the prompt template. This is anchor 4, not 5, because of those small redundancies.

4 / 5

Actionability

Concrete guidance throughout: a specific CLI call ('muapi image generate (model=gpt-image-2-text-to-image, aspect_ratio=21:9)'), a templated prompt string, and a curl fallback for unaliased endpoints. It stops short of anchor 5 because no full copy-paste command example is given, and step 2's 'Aspect ratio: 1.91:1' contradicts step 3's aspect_ratio=21:9 (1200×628 ≈ 1.91:1, so one of the two values is wrong).

4 / 5

Workflow Clarity

The sequence (derive metaphor → build prompt → call CLI → return deliverables) is clear and unambiguous, and as a simple one-shot generation it faces no destructive/batch validation cap. It misses anchor 5 because there is no checkpoint verifying the generated image actually contains the left-side negative space the title-placement deliverable depends on, and the 1.91:1 vs 21:9 contradiction leaves the executing agent uncertain which ratio to request.

4 / 5

Progressive Disclosure

The skill is ~50 lines with no external references needed and no bundle files, and content is organized into well-labeled sections (Inputs, Steps, Deliverables, Notes, Trigger Keywords). Per the rubric's guideline for short single-purpose skills with no reference files, this earns a 5.

5 / 5

Total

17

/

20

Passed

Description

58%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, concise description with a clear 'what', undermined by the complete absence of a 'when to use' trigger clause and thin keyword coverage. Adding a 'Use when...' sentence referencing the natural trigger phrases would lift both completeness and trigger term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user needs a featured image, hero image, or og image for a blog post or article.'

Fold natural synonyms into the description (featured image, OG/open graph image, hero image, article header) instead of confining them to the body's Trigger Keywords section.

Optionally mention the adapt-existing-photo capability so the 'what' covers both creation and editing paths the body supports.

DimensionReasoningScore

Specificity

The description names two concrete capabilities — 'Create a professional, eye-catching blog post header image sized for web (1200×628)' and 'optional title composition guidance' — with a specific pixel dimension. It falls just short of anchor 5 because coverage is limited to creation; no mention of adapting existing photos or other variants.

4 / 5

Completeness

It clearly answers 'what' (create a 1200×628 blog header with title composition guidance) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete and fully specified.

3 / 5

Trigger Term Quality

'blog post header image' is a natural phrase, but the description is missing common variations users would actually say such as 'featured image', 'og image', 'open graph', or 'hero image' (these appear only in the body's Trigger Keywords section, not the description). This matches anchor 3 — relevant keywords present but synonyms missing.

3 / 5

Distinctiveness Conflict Risk

'Blog post header image sized for web (1200×628)' carves a mostly distinct niche with minimal overlap risk. Not 5 because the wording still overlaps with generic image-generation skills and lacks distinguishing trigger phrases in the description itself.

4 / 5

Total

14

/

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

library/visual/blog-header/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.