CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

87%

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

82%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.

A highly actionable, well-structured instruction set with real validation gates and a genuine progressive-disclosure split into onboarding and script bundles. The main improvement levers are deduplicating the saved-item taxonomy and adding a post-save verification step to close the workflow loop.

Suggestions

Deduplicate the saved-item list: keep the full taxonomy in one place (Save section) and reference it from Saved User Context instead of repeating ten item categories.

Add a verification step after init_user_context.py and the save write, e.g. re-run scripts/user_context_preflight.py and confirm the new entries parse, before telling the user context was saved for future conversations.

Move the save-format template, category structure, and image-naming examples into a reference file (e.g. references/save-format.md) to slim the body and strengthen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and directive with no padding about concepts Claude already knows, but it is not fully lean: the saved-item taxonomy appears twice ("saved product URLs, Figma files, screenshots, reference images, codebase paths, Storybook, tokens, design systems, brand assets..." in Saved User Context, then again as the Save bullet list), and eight example image filenames are given where two or three would carry the convention. This fits anchor 4 (efficient with minor instances that could be trimmed) rather than anchor 5's "every token earns its place".

4 / 5

Actionability

Guidance is copy-paste ready throughout: exact state paths ($CODEX_HOME/state/plugins/product-design/user-context.md), runnable commands (python3 scripts/user_context_preflight.py, python3 scripts/init_user_context.py), a complete markdown save template with field-by-field semantics, an exact sentinel string ("status: not provided"), and concrete good image names. This matches anchor 5's fully executable, common-case-covering standard.

5 / 5

Workflow Clarity

The Preflight, Setup, Save, and Read flows are clearly sequenced, and the persistence check is a real validation checkpoint with an explicit failure branch ("If any check cannot be completed or fails, persistent context is unavailable. Do not offer saved-context onboarding..."). It falls short of anchor 5's feedback loops because there is no post-save verification that user-context.md was written correctly before claiming context was saved — the success path after init_user_context.py is unvalidated. The destructive/batch cap does not apply since this is not a destructive operation.

4 / 5

Progressive Disclosure

Onboarding detail is appropriately split into a real, verified one-level reference (references/onboarding.md, 68 lines), and the two scripts are concrete and correctly pathed. It sits at anchor 4 rather than 5 because the ~145-line body inlines the full save-format spec, the image-naming guide, and the category template — content that could live in a reference file — and only one external reference exists to absorb detail.

4 / 5

Total

17

/

20

Passed

Description

90%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.

A well-constructed description with excellent trigger coverage, explicit what/when structure, and clean third-person voice. The only weakness is that its action verbs are thin — "load or manage" undersells the save, update, and inspect behaviors the body actually implements.

Suggestions

Replace the generic "manage" with the distinct concrete actions the skill performs, e.g. "Load, save, and update Product Design's saved user context".

Trim the "Examples include..." artifact list (product URLs, Figma files, screenshots, reference images, codebase paths, Storybook, tokens, design systems, brand assets, and notes) to the few highest-signal items, since it duplicates trigger information without adding actions.

DimensionReasoningScore

Specificity

The description names the domain with two actions — "Load or manage Product Design's saved user context" — but "manage" is generic, and the trailing "Examples include..." list enumerates artifact types rather than actions. This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than anchor 4, which requires several specific actions like "Extracts text from PDF files, fills forms, converts pages to images".

3 / 5

Completeness

It explicitly answers both questions: the what is "Load or manage Product Design's saved user context" and the when is an explicit "Use when the user asks to..." clause with concrete trigger phrases, mirroring the anchor 5 exemplar. Voice is third person, so no penalty applies.

5 / 5

Trigger Term Quality

The trigger list is comprehensive and natural — "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" — covering synonyms ("get started"/"onboard") users would actually say, matching the anchor 5 example's coverage including variations.

5 / 5

Distinctiveness Conflict Risk

Every trigger is scoped to "Product Design" (e.g., "set up Product Design", "remember Product Design preferences"), giving the skill a clear niche with minimal overlap risk against generic memory or file skills; only the mild "update saved context" phrasing could brush a general memory skill, which is not enough to drop to anchor 4's "minor overlap risk" framing.

5 / 5

Total

18

/

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

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

14

/

16

Passed

Repository

openai/plugins

Path

plugins/product-design/skills/user-context/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.