muapi-brand-kit

Generate a cohesive brand visual kit — logo concept, color palette moodboard, and typography pairing suggestions.

Quality

58%

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/brand-kit/SKILL.md

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete CLI commands and complete prompt templates, and it is reasonably well organized. It loses points for a duplicated/garbled Notes section, redundant orchestration prose, and the absence of validation checkpoints for the parallel batch image generation before the deliverables summary.

Suggestions

Add an explicit validation checkpoint in Phase B — verify each generated asset (logo A, logo B, moodboard, pattern) exists/loaded before summarizing, retrying failed generations.

Merge the two 'Notes' sections and trim the 'Notes for the Executing Agent' block to only what is non-obvious (curl fallback + placeholder substitution), removing restated orchestration steps.

Fix the typo/garble in Phase A ('Submit ONE the plan with:') to a clear instruction such as 'Submit one parallel plan with:'.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean (tight prompt strings and a compact inputs table), but the duplicated 'Notes' section and the 'Notes for the Executing Agent' block restate orchestration guidance Claude can infer, so it could be tightened.	2 / 3
Actionability	Each asset step gives a concrete executable command (`muapi image generate` with explicit model IDs, aspect ratios, and full prompt templates) plus a curl fallback and a polling command, making it copy-paste ready.	3 / 3
Workflow Clarity	The phases are clearly sequenced (parallel generation in A, summary in B), but there are no validation checkpoints to confirm each generated asset before producing the Phase B summary, and Phase A's instruction ('Submit ONE the plan') is garbled.	2 / 3
Progressive Disclosure	The single file is well-organized into sections (Inputs, Steps, Notes, Trigger Keywords) and has no broken references, but two separate disjoint 'Notes' sections and one line that reads as an afterthought slightly weaken clear top-level navigation; there are no external reference files to score.	2 / 3
	Total	9 / 12 Passed

Description

52%

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 clearly differentiated, but it omits an explicit 'Use when...' trigger clause and relies on a separate body section for natural keywords, which caps completeness and trigger-term quality. Third-person voice is used correctly.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when the user wants a brand kit, logo concept, color palette, or typography pairing for a new brand.'

Fold natural user terms ('brand kit', 'branding', 'logo', 'brand design') into the description itself instead of only listing them in the body's Trigger Keywords section.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete deliverables — 'logo concept, color palette moodboard, and typography pairing suggestions' — naming distinct actions rather than vague abstractions.	3 / 3
Completeness	It clearly answers 'what' the skill does but the 'when/Use when...' trigger guidance is absent from the description, capping completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	The description itself contains only technical product language ('brand visual kit', 'moodboard'); the natural trigger terms users would say ('brand kit', 'branding', 'logo') live in a separate body section, not in the frontmatter description.	1 / 3
Distinctiveness Conflict Risk	The niche is narrow and specific — generating a multi-asset brand visual kit — making it unlikely to collide with general image-generation or other skills.	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/brand-kit/SKILL.md
Commit: 71242e2

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