CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-design-guide

Create a comprehensive brand design guide — color palette, typography pairings, UI component previews, and visual identity rules with example mockups.

Quality

75%

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/design-guide/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A well-structured, action-oriented body: concrete prompts, named models, aspect ratios, and clearly phased parallel generation with sensible conditional branches. The gaps are minor — no end-to-end CLI command examples, no validation of generated assets, and slight inline padding.

Suggestions

Show one complete example invocation (e.g. muapi image generate --model bytedance-seedream-v4.5 --prompt "..." --aspect-ratio 16:9) so the CLI argument syntax is unambiguous.

Add a light validation step after generation, e.g. re-check each image for consistent colors/typography against style_direction and regenerate any asset that drifted.

Trim the bold description restatement and the 'Trigger Keywords' section (or fold them into frontmatter) to tighten token usage.

DimensionReasoningScore

Conciseness

The body is lean — a compact inputs table and dense prompt specs with almost no concept explanation Claude doesn't need — but has minor trimmable padding: the bold restatement of the description, the 'Trigger Keywords' section, and the awkward 'all in a single the plan' phrasing. Fits 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Prompts are copy-paste ready with model IDs, aspect ratios, and a curl fallback, but the exact muapi CLI invocation syntax (how model, prompt, and aspect-ratio arguments are passed) is never shown, leaving minor gaps. Matches 'mostly executable guidance; concrete commands with minor gaps' — not anchor 5's fully copy-paste-ready command coverage.

4 / 5

Workflow Clarity

The three parallel phases are clearly sequenced with numbered steps and explicit conditional handling ('If {{primary_color}} is given...', 'If {{existing_logo}} provided, use muapi image edit'), plus a polling hint — but there is no validation checkpoint that generated images match the brand direction before presenting them. Fits 'clear sequence with most checkpoints; minor validation gaps'.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and none are referenced, and the body is well-sectioned — but at ~62 lines it exceeds the under-50-line simple-skill threshold, and content like the trigger-keyword list and agent-operational notes arguably belong elsewhere or in frontmatter. 'Good structure; minor organization gaps' fits better than a clean 5.

4 / 5

Total

16

/

20

Passed

Description

66%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, well-scoped description that clearly names its deliverables and uses natural design vocabulary. Its main weakness is the complete absence of 'when to use' guidance, which both caps completeness and slightly weakens trigger-term quality for users asking about logos or branding.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user asks for a brand design guide, brand identity, style guide, or brand colors and typography for a product or company.'

Include a few missing natural trigger synonyms such as 'logo direction', 'branding', 'brand book', and 'font pairing' to broaden keyword coverage.

Consider naming the underlying actions explicitly (generate color/typography reference cards, mock up UI components, produce real-world brand mockups) instead of the single verb 'Create'.

DimensionReasoningScore

Specificity

Enumerates concrete deliverables ('color palette, typography pairings, UI component previews, and visual identity rules with example mockups') but rests on a single action verb ('Create') rather than multiple distinct actions, so it matches 'several specific actions; minor gaps' rather than the fully comprehensive anchor 5.

4 / 5

Completeness

The 'what' is clear and concrete, but the description contains no 'Use when...' clause or equivalent explicit trigger guidance; per the judging guideline, a missing 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Contains good natural phrases users would say — 'brand design guide', 'color palette', 'typography', 'visual identity' — but omits common variations like 'logo', 'branding', 'fonts', or 'style guide', matching 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

The brand-design-guide niche is specific with distinct vocabulary, carrying only minor overlap risk with general branding/design-system skills, fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

15

/

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/design-guide/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.