CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

testing

Choose useful regression coverage and apply Epicenter test conventions for setup, Result assertions, type tests, naming, and pruning. Use when writing, reviewing, deleting, or reorganizing tests, especially `*.test.ts` files.

Quality

84%

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.

A well-structured conventions skill that keeps core rules and executable examples inline while deferring depth to five real, condition-mapped reference files one level deep. The main improvement opportunities are trimming minor over-explanations and tightening the abstract coverage-selection prose.

DimensionReasoningScore

Conciseness

The body is efficient — convention rules with tight good/bad example pairs and no padding about concepts Claude already knows — but the caret-annotated naming pattern breakdown and the doc-comment structure template duplicating the good example are minor over-explanations that could be trimmed, placing it just below the lean anchor.

4 / 5

Actionability

Mostly executable guidance: a copy-paste-ready expectOk/expectErr import and usage snippet, a fill-in doc-comment template, concrete file patterns in the splitting table, and specific naming examples. The "Choose useful coverage" section is reasoning prose whose concrete example is deferred to the reference, a minor gap against the fully-executable anchor.

4 / 5

Workflow Clarity

Decision sequences are clear with most checkpoints present: "name the plausible regression it detects and confirm that its setup can expose that failure" before adding tests, and the challenge/response/resolution pruning flow with an explicit escape hatch ("Keeping a test is a valid result"). The convention sections are unambiguous rules, but there is no explicit error-recovery loop, keeping it below the top anchor.

4 / 5

Progressive Disclosure

Clear overview with well-signaled, one-level-deep references: the References section maps each working condition to a specific file ("If working with negative type tests... read references/type-testing.md"), all five referenced files exist with no nested references, and detail is correctly deferred while core conventions stay inline.

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.

A strong description that explicitly states both capability and trigger conditions with concrete, natural language and a distinctive repo-specific niche. Keyword coverage and action specificity are just short of comprehensive, missing a few common synonyms like "unit tests" or "test suite".

DimensionReasoningScore

Specificity

The description lists several specific convention areas — "setup, Result assertions, type tests, naming, and pruning" — plus the concrete action of choosing regression coverage, but only two action verbs cover that enumerated scope, leaving minor gaps versus the comprehensive multi-action anchor at 5.

4 / 5

Completeness

It clearly answers both questions: the "what" is "Choose useful regression coverage and apply Epicenter test conventions for setup, Result assertions, type tests, naming, and pruning" and the "when" is an explicit "Use when writing, reviewing, deleting, or reorganizing tests, especially *.test.ts files" with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Natural user phrases like "writing, reviewing, deleting, or reorganizing tests" plus the "*.test.ts" file extension give good keyword coverage, but common variations such as "unit tests", "test suite", or "bun test" are missing, so it falls just short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

The Epicenter-specific framing ("Epicenter test conventions", wellcrafted "Result assertions") creates a clear niche with low conflict risk, but the fairly broad triggers around writing and reviewing tests leave minor overlap risk with generic testing skills.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

EpicenterHQ/epicenter

Path

.agents/skills/testing/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.