CtrlK
BlogDocsLog inGet started
Tessl Logo

test-before-ship

Use this skill when implementing a new feature or fixing a bug. Write or update tests before marking the task done. Never consider code complete without verifying it works through automated tests.

73

Quality

91%

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

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-organized instruction set that gives concrete test-writing guidance without wasting tokens on concepts Claude already knows. It fully satisfies the rubric for a simple, single-purpose instruction skill.

DimensionReasoningScore

Conciseness

The body is lean with no concept-explanation padding (it does not explain what tests are or how frameworks work); every line earns its place and assumes Claude's competence.

3 / 3

Actionability

Instruction-only but concrete and specific: "add a regression test that reproduces the bug before fixing it", a fail-when-broken validation check, and named anti-patterns; the scoring note permits absence of code for actionable instruction-only skills.

3 / 3

Workflow Clarity

As a simple single-purpose skill under 50 lines, its single action (write tests before marking done) is unambiguous, and the bug-fix branch gives a clear reproduce-before-fix sequence with an implicit verify step; the simple-skills carve-out applies.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references and no bundle files, the content is organized into clearly labeled sections; the under-50-lines carve-out applies, so well-organized sections alone score 3.

3 / 3

Total

12

/

12

Passed

Description

82%Weight 40%Scale 1-3

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 and concisely states both what the skill does and when to use it, with natural trigger terms. Its main weakness is that the activation triggers are broad coding scenarios, which risks overlapping with general coding skills.

Suggestions

Tighten the "when" trigger to a more distinctive condition (e.g., "Use when finishing a feature or bug fix and about to mark it complete") to reduce overlap with general coding skills.

Add one more concrete action to raise specificity, such as naming the verification step explicitly (e.g., "run the test suite and confirm it passes before marking done").

DimensionReasoningScore

Specificity

Names the testing domain and concrete actions ("Write or update tests", "verifying it works through automated tests") but does not enumerate multiple distinct specific actions as a score-3 example does.

2 / 3

Completeness

An explicit "Use this skill when..." clause supplies the trigger (when) while the rest states what to do (write/update tests, verify), matching the score-3 example structure.

3 / 3

Trigger Term Quality

"implementing a new feature", "fixing a bug", and "automated tests" are exactly the natural phrases a user would say when they need this skill, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The testing mandate is a clear niche, but the broad "when" triggers (implementing a feature / fixing a bug) fire on nearly any coding task, creating overlap with general coding skills.

2 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
aiming-lab/MetaClaw
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.