CtrlK
BlogDocsLog inGet started
Tessl Logo

product-design

Experimental end-to-end product-design orchestrator that frames project context, retrieves research, models experience flows, defines visual direction, creates artifacts, and validates rendered outcomes. Use only when explicitly asked for "end-to-end product design", "design this feature end-to-end", "redesign this flow", "build an experience from this brief", or "create a product experience". Use the stable specialist skills for isolated audits, dashboards, AI features, design systems, handoff, or case studies.

77

Quality

96%

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

92%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 well-structured, lean orchestrator workflow with explicit validation feedback loops and properly split one-level-deep references. The only minor gap is that several phases rely on directive checklists rather than executable code, capping actionability just below the top.

Suggestions

For the directive phases (§4 Model the experience, §5 Establish visual direction), add one or two concrete executable anchors (e.g., a command or template invocation) to raise actionability to fully copy-paste-ready.

Optionally include a minimal example of the search.py result-verification step ('Verify why each result applies') so Claude has a concrete pattern for that checkpoint.

DimensionReasoningScore

Conciseness

The body is dense and directive with no padding or explanation of concepts Claude already knows; even editorial framing lines ('not a collection of fashionable screens') are genuine guidance rather than fluff.

5 / 5

Actionability

Provides real executable commands (validate_context.py, search.py with flags, validate_data.py), but most phases are directive checklists rather than copy-paste-ready code, leaving minor gaps in executable coverage.

4 / 5

Workflow Clarity

A clearly sequenced 7-phase workflow with explicit validation checkpoints in §1, §3, and §6, plus a final Quality Gate checklist with a retry feedback loop ('If a check fails, return to its phase, correct the gap, and run the gate again').

5 / 5

Progressive Disclosure

SKILL.md is a concise overview with well-signaled one-level-deep references to real bundled files (all references/*.md and scripts/* verified to exist); content is appropriately split with easy navigation.

5 / 5

Total

19

/

20

Passed

Description

100%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 exemplary: it states comprehensive concrete capabilities, supplies natural quoted trigger phrases, explicitly covers both what and when, and actively disambiguates from overlapping specialist skills. No changes needed.

DimensionReasoningScore

Specificity

Lists six distinct concrete actions ('frames project context, retrieves research, models experience flows, defines visual direction, creates artifacts, and validates rendered outcomes'), giving comprehensive coverage of the orchestrator's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (the orchestrator capabilities) and 'when' ('Use only when explicitly asked for...') with concrete trigger phrases, fully satisfying the highest anchor.

5 / 5

Trigger Term Quality

Provides multiple natural, quoted trigger phrases users would actually say ('end-to-end product design', 'design this feature end-to-end', 'redesign this flow', 'build an experience from this brief', 'create a product experience') with synonymous variations.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (end-to-end product design) and actively routes away from related specialist skills (audits, dashboards, AI features, design systems, handoff, case studies), minimizing wrong-skill conflict.

5 / 5

Total

20

/

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
aditya-ariosity/ux-ui-skills
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.