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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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 well-organized, lean routing overview that effectively delegates detail to bundled workflows and references with clear checkpoints. Its main weakness is actionability: several routing steps are directional rather than giving concrete file paths or commands.

Suggestions

Add concrete file paths for the routing steps where feasible (e.g., name the specific workflow SKILL.md files to read for each common sequence instead of only naming the directories).

For the 'smallest suitable implementation' fallback, give one or two concrete host-supported starting points rather than only describing the preference abstractly.

Dimension	Reasoning	Score
Conciseness	Lean overview that assumes Claude's competence and avoids explaining what Product Design or a frontend stack is; every section earns its place with no padding or concept restating.	3 / 3
Actionability	Routing is concrete ('Read workflows/index/SKILL.md completely', 'Resolve relative links from the file that contains the link') but several steps are directional rather than executable and lack the specific commands/files that the top anchor expects; it stops just short of fully actionable guidance.	2 / 3
Workflow Clarity	The numbered routing sequence is explicit with clear checkpoints ('Read every selected workflow's SKILL.md completely before acting') and gating guards against over-loading unrelated workflows, satisfying the clear-sequence-with-checkpoints anchor.	3 / 3
Progressive Disclosure	A concise overview that points one level deep to workflows/index/SKILL.md and the real reference files in references/ (communication-protocol.md, critical-overrides.md, existing-codebase-edits.md), with bundled capabilities enumerated for easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

85%

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 comprehensive and clearly scoped, explicitly covering both capability and invocation triggers for a well-defined Product Design niche. It is slightly held back by jargon-tinged trigger phrasing rather than purely natural user language.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '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' — matching the top anchor for listing several specific actions.	3 / 3
Completeness	Explicitly answers both what (the enumerated design activities) and when ('Use this skill when Product Design is explicitly invoked or the main task is...'), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Includes some natural terms a user might say ('UX research', 'design QA', 'sharing a prototype') but mixes in less colloquial phrasing ('cloning a live product surface', 'flow auditing') and lacks common variations, so it sits below the full-coverage anchor.	2 / 3
Distinctiveness Conflict Risk	It carves a clear niche tied to a named Product Design bundle with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: XiaomiMiMo/MiMo-Code
Path: packages/opencode/src/skill/builtin/.bundle/product-design/SKILL.md
Commit: ff87d47

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.