CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

testing-conventions

Use when adding or changing tests, the e2e harness, fake CLIs in pipeline-step tests, test process isolation, or CI test sharding.

Quality

74%

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/testing-conventions/SKILL.md
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.

An unusually dense, expert-level conventions document: every rule is actionable, environment-specific, and backed by named regression tests, with no filler or basic-concept padding. Its main weakness is structure — the two longest topics (Windows CI sharding, the macOS Go race bug) are inlined as single monolithic bullets instead of being split into referenced files.

Suggestions

Move the Windows CI sharding details and the macOS Go 1.26 race-bug diagnostics into separate reference files (e.g. references/windows-ci.md, references/macos-race-bug.md), keeping a one-line rule plus a pointer in SKILL.md.

Trim historical narrative such as issue numbers and timeout-growth history, or consolidate it into a short 'rationale' note in the reference file.

De-duplicate the 'Regressions:' test lists at the end of long bullets where the same test names are already cited inline.

DimensionReasoningScore

Conciseness

Nearly every token carries non-inferable repo-specific fact (env var names, package paths, shard topology, regression test names) with zero explanation of concepts Claude already knows. Minor trimmable material remains — issue-number history ('steps grew back to the 15m timeout in issue #1580, daemon/gate in #1682') and the trailing regression-test list that repeats names already cited inline — which keeps it at anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Guidance is fully concrete and executable in instruction form: exact env vars (GIT_CONFIG_COUNT, GIT_CONFIG_NOSYSTEM=1, GIT_CONFIG_GLOBAL, NM_HOME, NM_E2E_DAEMON_MAX), commands (make e2e, scripts/e2e.sh), named helpers to copy from (stepstest.Init / LinkFakeCLI, internal/testgit.RealGit), and explicit prohibitions ('Do not re-exec the race-instrumented test binary as those names'). Per the rubric's instruction-skill note, the absence of code blocks is not penalized when guidance is this specific.

5 / 5

Workflow Clarity

This is a conventions list rather than a sequenced workflow, and each rule states the convention, its rationale, and the enforcement test that fails on regression (e.g. shard tests 'fail when a declared test or a first-character probe name runs in zero rows or in more than one'). Rules are unambiguous with named enforcement checkpoints (anchor 4), but there is no guided sequence across the many topics, so it does not reach anchor 5.

4 / 5

Progressive Disclosure

No bundle files exist and all content is inlined in one SKILL.md under only two section headers. The ~350-word Windows sharding bullet and the ~250-word macOS Go toolchain-bug diagnostic are self-contained topics that clearly belong in separate reference files, matching anchor 3 ('content that should be separate is inline'). It is not anchor 2 because the headers and per-topic bullets do provide genuine structure.

3 / 5

Total

16

/

20

Passed

Description

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

A highly specific, low-conflict trigger description that clearly signals when to use the skill, but it omits any statement of what the skill provides, leaving the 'what' half of the description implicit. Adding a brief capability clause before the 'Use when' clause would make it complete.

Suggestions

Add a 'what' clause before the trigger, e.g. 'Repository conventions for writing and maintaining tests: ... Use when adding or changing tests...'.

Include a few natural trigger variations such as 'unit tests', 'flaky tests', or 'Windows CI' to broaden keyword coverage.

Optionally name the toolchain/domain once (Go test conventions) so the scope is explicit rather than inferred from the trigger list.

DimensionReasoningScore

Specificity

The description enumerates concrete, domain-specific objects ('the e2e harness', 'fake CLIs in pipeline-step tests', 'test process isolation', 'CI test sharding'), but the only action stated is the generic 'adding or changing', so the skill's actual behaviors are never named. This lists several specific items with minor gaps (anchor 4) rather than just 1-2 concrete actions (anchor 3).

4 / 5

Completeness

The description is entirely a 'Use when...' trigger clause: the 'when' is explicit and concrete, but no 'what' is stated anywhere — what the skill does or contains is only inferable. This matches anchor 2 ('only when is present without what') exactly, and scoring only what is explicit rules out anchor 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

Phrases like 'adding or changing tests', 'e2e harness', and 'CI test sharding' are ones a developer would naturally say when needing this skill. Coverage is good but misses common variations such as 'unit tests', 'flaky tests', or 'test suite', placing it at anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Triggers are tightly scoped to this codebase's testing infrastructure ('fake CLIs in pipeline-step tests', 'CI test sharding', 'test process isolation'), forming a clear niche with minimal overlap risk against any other skill. Unambiguous anchor 5.

5 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

kunchenguid/no-mistakes

Path

.agents/skills/testing-conventions/SKILL.md

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.