CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

design-style-picker

Batch-generate and compare visual design directions so a user can choose the style they actually want. Use when the user says they cannot describe an abstract visual style, asks for many style options, wants to choose from generated UI/design-system images, rejects outputs as too colorful/too dead/too generic, or needs an existing UI/design system evolved without discarding current assets.

Quality

84%

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

78%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 well-structured instructional skill: clear sequenced workflow with review/repair checkpoints, concrete generation parameters and a usable prompt template, and clean one-level-deep progressive disclosure. Main weaknesses are mild repetition of the retention/adoption caveat and a few abstract passages that dilute executability.

Suggestions

Consolidate the retention/adoption caveat into one place (e.g., step 1) and reference it tersely elsewhere; it is currently repeated in steps 1, 6, and the playbook.

Convert abstract guidance like 'Distinguish choosing one direction, retaining several, and assigning directions' into a small decision checklist with concrete user responses to map.

Make the review-before-presenting step an explicit validation gate: a short list of pass/fail checks (surface coverage, state coverage, contrast between candidates) applied before presenting paths.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no explanation of concepts Claude already knows; every section carries guidance. The retention/adoption caveat ('Multiple options do not imply mutual exclusion...') repeats across steps 1, 6, and the playbook, and a few dense hedging sentences could be trimmed, matching anchor 4 rather than 5.

4 / 5

Actionability

Concrete, executable guidance throughout: specific ladder values ('color intensity 20/35/50/65/80'), a fill-in prompt template, explicit boundary samples ('safe, middle, high, and overload boundary'), and a concrete fusion example ('Use H02 for color placement and V04 for palette intensity'). A few abstract sentences ('Distinguish choosing one direction, retaining several...') keep it below fully copy-paste-ready level 5.

4 / 5

Workflow Clarity

A clear 6-step sequence with feedback loops ('If two images look like siblings, regenerate one with a clearer contrast', 'Repair missing coverage before judging colors', 'Run rendered visual QA after implementation'). Not 5 because some checkpoints are implicit — e.g., no explicit verify step between generation and presentation beyond 'Open generated images yourself', and review criteria are described but not as a strict gate.

4 / 5

Progressive Disclosure

The body is a well-organized overview and its single reference is clearly signaled with explicit read conditions ('Read references/selection-playbook.md when running a full style-selection session or when the user gives taste corrections during image exploration'). The reference exists, is one level deep, and points to no further files, matching the anchor 5 structure.

5 / 5

Total

17

/

20

Passed

Description

83%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 strong description with an explicit 'Use when' clause grounded in natural user phrasing, including distinctive taste-rejection triggers. Minor improvements possible in action coverage and trigger synonyms.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Batch-generate and compare visual design directions', 'evolved without discarding current assets') with a clear user outcome, but coverage is narrower than a comprehensive action list. It is above level 3 because more than 1-2 specific actions are named, and below 5 because capability coverage has minor gaps.

4 / 5

Completeness

Explicitly answers both what ('Batch-generate and compare visual design directions so a user can choose the style they actually want') and when ('Use when the user says they cannot describe... rejects outputs as too colorful/too dead/too generic...'), with multiple concrete trigger phrases. Clearly matches the anchor 5 example structure.

5 / 5

Trigger Term Quality

Natural user phrases are well covered: 'cannot describe an abstract visual style', 'asks for many style options', 'too colorful/too dead/too generic', 'choose from generated UI/design-system images'. A few common synonyms (e.g., 'style variants', 'themes', 'mood board') are missing, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The taste-rejection triggers ('too colorful/too dead/too generic') and style-option selection niche are distinctive, but 'needs an existing UI/design system evolved' has minor overlap risk with general design-system or UI-restyling skills, fitting anchor 4 rather than 5.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

daymade/claude-code-skills

Path

daymade-codex/design-style-picker/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.