CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prototype

Answer a design or feasibility question with explicitly throwaway spike code — never committed, findings recorded in the diary or an ADR draft. Use when a decision is blocked on "would X even work?" (library capability, API behavior, performance shape). Not for building features — that's /tdd via /implement.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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-structured skill body: concrete rules with rationale, an executable procedure, and specific artifacts and paths. The only meaningful improvement is trimming the repetition of the throwaway invariant across the intro, rules, and procedure, and adding a checkpoint for inconclusive spikes.

DimensionReasoningScore

Conciseness

Lean and assumes competence, but the core invariant (spikes are throwaway, never promoted) is stated three times — intro paragraph, rule 2, rule 6 — and Procedure steps 1 and 4 restate rules 1 and 5. Minor redundancy keeps it below 'every token earns its place'.

4 / 5

Actionability

Instruction-only skill with fully concrete guidance: specific locations (session scratchpad or $TMPDIR), specific artifact (dated docs/diary.md entry with question, verdict, evidence, surprises), version citation, a worked falsifiable-question example, and deletion of the spike dir. No code is needed for this skill type.

5 / 5

Workflow Clarity

Clear 4-step Procedure with a pre-flight gate (check primary docs first) and timebox failure handling (rule 3), but no explicit checkpoint for an inconclusive spike result. Fits 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no bundle files needed, with well-organized Rules/Procedure sections and clean navigation. Per the simple-skill guideline, this scores 5.

5 / 5

Total

18

/

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 description: third-person voice, concrete what/when with a natural quoted trigger phrase, and explicit boundary disambiguation against related skills. The only gaps are a few missing synonyms (prototype, proof of concept) that would make triggers fully comprehensive.

DimensionReasoningScore

Specificity

Names several concrete actions — 'throwaway spike code — never committed, findings recorded in the diary or an ADR draft' — with specific destinations for outputs. Not a 5 because coverage of the capability surface is narrow (single action family), but well above the 1-2-action anchor at 3.

4 / 5

Completeness

Explicitly answers both 'what' (answer a design/feasibility question with throwaway spike code, findings recorded) and 'when' with a concrete quoted trigger phrase ('Use when a decision is blocked on "would X even work?"'), plus an explicit negative boundary ('Not for building features').

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say: 'would X even work?', 'feasibility', 'library capability, API behavior, performance shape'. Missing common synonyms such as 'prototype', 'proof of concept', or 'POC', which keeps it below comprehensive anchor-5 coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche (throwaway feasibility spikes) with distinct triggers and explicit disambiguation from sibling skills ('Not for building features — that's /tdd via /implement'), minimizing wrong-skill triggering.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

agranado2k/google-books-clojure

Path

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