CtrlK
BlogDocsLog inGet started
Tessl Logo

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.

76

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

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.

A well-structured, lean skill body with a clear sequenced workflow, executable example, and excellent one-level-deep reference navigation. The main gap is that only one framework is demonstrated inline while the rest are referenced.

DimensionReasoningScore

Conciseness

The body is lean: it assumes Claude's competence (no explaining of what mocking or coverage is) and every section — workflow, example, references table, constraints, template — earns its tokens; inline code comments only illustrate enforced patterns.

5 / 5

Actionability

Provides a copy-paste Jest example with happy-path and error-throw cases, concrete MUST DO/MUST NOT rules, and a severity-labeled output template, but only one framework is shown in full while others are deferred to references.

4 / 5

Workflow Clarity

The five-step Core Workflow is clearly sequenced with explicit feedback loops (fail → classify → fix root cause → re-run; flaky → isolate → stabilize) and a verification checkpoint ('Verify coverage targets are met before closing; flag gaps explicitly').

5 / 5

Progressive Disclosure

A well-signaled Reference Guide table maps each topic to a real one-level-deep reference file with a 'Load When' criterion; all 10 referenced files exist in ./references/, and the body stays an overview pointing to detail.

5 / 5

Total

19

/

20

Passed

Description

96%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, specific description that concretely states capabilities and provides rich, natural trigger phrasing across the testing domain. Its only weakness is breadth that slightly raises overlap risk with adjacent specialist skills.

DimensionReasoningScore

Specificity

Lists five concrete actions ('Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports') across functional, performance, and security disciplines — comprehensive and specific rather than vague.

5 / 5

Completeness

Explicitly answers both 'what' (the five generation/analysis actions) and 'when' via a concrete 'Use when ...' clause enumerating trigger scenarios, matching the top anchor.

5 / 5

Trigger Term Quality

Covers natural user phrasings and synonyms ('unit tests, integration tests, or E2E tests', 'flaky tests', 'QA, regression', 'shift-left testing', 'test maintenance') plus tool-level terms (k6, Artillery, OWASP), giving comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

The testing/QA niche is clear and triggers are distinct, but the broad scope (E2E, flaky tests) creates minor overlap risk with closely related skills like playwright-expert and debugging-wizard listed in metadata.

4 / 5

Total

19

/

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
jeffallan/claude-skills
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.