CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prototype

Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Only runs when explicitly invoked; it does not trigger on its own.

Quality

74%

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 ./.agents/skills/prototype/SKILL.md

The canonical home for this skill is prototype in emilkowalski/skills

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 tightly written, well-sequenced instruction skill that earns its tokens and encodes real craft standards, with clear completion criteria and a verification pass before handoff. Its one significant defect is that both the Hard Rules and Phase 4 direct the model to load and copy PICKER.md verbatim, and that file is absent from the bundle, leaving the skill's central artifact unspecified.

Suggestions

Ship PICKER.md alongside SKILL.md (e.g., in references/) containing the picker's exact markup, styles, and keyboard wiring, or inline that spec in Phase 4 if the bundle is meant to stay single-file.

Add an explicit error-recovery loop to Phase 5 (e.g., "if a variant fails to render or throws console errors, fix it and re-flip before presenting") to earn the top workflow-clarity anchor.

Provide a minimal starter for the no-project branch (a skeleton of the self-contained HTML harness) so the standalone path is as executable as the in-project path.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence throughout — motion standards are stated as facts ("sub-300ms UI motion", "transform/opacity only", "never `ease-in`") rather than explained, and there is no padding of known concepts. Every section drives behavior: hard rules are terse imperatives, phases carry exact counts and completion criteria, and the invocation grammar is given as syntax. Re-reading anchor 4, there are no real instances of over-explanation to trim, so the lean anchor fits best.

5 / 5

Actionability

Most guidance is concrete and executable ("an isolated route or page (`/prototypes/<slug>`, or the framework's equivalent)", the invocation-variant table, the defined presentation-table format), but the most load-bearing artifact is delegated to a missing file: "Its exact markup, styles, and behavior are specified in [PICKER.md](PICKER.md) — copy them verbatim" and "load it now and build exactly that" both point at a PICKER.md that does not exist anywhere in the bundle (no references/ directory). That is a missing key detail, matching anchor 3; it is not 4 because the gap breaks a Hard Rule and a phase, and not 2 because the remaining guidance is specific and directive rather than high-level hints.

3 / 5

Workflow Clarity

Six clearly sequenced phases with named checkpoints — "**Completion criterion:** every variant has a name and a stated axis", and Phase 5's "Run the harness. Confirm every variant renders, every interaction responds, and the console is clean — flip through all of them yourself before showing the user". It falls short of anchor 5 only because there is no explicit error-recovery loop (what to do when a variant fails verification); the only destructive step (deleting the prototype surface in Phase 6) is guarded by user selection and Hard Rule 1, so no destructive-operation cap applies.

4 / 5

Progressive Disclosure

The body is well-sectioned and makes the right disclosure move — pushing the bulky picker spec out of SKILL.md to a one-level-deep, prominently signaled reference ("specified in [PICKER.md](PICKER.md)") rather than inlining it. But the bundle listing shows no references/, scripts/, or assets/ directories and no PICKER.md anywhere, so the disclosure chain is broken at its only link, which keeps it at anchor 3 rather than 4–5; it is above 2 because nothing is wrongly inlined and the reference is clearly signaled, not buried.

3 / 5

Total

15

/

20

Passed

Description

66%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 distinctive, concrete description that clearly communicates both what the skill does and that it only runs on explicit invocation, with minimal conflict risk against other skills. Its weaknesses are the second-person voice (which costs it specificity under this rubric) and thin trigger-term coverage — natural synonyms like "prototype" and "mockup" are absent.

Suggestions

Rewrite in third person to remove the second-person constructions (e.g., "Builds multiple genuinely different versions of a described UI piece, rendered behind a visual picker for live comparison, and promotes the chosen variant into the codebase").

Add natural trigger synonyms users would actually say — "prototype", "mockup", "design exploration", "sketch some options" — so the skill's vocabulary matches how it will be requested.

Optionally note what it deliberately does not do (review or fix existing UI) in the description to further sharpen the boundary with sibling skills.

DimensionReasoningScore

Specificity

It lists several concrete actions — "Build multiple genuinely different versions of a UI piece you describe", "rendered behind a visual picker", "flip through them live", "promote the one that feels right" — which would fit anchor 4, but the description is written in second person ("a UI piece you describe", "so you can flip through them live"), and the rubric mandates a 1-point specificity penalty for second-person voice, bringing it to 3.

3 / 5

Completeness

The "what" is clear (build multiple divergent versions of a described UI piece behind a live picker and promote the winner), and the "when" is explicitly stated as "Only runs when explicitly invoked; it does not trigger on its own", which counts as explicit trigger guidance rather than a merely implied one, avoiding the cap at 3. It is not 5 because the when-clause states an invocation mode rather than concrete trigger phrases, fitting anchor 4 (both present, when could be more specific).

4 / 5

Trigger Term Quality

Some natural, relevant terms are present ("versions", "UI piece", "visual picker", "flip through", "promote"), but common variations a user would actually say are missing — notably "prototype", "mockup", and "design exploration", none of which appear even though "prototype" is the skill's own name. This matches anchor 3 (relevant keywords, missing synonyms); it is above 2 because the terms present are natural rather than generic filler, and below 4 because coverage of synonyms is thin.

3 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — divergent UI variant generation with a live visual picker and winner promotion — with distinctive phrases ("genuinely different versions", "visual picker", "promote the one that feels right") that overlap with virtually nothing else, and "Only runs when explicitly invoked" removes accidental-trigger risk entirely. This matches anchor 5 (clear niche, distinct triggers, minimal conflict risk); the body even explicitly fences off sibling skills.

5 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

englishstreetventures/osn

Path

.agents/skills/prototype/SKILL.md

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.