muapi-blog-header

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

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./library/visual/blog-header/SKILL.md

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 well-structured and gives a concrete, executable generation command with sensible fallbacks. The main weakness is conflicting aspect-ratio guidance (1.91:1, 16:9, and 21:9) across the style string, step text, and the actual call.

Suggestions

Reconcile the aspect ratio: pick one value (the `muapi image generate` call, the '1.91:1' note, or the '16:9 wide' style string) and use it consistently everywhere.

Merge the two 'Notes' sections into one to remove structural redundancy.

Trim the generic 'Notes for the Executing Agent' boilerplate to only what is specific to this recipe, or move it to a shared reference.

Dimension	Reasoning	Score
Conciseness	Mostly lean with useful domain guidance Claude may not know (cliché avoidance, negative-space reasoning); minor trimmable padding like the repeated 'professional, eye-catching' phrasing and the generic 'Notes for the Executing Agent' boilerplate. Not a 5 because of those small over-explanation instances.	4 / 5
Actionability	Provides a concrete executable command (`muapi image generate` with model and aspect_ratio) plus a curl fallback, but the stated aspect ratios conflict (1.91:1, 16:9, and 21:9 appear), leaving a minor gap. Not a 5 due to that inconsistency; not a 3 because the command is still copy-paste ready.	4 / 5
Workflow Clarity	A clear three-step sequence (metaphor → prompt → generate) for a simple single-shot task, with no destructive/batch operation needing validation. Kept at 4 rather than 5 because the conflicting aspect-ratio values create ambiguity about which to actually use.	4 / 5
Progressive Disclosure	Well-organized with clear section headers (Inputs, Steps, Deliverables, Notes) and no nested references; no bundle files are needed. Not a 5 because the two separate Notes sections introduce slight structural redundancy.	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 clearly states what the skill produces but omits any explicit 'when to use' trigger guidance, capping completeness. Trigger-term coverage is moderate because natural synonyms sit in the body rather than the description.

Suggestions

Append a 'Use when...' clause naming trigger phrases (e.g. 'Use when creating blog headers, featured images, og/open graph images, or article hero images').

Fold one or two natural synonyms (featured image, hero image, og image) into the description itself rather than only the body Trigger Keywords list.

Consider adding a second concrete deliverable verb (e.g. 'and generate SEO alt text') to lift specificity beyond two actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('blog post header image sized for web (1200×628)') and two concrete actions (create the image, provide title composition guidance), but coverage is not comprehensive. Not a 4 because only two actions are listed with no broader capability set.	3 / 5
Completeness	The 'what' is clear (create a 1200×628 blog header with title guidance), but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Contains the natural phrase 'blog post header image' but omits common synonyms users say (featured image, og/open graph image, hero image); those live only in the body's Trigger Keywords section, not the description.	3 / 5
Distinctiveness Conflict Risk	The 1200×628 blog-header niche with title overlay guidance is mostly distinct from generic image skills; minor overlap risk with general image-generation skills keeps it just below 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 3b62f78

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.