muapi-blog-header

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

Quality

57%

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

57%

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 concrete CLI guidance for a simple single-shot task, but is held back by a duplicated description line, generic agent boilerplate, and an unresolved aspect-ratio inconsistency across the description, prompt, and command.

Suggestions

Resolve the aspect-ratio conflict: pick one value (e.g. 1.91:1 / 1200×628 for Open Graph) and use it consistently across the description, the prompt style line, and the `muapi image generate` call.

Drop the verbatim bolded description line at the top of the body since it duplicates the frontmatter, and trim the generic "Notes for the Executing Agent" boilerplate to only blog-header-specific operational detail.

Provide a fully assembled example prompt and command for one sample topic so the guidance is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the bolded opening line duplicates the frontmatter description verbatim and the "Notes for the Executing Agent" section is generic recipe boilerplate not specific to blog headers, so not every token earns its place.	2 / 3
Actionability	It gives a concrete `muapi image generate` command with a model ID and a structured prompt template, but the aspect ratios conflict (1.91:1 vs 21:9 vs 1200×628) and the prompt still requires assembly, so it is not fully copy-paste ready as the score-3 anchor demands.	2 / 3
Workflow Clarity	The 3-step sequence (metaphor → prompt → generate) is clear and the Deliverables act as an output checklist, but the contradictory aspect ratio guidance creates ambiguity and there are no validation checkpoints; it falls below score 3 because the conflicting detail leaves the operator unsure which ratio to use.	2 / 3
Progressive Disclosure	The skill is self-contained (no references/, scripts/, or assets/ bundles), under roughly 55 lines, and organized into clearly labeled sections (Inputs, Steps, Deliverables, Notes, Trigger Keywords); per the guidelines a short skill needing no external references can score 3 with well-organized sections.	3 / 3
	Total	9 / 12 Passed

Description

57%

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 and distinct in its niche but stops short of full completeness: it states what the skill does concretely yet omits any explicit "Use when…" trigger guidance, and the natural trigger variations are siloed in the body rather than the description.

Suggestions

Append an explicit trigger clause to the description, e.g. ". Use when the user needs a blog post header, featured image, hero image, or Open Graph image."

Surface 2–3 natural trigger terms (featured image, og image, hero image) directly in the description instead of relying on the body's Trigger Keywords section.

Tighten fluff like "professional, eye-catching" to keep the description concrete and token-efficient.

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete output ("blog post header image sized for web (1200×628)") plus an optional deliverable ("title composition guidance"), but describes essentially one primary action rather than the multiple distinct concrete actions of the score-3 anchor.	2 / 3
Completeness	It clearly answers "what" (create a web-sized blog header image with composition guidance) but provides no "Use when…" clause or explicit trigger guidance; per the guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	"blog post header image" and "title composition" are natural terms a user might say, but the richer variations (featured image, og image, hero image) appear only in the body's Trigger Keywords, not in the description itself.	2 / 3
Distinctiveness Conflict Risk	The niche is specific and narrow — web-sized 1200×628 blog headers with title composition guidance — making it clearly distinguishable and unlikely to trigger for unrelated skills; it is above score 2 because the sizing/composition framing pins it to a distinct use case.	3 / 3
	Total	9 / 12 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: 71242e2

Reviewed: about 20 hours 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.