CtrlK
BlogDocsLog inGet started
Tessl Logo

spike

Run throwaway prototypes to validate feasibility, compare approaches, and report a verdict.

56

Quality

63%

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/spike/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, well-structured instruction skill with a clear loop, concrete output shape, and a verdict template; its main weakness is the stray PilotDeck migration/review note, which is process metadata unrelated to using the skill and slightly inflates and disorganizes the body.

Suggestions

Remove the 'PilotDeck Migration Note' section (and its temp filesystem source path) from the shipped SKILL.md — it is review metadata, not skill guidance.

Add an explicit feedback loop after 'Stress' (e.g. 'If the edge case invalidates the approach, adjust the artifact and re-run Stress before the Verdict') to strengthen workflow clarity.

Clarify the slug derivation (e.g. kebab-case of the question) so the workspace path is fully reproducible.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — concrete loop, output shape, anti-patterns — but the trailing 'PilotDeck Migration Note' with a temp filesystem path is review-process noise that could be trimmed.

4 / 5

Actionability

Gives concrete, executable guidance for an instruction skill — specific workspace paths, a verdict enum, and a copy-paste verdict template — with only minor gaps (e.g. no slug rule).

4 / 5

Workflow Clarity

The five-step Loop is clearly sequenced with a 'Stress' edge-case check and a terminal Verdict checkpoint, but there is no explicit error-recovery feedback loop (fail → adjust → retry) to reach a 5.

4 / 5

Progressive Disclosure

Well-organized into clear sections with no external references needed, but at ~52 lines and with an out-of-place 'PilotDeck Migration Note' section it sits just outside the under-50-line simple-skill case that would warrant a 5.

4 / 5

Total

16

/

20

Passed

Description

51%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.

The description clearly states the skill's purpose and concrete actions but omits any explicit 'Use when' trigger guidance, which caps completeness and leaves the natural trigger phrases out of the description itself. Trigger-term coverage is the weakest dimension because the user-facing phrases live in the body rather than the frontmatter.

Suggestions

Add an explicit 'Use when...' clause to the description, e.g. 'Use when the user says spike this, quick prototype, is this possible, or compare A/B.'

Surface the natural trigger keywords (spike, quick prototype, feasibility, compare A/B) directly in the description rather than only in the body.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Run throwaway prototypes', 'validate feasibility', 'compare approaches', 'report a verdict' — with only minor abstraction in 'validate feasibility'; not quite the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

Provides a clear 'what' but no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Contains a couple domain keywords ('prototypes', 'compare approaches') but omits the natural trigger phrases users actually say ('spike this', 'quick prototype', 'is this possible', 'compare A/B'), which only appear in the body.

2 / 5

Distinctiveness Conflict Risk

Targets a clear niche (throwaway feasibility spikes) that is mostly distinct from production build skills, with only minor overlap risk against general 'prototype' or 'build' skills.

4 / 5

Total

13

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
OpenBMB/PilotDeck
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.