CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-ui-design

Generate high-fidelity UI/UX mockups for mobile and web apps using Atomic Design principles — creates wireframes and design systems via muapi.ai

Quality

69%

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 ./.opencode/skills/muapi-ui-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 skill body is well-organized and gives mostly concrete, executable guidance centered on a clear two-step workflow, but it spends tokens re-explaining design concepts Claude already knows and lacks any validation or error-recovery checkpoint around image generation. The dangling script references also slightly undermine its structure.

Suggestions

Add a validation step after script invocation, e.g., check the generated image against the Constraints section (no hands/devices, contrast, consistent atoms) and regenerate with adjusted flags if it fails — this addresses the weakest dimension, workflow clarity.

Trim the "Core Competencies" section and generic design-token explanations (Atomic Design, Nielsen's heuristics, 8pt grid, WCAG basics) down to one-line pointers; keep only muapi-specific and non-obvious guidance to improve conciseness.

Either include the referenced "scripts/generate-mockup.sh" (and document its full flag set and outputs) or remove/fix the dangling references so the documented invocation actually resolves in the bundle.

DimensionReasoningScore

Conciseness

The body is mostly task-relevant, but the "Core Competencies" section, the Nielsen's Heuristics mention, and the generic design-token explanations (Inter/Roboto, 8pt grid, WCAG) re-teach design concepts Claude already knows, and the intro sentence duplicates the header line — more than minor trimmable padding, so anchor 3 rather than 4.

3 / 5

Actionability

The bash invocation is concrete and executable-shaped ("bash scripts/generate-mockup.sh --desc ... --platform mobile --theme dark --style glassmorphism") and the numbered prompt-expansion steps give specific directives ("Input fields with 4px radius", "Inter Sans-serif"). Minor gaps: the script's outputs and full flag set are undocumented, and both referenced scripts are missing from the bundle — mostly executable, not fully copy-paste ready, so anchor 4.

4 / 5

Workflow Clarity

A real sequence exists ("Step 1: Define the Product Brief" → "Step 2: Invoke the Script", preceded by the Prompt Optimization Protocol), but there are no validation checkpoints or error-recovery loops — e.g., no step to verify the generated image meets the "no hands/phones" and contrast constraints before delivering. Anchor 3: steps present, checkpoints missing.

3 / 5

Progressive Disclosure

The body is well-sectioned and self-contained (Intent Mapping, Tokens, Protocol, Constraints), but no bundle files exist while the body references "scripts/generate-mockup.sh" and "core/media/generate-image.sh" that aren't present, and the ~75-line body exceeds the 50-line simple-skill threshold while inlining reference-style tables. Good structure with minor organization gaps — anchor 4.

4 / 5

Total

14

/

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.

The description states concrete third-person capabilities with good natural trigger terms, but it omits any "when to use this" guidance, which caps its completeness at 3. Adding an explicit "Use when..." clause covering prototyping/design-mockup requests would resolve the main weakness.

Suggestions

Append a trigger clause such as "Use when the user asks for app or website mockups, UI/UX prototypes, wireframes, or a design system for mobile or web apps."

Add natural synonym terms users actually say — "prototype", "app design", "landing page design" — to broaden trigger coverage.

Optionally mention one more concrete action (e.g., iterating on or refining an existing mockup) to close the small specificity gap.

DimensionReasoningScore

Specificity

Lists several concrete third-person actions ("Generate high-fidelity UI/UX mockups", "creates wireframes and design systems") with named platforms, but coverage of related tasks (editing, exporting, iterating on mockups) has minor gaps — anchor 4 rather than 5.

4 / 5

Completeness

The "what" is clear (generate mockups/wireframes/design systems), but there is no "Use when..." clause or any trigger guidance; per the rubric guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural phrases like "UI/UX mockups", "wireframes", "design systems", and "mobile and web apps" are present, but common variations users would say ("prototype", "app design", tool-specific extensions) are missing — good coverage, not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The mockup/wireframe/muapi.ai framing carves a fairly distinct niche, but it could still overlap with general design, branding, or image-generation skills; minor overlap risk — anchor 4, not 5.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

SamurAIGPT/Generative-Media-Skills

Path

.opencode/skills/muapi-ui-design/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.