CtrlK
BlogDocsLog inGet started
Tessl Logo

api-shape-explorer

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".

70

Quality

86%

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

The canonical home for this skill is design-an-interface in mattpocock/skills

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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, actionable five-step process with no external references needed. Its main weaknesses are duplicated criteria between section 4 and the Evaluation Criteria section, and an implicit rather than explicit validation checkpoint for the parallel sub-agent output.

Suggestions

Collapse or remove the standalone 'Evaluation Criteria' section, since its four criteria (interface simplicity, general-purpose, implementation efficiency, depth) already appear in section 4 Compare Designs — keep one authoritative copy.

Add an explicit validation checkpoint after step 2: verify the spawned designs are radically different and regenerate any that overlap before presenting them, turning the Anti-Patterns warning into an active workflow step.

DimensionReasoningScore

Conciseness

Mostly lean and instruction-oriented, but the 'Evaluation Criteria' section largely restates the same four criteria already listed in section 4 (interface simplicity, general-purpose, implementation efficiency, depth), which could be tightened.

2 / 3

Actionability

Provides concrete, actionable guidance — a fill-in prompt template, per-agent constraint assignments, a defined output format, and specific comparison dimensions and synthesis questions — fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

The five-step sequence (Gather → Generate → Present → Compare → Synthesize) is clearly ordered with a checklist, but validation of the batch sub-agent output is only implicit (an Anti-Patterns warning) rather than an explicit 'verify designs are radically different; regenerate if not' checkpoint.

2 / 3

Progressive Disclosure

A single self-contained file with well-organized, clearly headed sections and no nested references; for this process skill there is nothing that needs splitting into a separate bundle file, so the organization is appropriate.

3 / 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.

The description is specific, trigger-rich, and clearly answers both what the skill does and when to use it, with a distinctive niche. It uses the same base-verb voice ('Generate...') as the rubric's own good examples, so no voice penalty applies.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Generate multiple radically different interface designs for a module using parallel sub-agents' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Generate multiple radically different interface designs...') and when ('Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice"'), with an explicit 'Use when...' trigger clause.

3 / 3

Trigger Term Quality

Covers natural phrasings a user would actually say — 'design an API', 'explore interface options', 'compare module shapes', 'design it twice' — giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

The 'design it twice' / 'compare module shapes' / interface-design niche is distinct and unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zebbern/claude-code-guide
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.