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

66

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/api-shape-explorer/SKILL.md
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.

A well-structured, actionable design-exploration skill with a clear workflow and good organization. The main weakness is redundancy between the comparison step and the Evaluation Criteria section.

Suggestions

Merge or trim the 'Evaluation Criteria' section, since interface simplicity, depth, and implementation efficiency are already laid out in step 4's comparison criteria.

Tighten the preamble ('Based on Design It Twice from A Philosophy of Software Design') to one clause so it motivates the approach without padding.

Consider adding a brief note on how many designs to present by default and when to stop iterating, to make the workflow even more deterministic.

DimensionReasoningScore

Conciseness

Mostly efficient, but the 'Evaluation Criteria' section largely restates criteria already covered in step 4 (interface simplicity, depth, implementation efficiency), creating avoidable token duplication.

3 / 5

Actionability

Provides a concrete sub-agent prompt template with per-agent constraints and a specified output format, plus actionable anti-patterns; minor gaps remain as it is instruction-only with no literal runnable code.

4 / 5

Workflow Clarity

A clear five-step sequence with numbered sub-steps and a requirements checklist; no validation checkpoints are needed for this non-destructive design-exploration skill, so the sequence is solid with only minor gaps.

4 / 5

Progressive Disclosure

A single self-contained file with no external references needed and well-organized section headers, matching the rubric's allowance for compact skills to score 5 on well-organized structure alone.

5 / 5

Total

16

/

20

Passed

Description

87%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, third-person description that clearly states its purpose and gives explicit, natural trigger guidance. Minor headroom remains in enumerating more discrete concrete operations and adding a few more synonymous trigger phrases.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions ('Generate multiple radically different interface designs', 'using parallel sub-agents'), but stops short of the anchor-5 level of four-plus discrete enumerated operations.

4 / 5

Completeness

Explicitly states what the skill does and provides an explicit 'Use when' clause with several concrete trigger phrases, answering both what and when.

5 / 5

Trigger Term Quality

Good natural-term coverage ('design an API', 'explore interface options', 'compare module shapes', 'design it twice'), though a few common synonyms and phrasings a user might naturally say are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (interface/API shape design via parallel sub-agents) with distinctive triggers like 'design it twice' and 'compare module shapes', minimizing overlap with other skills.

5 / 5

Total

18

/

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.

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.