CtrlK
BlogDocsLog inGet started
Tessl Logo

design-exploration

Use Design for UI/UX exploration, side-by-side design directions, interactive prototype previews, user selection, iteration, and design-to-code handoff through the hosted Design MCP app.

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/plugins/agent-native-design/skills/design-exploration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 tool calls, exact parameters, and a well-sequenced variant workflow with validation stop-points; its main weaknesses are some editorializing in the quality bar and a monolithic structure with no progressive disclosure into bundle files.

Suggestions

Trim the explanatory rationale in "Design Quality Bar" to directive statements, keeping only the actionable bans and required alternatives.

Consider offloading the detailed reconnect/auth troubleshooting and the full quality-bar checklist into a references/ file, keeping SKILL.md as a tighter overview.

No bundle files exist yet — if reference material is added, ensure referenced paths resolve to real files one level deep.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concepts Claude already knows, but the "Design Quality Bar" section carries editorial rationale prose (e.g. explaining why slop happens) that could be tightened into pure directive guidance.

2 / 3

Actionability

Provides fully executable, copy-paste-ready guidance: exact tool names, mode flags (mode: "replace-file"), fileId parameters, banned hex codes, and a literal reconnect command.

3 / 3

Workflow Clarity

The variant flow is explicitly sequenced with checkpoints and a stop condition ("Stop after the first successful edit-design save"), plus a clear auth-error recovery loop (stop, reconnect, continue) for the destructive/batch variant-deletion step.

3 / 3

Progressive Disclosure

The body is well-organized into clear sections but is a ~108-line monolithic single file with no bundle files and no offloading of detail; some content (quality-bar specifics, reconnect troubleshooting) could be split into references.

2 / 3

Total

10

/

12

Passed

Description

60%

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 action-rich, naming a clear set of design capabilities, but it omits an explicit "Use when..." trigger and natural-term coverage is partial, so it answers "what" well while leaving "when" implied.

Suggestions

Append an explicit "Use when..." clause naming natural triggers, e.g. "Use when the user wants UI/UX mockups, redesigns, side-by-side design directions, prototype previews, or design-to-code handoff."

Broaden trigger vocabulary to cover common variations users say (mockups, wireframes, redesign, design system, look-and-feel).

Add a disambiguating phrase to separate this from sibling apps (e.g. "for visual UI design specifically — use Slides for decks and Assets for media").

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "UI/UX exploration, side-by-side design directions, interactive prototype previews, user selection, iteration, and design-to-code handoff" — matching the multi-action anchor rather than the partial domain+actions level.

3 / 3

Completeness

Clearly states what the skill does but offers no explicit "Use when..." trigger clause; the when is only implied, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant terms a user might say ("UI/UX exploration", "design directions", "prototype previews") but misses common variations like mockups, wireframes, redesign, or design system, so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The Design MCP niche is somewhat specific, but the description could still overlap with general design/build skills or sibling apps (Slides/Assets) and lacks fully distinct trigger phrasing.

2 / 3

Total

9

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
BuilderIO/agent-native
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.