CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

design-an-interface

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

85

1.36x
Quality

82%

Does it follow best practices?

Impact

98%

1.36x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 delivers a clear, actionable five-step workflow with an excellent copy-paste sub-agent prompt template and useful anti-pattern guardrails, all appropriately contained in one well-organized file. Its main weakness is redundancy: the Evaluation Criteria section repeats the Step 4 comparison dimensions almost verbatim, and explicit validation checkpoints (e.g., confirming the generated designs are genuinely divergent) are absent.

Suggestions

Merge the 'Evaluation Criteria' section into Step 4's comparison list to remove the duplicated dimensions (simplicity, general-purpose, efficiency, depth) and save tokens.

Add an explicit checkpoint after sub-agents return, e.g. 'Verify designs are radically different; if two are similar, regenerate one with a stronger constraint' — a feedback loop that also operationalizes the first anti-pattern.

Tighten loose parameters: specify the exact number of sub-agents (e.g., 'spawn 3-4') and phrase the tool reference generically (e.g., 'your sub-agent tool') so the skill is environment-agnostic.

DimensionReasoningScore

Conciseness

Mostly efficient, but the 'Evaluation Criteria' section duplicates the comparison dimensions already stated in Step 4 ('Interface simplicity', 'General-purpose', 'Implementation efficiency', 'Depth' each appear twice), and the book attribution is repeated. Not 2 because there is no explanation of concepts Claude already knows; not 4 because the duplicated section is a genuine redundancy, not a minor trim.

3 / 5

Actionability

Provides a copy-paste-ready sub-agent prompt template with per-agent constraint assignments, a structured output format, and a concrete requirements checklist. Not 5 because of loose details ('3+ sub-agents', environment-specific 'Task tool', unfilled placeholders); not 3 because the guidance is executable as written, not pseudocode.

4 / 5

Workflow Clarity

Clear 5-step sequence (Gather → Generate → Present → Compare → Synthesize) with a checklist in step 1 and anti-pattern guardrails. Not 5 because there are no explicit validation checkpoints or feedback loops (e.g., verifying designs are actually radically different before presenting); not 3 because the sequence is complete and well defined with implicit checkpoints via the anti-patterns.

4 / 5

Progressive Disclosure

A single self-contained file with no bundle files and no need for external references: well-organized sections (Workflow, Evaluation Criteria, Anti-Patterns) that are easy to navigate. Per the simple-skill scoring note, well-organized sections with no need for external references earn the top score.

5 / 5

Total

16

/

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: it states concrete capabilities in third-person voice and pairs them with an explicit 'Use when' clause containing natural, distinctive trigger phrases including the signature term 'design it twice'. The only gaps are a few missing synonyms and slightly incomplete action coverage.

DimensionReasoningScore

Specificity

Names the domain (interface design) and several specific actions: 'Generate multiple radically different interface designs', 'using parallel sub-agents', 'design an API, explore interface options, compare module shapes'. Not 5 because coverage is not fully comprehensive (synthesis and evaluation actions are implied rather than listed); not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: what ('Generate multiple radically different interface designs for a module using parallel sub-agents') and when ('Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice"'). This matches the top anchor nearly verbatim.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say: 'design an API', 'explore interface options', 'compare module shapes', 'design it twice'. Not 5 because common synonyms like 'API design' or 'module interface' are missing; not 3 because keyword coverage is good, not partial.

4 / 5

Distinctiveness Conflict Risk

Clear niche (interface/module design via parallel sub-agents) with a distinctive signature trigger ('design it twice'). Not 5 because there is minor overlap risk with general design or architecture-planning skills; not 3 because the trigger set is well differentiated from generic design skills.

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

SnowingFox/ai-skills

Path

.cursor/skills/design-an-interface/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.