CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-brand-kit

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

Quality

70%

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

Quality

Content

68%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 lean, well-structured, and gives concrete model IDs, aspect ratios, and prompt templates for each asset. Its main weaknesses are the absence of any validation checkpoint on the batch of generated assets, a confusing typo in the key orchestration instruction, and frontmatter-matter (trigger keywords, restated description) inlined in the body.

Suggestions

Add a validation checkpoint after Phase A, e.g. verify each generated asset succeeded before composing the deliverables summary, and retry failed generations.

Fix the typo 'Submit ONE the plan with' to a precise instruction such as 'Submit ONE plan with:' and show the exact `muapi` plan-submission command syntax.

Remove the restated bold description and the 'Trigger Keywords' section from the body — move trigger guidance into the frontmatter description's 'Use when' clause.

DimensionReasoningScore

Conciseness

Efficient input table and lean prompt templates with no over-explanation of concepts Claude already knows; every section instructs rather than teaches. Falls short of 5 due to minor redundancy: the frontmatter description is restated verbatim in bold, and two separate 'Notes' sections could be merged.

4 / 5

Actionability

Provides concrete, near-executable guidance — specific model IDs, aspect ratios, and full prompt templates per asset, plus CLI fallback instructions. Not 5 because the typo 'Submit ONE the plan with' obscures the core orchestration instruction and the exact `muapi` plan-submission syntax is never shown.

4 / 5

Workflow Clarity

The two phases are clearly sequenced (parallel asset generation, then deliverables summary), but there are no validation or verification checkpoints on the generated outputs. Because the plan is a batch operation (four parallel generations in one plan), the rubric caps workflow clarity at 3.

3 / 5

Progressive Disclosure

A single self-contained file, well-organized into Inputs / Steps / Notes with no external references needed and no buried content. Not 5 because the 'Trigger Keywords' section and the duplicated bold description belong in the frontmatter rather than the body, leaving minor organization gaps.

4 / 5

Total

15

/

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.

The description clearly states what the skill produces and names its concrete deliverables, but it lacks any 'when to use' trigger guidance and misses common synonym terms like 'branding' and 'brand identity'. Adding an explicit use-when clause would resolve the completeness cap.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks for a brand kit, branding, brand identity, visual identity, or logo design."

Include common synonym terms users actually say ('branding', 'brand identity', 'visual identity') so the description matches natural phrasing.

Mention the pattern/texture asset or the deliverables summary so the 'what' fully covers the skill's actual outputs.

DimensionReasoningScore

Specificity

Names the domain and three concrete deliverables ("logo concept, color palette moodboard, and typography pairing suggestions"), matching the 'lists several specific actions; minor gaps in coverage' anchor. Falls short of 5 because the action verb is generic ('Generate') and other deliverables in the body (pattern asset, usage guidance) are omitted.

4 / 5

Completeness

Has a clear 'what' (generate a brand visual kit with named deliverables) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Contains relevant natural terms ('brand', 'logo', 'color palette', 'typography') but misses common variations users would say such as 'branding', 'brand identity', or 'visual identity'. Not 4 because those frequent synonyms are absent, not 2 because several genuinely natural keywords are present.

3 / 5

Distinctiveness Conflict Risk

Occupies a fairly distinct niche (brand visual kits) with specific deliverable vocabulary; minor overlap risk with generic image-generation or design skills. Not 5 because 'logo' and 'brand' alone could collide with broader design-related skills.

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