CtrlK
BlogDocsLog inGet started
Tessl Logo

spike

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

64

Quality

76%

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

85%

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 lean, well-sequenced, actionable process skill with a strong verdict template and clear workspace guidance; its only real weakness is the appended PilotDeck migration metadata, which is noise relative to skill execution.

Suggestions

Remove the 'PilotDeck Migration Note' section (and its platform-specific temp path) from the operational skill body, or relocate it to non-skill review metadata.

Consider adding a one-line explicit validation/retry note in the Loop (e.g., if research shows the approach is not credible, restart at the Question step) to make the feedback loop explicit.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the trailing 'PilotDeck Migration Note' (a platform-specific temp path and review metadata) is non-operational noise that does not earn its place, fitting the 'mostly efficient but could be tightened' anchor.

2 / 3

Actionability

It gives a concrete 5-step loop, a copy-paste verdict template, explicit workspace paths (`.tmp/openclaw-spikes/<slug>`, `spikes/<NNN-slug>/`), and a concrete avoid-list; as an instruction-only skill the guidance is fully actionable.

3 / 3

Workflow Clarity

The numbered Loop is a clear sequence with an explicit 'Stress: try one edge case or failure mode' checkpoint and a verdict gate, matching the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references, and is organized into well-labeled sections, so progressive disclosure scores 3 per the simple-skills note.

3 / 3

Total

11

/

12

Passed

Description

67%

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 is specific and occupies a distinct niche, but it omits any explicit 'when to use' trigger guidance and lacks natural user phrasing, which together cap completeness and trigger-term quality at 2.

Suggestions

Add a 'Use when...' clause with natural triggers such as 'spike this', 'quick prototype', 'is this possible', or 'compare A/B' to the frontmatter description.

Include common user variations ('prototype', 'feasibility check', 'proof of concept') alongside the existing domain keywords to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Run throwaway prototypes to validate feasibility, compare approaches, and report a verdict" lists multiple concrete actions (validate, compare, report), matching the 'lists multiple specific concrete actions' anchor rather than the partial score-2 anchor.

3 / 3

Completeness

It clearly answers 'what' but contains no 'Use when...' trigger guidance, which per the rubric guidelines caps completeness at 2; it is not a 1 because the 'what' is strong.

2 / 3

Trigger Term Quality

Domain keywords like 'throwaway prototypes' and 'compare approaches' are present, but no natural user phrasing ('spike this', 'quick prototype') is included, so it sits at 'some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

Feasibility-spike/prototyping is a clear niche with distinct intent unlikely to trigger the wrong skill, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

10

/

12

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.