prototype

Build a throwaway prototype to flesh out a design before committing to it. 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".

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, actionable, well-sequenced body that respects token budget and gives concrete branching guidance. The main gap is progressive disclosure: the two referenced branch files (LOGIC.md, UI.md) are not present in the bundle, leaving broken navigation.

Suggestions

Add the missing LOGIC.md and UI.md bundle files referenced in the 'Pick a branch' section, or inline the branch guidance directly into SKILL.md.

If keeping the references, confirm the file paths resolve relative to the skill bundle directory so the links are not broken.

Consider a one-line note in each branch entry describing what the referenced file contains, so the overview remains useful even before the files are opened.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: 'A prototype is throwaway code that answers a question. The question decides the shape.' It assumes Claude's competence, adds no padding, and does not explain concepts Claude already knows. Every line earns its place.	3 / 3
Actionability	Gives concrete, specific guidance: 'Use the repo's Bun script or a direct `bun <path>` command', 'switchable via a URL search param and a floating bottom bar', 'a local file with a clear "PROTOTYPE: wipe me" name'. As an instruction-only skill the guidance is actionable with concrete mechanisms, satisfying the rubric's code-vs-instruction note.	3 / 3
Workflow Clarity	Clear sequence: pick a branch (with an explicit ambiguity fallback: 'default to whichever branch better matches the surrounding code... state the assumption'), six shared rules, then 'When done'. Includes a checkpoint ('Surface the state... after every action') and a closing capture/delete loop.	3 / 3
Progressive Disclosure	The body signals one-level-deep references to [LOGIC.md] and [UI.md] with clear branch routing, which is good structure, but neither file exists in the bundle, so the navigation is broken. This falls below the level-3 'easy navigation' anchor; not level 1 because the structure and signaling are sound.	2 / 3
	Total	11 / 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.

A strong, third-person description that concisely states the capability, the two-branch routing, and a rich set of natural trigger phrases. It clearly answers both what and when with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'Build a throwaway prototype', 'Routes between two branches: a runnable terminal app... or several radically different UI variations toggleable from one route'. Matches the level-3 anchor of multiple specific concrete actions, not the level-2 single-domain phrasing.	3 / 3
Completeness	Explicitly answers both what (throwaway prototype with two branches) and when via a full 'Use when the user wants to prototype...' clause. Clearly meets the level-3 anchor with explicit triggers, not merely implied.	3 / 3
Trigger Term Quality	Good coverage of natural phrases users would say: 'prototype this', 'let me play with it', 'try a few designs', 'mock up a UI', 'explore design options', 'sanity-check a data model or state machine'. These are genuine user utterances, not jargon.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (throwaway prototyping routing between a terminal logic app and UI variations) with distinct triggers unlikely to fire for unrelated skills. Not generic enough to overlap with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: EpicenterHQ/epicenter
Path: .agents/skills/prototype/SKILL.md
Commit: cb12bcc

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.