CtrlK
BlogDocsLog inGet started
Tessl Logo

product-design

Use this skill when Product Design is explicitly invoked or the main task is product design exploration, UX research, flow auditing or critique, visual ideation, cloning a live product surface, implementing a selected visual target, design QA, saved design context, or sharing a prototype.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 a concise, well-sequenced router that gives actionable routing guidance and clear guardrails. Its main weakness is progressive disclosure: the actual bundled reference files are orphaned from the body and the workflows/ paths it names are not present in the bundle.

Suggestions

Link the bundled reference files individually from the body (e.g. 'See references/critical-overrides.md before user-facing responses') so the existing references/ files are discoverable.

Either include the referenced workflows/ directory (with workflows/index/SKILL.md) or note that those paths live in a separate plugin/bundle, so the body's references resolve against the actual file structure.

Add a brief validation/recovery note for routing (e.g. what to do when a named workflow's SKILL.md is missing), which would lift workflow_clarity to a 5.

DimensionReasoningScore

Conciseness

Lean and well-organized with no over-explanation of concepts Claude already knows, but a few sentences (e.g. restating that workflow instructions live under workflows/ and shared guidance under references/) could be trimmed, keeping it just below the 'every token earns its place' bar.

4 / 5

Actionability

Gives concrete executable routing instructions — 'Read workflows/index/SKILL.md completely', 'Read every selected workflow's SKILL.md completely before acting', 'Resolve relative links from the file that contains the link' — with only minor gaps; appropriately actionable for an instruction-only router with no code.

4 / 5

Workflow Clarity

The 'Route the request' section is a clearly ordered 5-step sequence with gating checkpoints ('completely before acting') and an explicit guardrail ('Do not load unrelated focused workflows merely because they are present'), though it lacks an explicit error/feedback loop.

4 / 5

Progressive Disclosure

The body is structured as an overview pointing to workflows/ and references/, but the three bundled reference files (critical-overrides.md, communication-protocol.md, existing-codebase-edits.md) are never individually linked from the body, and the heavily referenced workflows/ directory is not present in the actual bundle — so references are signaled only at the directory level and navigation to the real bundled files is unclear.

3 / 5

Total

15

/

20

Passed

Description

92%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 is a strong, third-person trigger statement that pairs an explicit 'Use when' clause with a comprehensive list of concrete design activities. It is distinct and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Names the Product Design domain plus nine concrete activities — 'UX research, flow auditing or critique, visual ideation, cloning a live product surface, implementing a selected visual target, design QA, saved design context, or sharing a prototype' — giving comprehensive coverage of specific capabilities rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated design activities) and 'when' via the concrete 'Use this skill when Product Design is explicitly invoked or the main task is ...' trigger clause.

5 / 5

Trigger Term Quality

Strong natural keywords a user would say ('Product Design', 'UX research', 'design QA', 'critique', 'cloning a live product surface', 'sharing a prototype'), but a few common synonyms (e.g. 'wireframe', 'mockup', 'Figma') are absent, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear Product Design niche gated by 'explicitly invoked' and a specific activity list makes it unlikely to fire for unrelated skills, with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
XiaomiMiMo/MiMo-Code
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.