CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-tests

Instructions and hints for writing tests.

60

Quality

68%

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 ./.agents/skills/writing-tests/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is an exemplar of concise, judgment-focused instruction that respects token budget and assumes Claude's intelligence. Its only gap is the absence of a concrete worked example to anchor the abstract rules.

Suggestions

Add one short worked example (e.g. a function with an early guard and a test using input that would also fail a later check) to lift actionability to fully executable.

Optional: label each bullet with the scenario it governs (layer selection, early-rejection, cross-boundary regression) so the guidance is even quicker to navigate.

DimensionReasoningScore

Conciseness

Four lean lines with no concept explanation; every bullet earns its place and the skill assumes Claude's competence, matching the lean-and-efficient anchor.

5 / 5

Actionability

Specific, actionable judgment guidance (e.g. "use input that would fail a later check") is present, but there are no concrete worked examples illustrating the rules, leaving minor gaps.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill with unambiguous guidance and no destructive or batch operations, so the simple-skill exception applies and the single action is clear.

5 / 5

Progressive Disclosure

Under 50 lines, no external references needed, and well-organized under a clear section header, so the simple-skill exception allows a top score.

5 / 5

Total

19

/

20

Passed

Description

45%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 is concise and grammatically clean but vague: it states a domain without concrete actions or any "Use when" trigger guidance. It would not reliably surface for the right moment nor distinguish itself from other test-related skills.

Suggestions

Add concrete actions, e.g. "Choose the right test layer, design early-rejection test inputs, and decide when to add integration or end-to-end coverage."

Append a "Use when..." trigger clause naming natural phrases like "writing tests", "unit tests", "regression tests", or "test coverage".

Narrow the niche to lower conflict risk, e.g. frame it around test-layer selection rather than test-writing in general.

DimensionReasoningScore

Specificity

Names the domain ("writing tests") but the only action is the generic "Instructions and hints" with no concrete capabilities listed, matching the anchor where actions are minimal or generic.

2 / 5

Completeness

Has a clear "what" (instructions/hints for writing tests) but no "when"/trigger clause at all; per the guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"writing tests" is a relevant natural phrase, but no synonyms or common variations (e.g., unit tests, regression tests, test coverage, test suite) are included, leaving common variations missing.

3 / 5

Distinctiveness Conflict Risk

"writing tests" is somewhat specific but very broad and lacks distinct trigger phrases, so it could still overlap with other test-related skills.

3 / 5

Total

11

/

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
chattocorp/chatto
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.