CtrlK
BlogDocsLog inGet started
Tessl Logo

testing-principles

Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.

68

Quality

83%

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

82%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 a lean, well-organized set of testing principles that assumes competence and gives concrete, directive rules with a clear TDD workflow and verification steps. Its main limitation is the absence of worked examples that would make the guidance fully concrete for an instruction-only skill.

Suggestions

Add one or two short worked examples (e.g., a tiny Arrange-Act-Assert test and a mock-at-I/O-boundary snippet) to lift actionability toward fully executable guidance.

Include a brief checklist for the TDD cycle and regression-test addition so the workflow has an explicit feedback/re-run checkpoint beyond the VERIFY step.

Consider splitting the Data Layer Testing detail into a short reference section or file if the skill grows, to keep the overview lean.

DimensionReasoningScore

Conciseness

The body is dense, principle-driven, and free of padding or basic concept explanations (e.g., it never explains what a test is); every line states a rule that earns its place, assuming Claude's competence.

5 / 5

Actionability

Guidance is concrete and directive ("Structure each test as Arrange, one Act, and Assert", "Mock direct external I/O boundaries", "Each test creates and cleans up its own state"), but as an instruction-only skill it lacks illustrative examples that would push it to fully copy-paste-ready clarity.

4 / 5

Workflow Clarity

The TDD cycle is explicitly sequenced with a verify checkpoint ("RED ... GREEN ... REFACTOR ... VERIFY: run the repository's applicable regression checks"), and regression guidance includes re-running characterization evidence; the overall skill is a principle collection rather than one workflow, so it stops short of the checklist-driven 5.

4 / 5

Progressive Disclosure

Content is organized into clearly labeled sections (TDD, Quality Requirements, Test Design Rules, Mock and Boundary Rules, Data Layer Testing, Verification Requirements, Test Organization, Regression Testing) with no nested references and appropriate single-level structure; it sits at the boundary of the simple-skill exception rather than cleanly qualifying for 5.

4 / 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.

The description is well-crafted, explicitly covering both capabilities and use-when triggers in third person with concrete, natural language. It is comprehensive and distinct, with only minor room for additional synonyms and more action-oriented verbs.

DimensionReasoningScore

Specificity

Names the domain plus four concrete capability areas ("TDD, test quality, coverage standards, and test design patterns"), giving specific coverage with only minor gaps; not a 5 because these are topics rather than fully enumerated concrete actions.

4 / 5

Completeness

It explicitly answers both what ("Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns") and when ("Use when writing tests, designing test strategies, or reviewing test quality") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"Use when writing tests, designing test strategies, or reviewing test quality" supplies natural phrases users would say, but omits common synonyms like "unit tests" or "test coverage" that would warrant a 5.

4 / 5

Distinctiveness Conflict Risk

"Language-agnostic testing principles" carves a clear niche with distinct triggers and low conflict risk, but the broad testing domain still allows minor overlap with language-specific testing skills, keeping it just below 5.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
shinpr/claude-code-workflows
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.