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

64

Quality

76%

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

67%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 content is a well-sequenced, actionable workflow with a strong sub-agent prompt template. Its main weakness is redundancy: the Evaluation Criteria section duplicates the comparison criteria, and there is no explicit validation step for sub-agent outputs.

Suggestions

Delete the 'Evaluation Criteria' section (or fold its two unique points — deep-vs-shallow module framing and the over-generalization caveat — into the 'Compare Designs' step) to remove the near-verbatim duplication of the comparison criteria.

Replace the vague 'Don't let sub-agents produce similar designs - enforce radical difference' with a concrete checkpoint, e.g., after generation, verify each design has a different primary trade-off before presenting; regenerate any that overlap.

Name the actual sub-agent tool used by the harness (e.g., 'Agent tool' instead of 'Task tool') so the instruction is directly executable.

DimensionReasoningScore

Conciseness

The body is mostly lean (checklist, prompt template, criteria lists), but the "Evaluation Criteria" section repeats interface simplicity, general-purpose, implementation efficiency, and depth nearly verbatim from the "Compare Designs" step, and re-explains deep-vs-shallow modules. This fits the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor rather than the minor-trimming anchor 4.

3 / 5

Actionability

The sub-agent prompt template with per-agent constraint assignments ("Agent 1: 'Minimize method count...'") and a specified output format is concrete and near copy-paste ready, and the requirements checklist gives executable questions. Minor gaps (references a "Task tool" that may not match the harness, placeholders left undefined) keep it below the fully-executable anchor 5.

4 / 5

Workflow Clarity

The five steps (gather, generate, present, compare, synthesize) are clearly sequenced, with the synthesize step acting as a user feedback loop and the anti-patterns section guarding failure modes. However, there is no checkpoint verifying the outputs (e.g., how to actually enforce that sub-agent designs are radically different), so it sits at 'most checkpoints present; minor validation gaps' rather than anchor 5.

4 / 5

Progressive Disclosure

A single self-contained file with clear section headers and no nested references, so navigation is easy. The skill is ~94 lines (above the under-50-line simple-skill exception), and the duplicated comparison/evaluation criteria could be consolidated, which fits the 'good structure; minor organization gaps' anchor.

4 / 5

Total

15

/

20

Passed

Description

86%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: concise, third-person, with an explicit trigger clause containing natural synonyms and a distinctive hook phrase. The main gap is that only the design-generation action is described, leaving the comparison and synthesis capabilities unstated.

DimensionReasoningScore

Specificity

"Generate multiple radically different interface designs for a module using parallel sub-agents" names the domain and one concrete action with its mechanism, but the description omits the compare, present, and synthesize capabilities the skill actually performs. Anchor 4 requires several specific actions; this is closer to '1-2 concrete actions, not comprehensive'.

3 / 5

Completeness

Both questions are explicitly answered: the "what" is generating radically different interface designs via parallel sub-agents, and the "when" clause lists concrete trigger phrases. It clearly matches the anchor for explicitly answering both with concrete triggers, not the level-4 anchor where 'when' could be more specific.

5 / 5

Trigger Term Quality

"Use when user wants to design an API, explore interface options, compare module shapes, or mentions 'design it twice'" covers the natural phrasings and their synonyms, including the distinctive book phrase. This matches the comprehensive-synonyms anchor; no natural variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

"Design it twice", "explore interface options", and "compare module shapes" carve out a clear niche, but "wants to design an API" could also fire for general API-building/architecture requests where a single design is wanted. Minor overlap risk with closely related skills fits anchor 4 rather than the minimal-conflict anchor 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
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.