CtrlK
BlogDocsLog inGet started
Tessl Logo

prototype

Build a throwaway prototype to flush out a design before committing. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".

74

Quality

93%

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

86%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 tight, well-organized instruction-only skill that assumes Claude's competence and provides concrete commands and naming conventions. The main weakness is that the executable branch detail lives in referenced files not present in this bundle, leaving minor actionability gaps in the body itself.

Suggestions

Inline a one-line minimal runnable example for each branch (e.g. a tiny terminal-app skeleton and a one-route UI scaffold) so the body is actionable even before opening LOGIC.md/UI.md.

Add an explicit verification checkpoint before the 'Delete or absorb when done' step (e.g. 'Confirm the question is answered and the verdict is captured before deleting').

Ensure the referenced LOGIC.md and UI.md files ship in the skill bundle so the well-signaled links are not dead ends.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every line earns its place ('A prototype is throwaway code that answers a question. The question decides the shape.').

5 / 5

Actionability

Mostly concrete guidance with specific commands ('pnpm <name>, python <path>, bun <path>') and naming ('PROTOTYPE — wipe me'), but the actual branch execution detail is deferred to referenced LOGIC.md/UI.md, leaving minor gaps in the body itself.

4 / 5

Workflow Clarity

Clear sequence (pick a branch → build per shared rules → surface state → when done, capture and delete/absorb) with a 'surface the state after every action' checkpoint; minor validation gaps before the destructive delete step keep it just below a 5.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to [LOGIC.md](LOGIC.md) and [UI.md](UI.md), content appropriately split into overview, shared rules, and a 'when done' section.

5 / 5

Total

18

/

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.

A highly specific, well-structured description that crisply states the skill's purpose, its two-branch routing, and an explicit 'Use when' clause with concrete trigger phrases and direct user quotes. Third-person/imperative voice is used throughout with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions with comprehensive coverage: 'Build a throwaway prototype', 'a runnable terminal app for state/business-logic questions', 'several radically different UI variations toggleable from one route'.

5 / 5

Completeness

Explicitly answers both what ('Build a throwaway prototype…Routes between two branches') and when ('Use when the user wants to prototype…or says "prototype this", "let me play with it", "try a few designs"') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and direct user quotes: 'prototype', 'sanity-check a data model or state machine', 'mock up a UI', 'explore design options', 'prototype this', 'let me play with it', 'try a few designs'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (throwaway prototyping) with distinct triggers and minimal overlap risk with other skills; the two-branch framing is highly specific.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
belchman/claude-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.