CtrlK
BlogDocsLog inGet started
Tessl Logo

exploration-protocol

Structured approach to explore features before production development. Templates for objectives, acceptance criteria, architecture, prototypes, and verification. This skill should be used when the user asks to "explore a feature", "start an exploration", "create a task folder", or mentions exploration protocol.

66

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 skill body is a well-structured overview that delegates detail to real reference templates and provides concrete scaffolding patterns with a clear phased workflow. It is slightly improvable by trimming pattern examples already covered by the templates and adding explicit error-recovery loops.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids restating known concepts; the illustrative 'Key Patterns' examples overlap slightly with the referenced templates and could be trimmed.

4 / 5

Actionability

Gives concrete, copy-ready patterns (folder layout, stub markers, criteria tables, checkpoint lists, ASCII diagrams) and a MUST-read directive pointing to real template files, with only minor gaps in fully executable detail.

4 / 5

Workflow Clarity

The Phase Flow lists a clear six-step sequence with explicit approval gates ('user reviews', 'user approves before work begins', 'stub until criteria approved'), though error-recovery feedback loops are not detailed.

4 / 5

Progressive Disclosure

The body is a concise overview that signals one-level-deep references to the six real template files in ./references/001-example-task/, with content appropriately split and easy navigation.

5 / 5

Total

17

/

20

Passed

Description

83%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 both capability and trigger conditions with concrete, natural-language phrases. It is specific and distinct, with only minor room to add synonyms and tighten the 'structured approach' framing.

DimensionReasoningScore

Specificity

Lists several concrete artifacts (templates for objectives, acceptance criteria, architecture, prototypes, and verification) beyond just naming the domain, though 'structured approach' is slightly abstract, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (structured exploration with templates for five named artifacts) and when (concrete trigger phrases in the 'should be used when' clause), matching the top anchor.

5 / 5

Trigger Term Quality

Provides natural phrases users would say ('explore a feature', 'start an exploration', 'create a task folder', 'mentions exploration protocol'), with good coverage but a few common synonyms (e.g. 'spike', 'investigate') absent.

4 / 5

Distinctiveness Conflict Risk

The 'exploration protocol' niche and its task-folder triggers are mostly distinct, with only minor overlap risk against general project-planning skills.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 6 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
dwmkerr/claude-toolkit
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.