user-context

Load or manage Product Design's saved user context. Use when the user asks to set up Product Design, get started, onboard, save product or design sources, see what Product Design remembers, update saved context, or remember Product Design preferences. Examples include product URLs, Figma files, screenshots, reference images, codebase paths, Storybook, tokens, design systems, brand assets, and general product/design notes.

Quality

88%

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

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 actionable and workflow-aware with real validation checkpoints, but loses points on token efficiency (repeated source lists) and on progressive disclosure due to two broken cross-skill reference paths.

Suggestions

Dedupe the source-type enumeration: keep it once (description or Saved User Context) and have the Save section reference it rather than re-listing it.

Fix or remove the broken links to ../index/SKILL.md and ../../references/critical-overrides.md, since unresolved references hurt progressive-disclosure navigation.

Trim the eight image-name examples to two or three representative ones to save tokens while still illustrating the naming convention.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but repeats the source-type list (URLs, Figma, Storybook, tokens, brand assets) three times across the description, Saved User Context, and Save sections, and supplies eight image-name examples where two or three would suffice.	2 / 3
Actionability	Concrete executable commands ("python3 scripts/user_context_preflight.py", "python3 scripts/init_user_context.py"), exact state-file paths, a copy-paste save-structure template, and specific image-naming examples make the guidance directly executable.	3 / 3
Workflow Clarity	The preflight persistence check, the "if any check cannot be completed or fails" failure branch, and the setup→init→add-references sequence provide explicit validation checkpoints and an error-recovery loop.	3 / 3
Progressive Disclosure	references/onboarding.md and the scripts exist and are one level deep, but two referenced paths do not resolve: "../index/SKILL.md" and "../../references/critical-overrides.md", which breaks navigation despite otherwise clear signaling.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 strong description: third-person, concrete, and explicit about both capabilities and triggering situations, with natural user phrasings. No meaningful weaknesses to address.

Dimension	Reasoning	Score
Specificity	"Load or manage Product Design's saved user context" names concrete actions (load, manage, save, update) and enumerates concrete source types (Figma files, Storybook, tokens, design systems), matching the multi-action anchor.	3 / 3
Completeness	It answers both what ("Load or manage Product Design's saved user context") and when (explicit "Use when the user asks to..." clause with multiple triggers), satisfying the top anchor.	3 / 3
Trigger Term Quality	Natural trigger phrasings a user would say are densely covered: "set up Product Design, get started, onboard, save product or design sources, see what Product Design remembers, update saved context, or remember Product Design preferences."	3 / 3
Distinctiveness Conflict Risk	The niche is narrow (Product Design's persisted saved context) and triggers are scoped to Product Design setup/onboarding/context-save, making unintended triggering by unrelated skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning
referenced_paths_exist	Referenced path issues: 8 missing	Warning

	Total	14 / 16 Passed

Repository: XiaomiMiMo/MiMo-Code
Path: packages/opencode/src/skill/builtin/.bundle/product-design/workflows/user-context/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.