testing-patterns

Cross-language testing strategies and patterns. Triggers on: test pyramid, unit test, integration test, e2e test, TDD, BDD, test coverage, mocking strategy, test doubles, test isolation.

1.17x

Quality

63%

Does it follow best practices?

Impact

92%

1.17x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xdarkmatter/claude-mods/testing-patterns/SKILL.md

Quality

Content

57%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 well-organized and provides a usable, executable AAA example and a clear test-doubles table, but it spends tokens explaining well-known concepts and, critically, all referenced reference/script files are missing from the bundle, breaking progressive-disclosure navigation.

Suggestions

Ship the referenced bundle files (./references/tdd-workflow.md, mocking-strategies.md, test-data-patterns.md, ci-testing.md and ./scripts/coverage-check.sh) or remove the dangling references.

Trim definitional padding Claude already knows (the test-pyramid diagram and the Scope/Speed/Dependencies rows for unit/integration/e2e) in favor of novel, opinionated guidance.

Add an explicit lightweight workflow for applying these patterns (e.g. pick test type -> name with convention -> structure with AAA -> verify isolation) with a validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is mostly tabular and lean, but it re-explains concepts Claude already knows (the test pyramid, definitions of unit/integration/e2e tests, and stub/mock/spy/fake/dummy definitions). Matches the score-3 anchor of mostly efficient with some unnecessary explanation; not a 4 because several sections are definitional padding rather than novel guidance.	3 / 5
Actionability	Provides concrete, executable guidance: a complete AAA Python example, a test naming convention with worked examples, a test-doubles table with real syntax snippets, and isolation options. Matches score 4 (mostly executable guidance with concrete code, minor gaps); not a 5 because much of the body is descriptive reference material rather than copy-paste-ready procedures covering common cases.	4 / 5
Workflow Clarity	This is a patterns/reference skill with no sequenced multi-step workflow or validation checkpoints; sections are organized but lack an explicit ordered process. The score-3 anchor (sequence present but checkpoints missing/implicit) fits best; the destructive/batch cap does not apply since no risky operations are involved, but the absence of any workflow keeps it from scoring higher.	3 / 5
Progressive Disclosure	The body is well-structured with a dedicated "Additional Resources" and "Scripts" section giving one-line descriptions of one-level-deep references. However, the referenced files (./references/*.md and ./scripts/coverage-check.sh) do not exist in the bundle, so the navigation is broken; per the guideline to score against the actual bundle structure, this drops it to 3 rather than 4.	3 / 5
	Total	13 / 20 Passed

Description

68%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 has strong trigger guidance and a distinct niche, but its statement of capability is abstract ("strategies and patterns") rather than listing concrete actions. Explicit "Triggers on:" phrasing is a notable strength.

Suggestions

Replace the abstract "Cross-language testing strategies and patterns" with concrete capabilities, e.g. "Design test suites, choose test types, structure mocks and test doubles, and plan test coverage."

Add a few missing natural trigger terms such as "test fixtures", "test suites", and "flaky tests" to round out keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Cross-language testing strategies and patterns") but lists no concrete actions or capabilities, only an abstract domain label. This matches the score-2 anchor ("Names the domain but actions are minimal or generic"); it is not a 3 because no specific verbs/actions are enumerated, and not a 1 because the domain is clearly identified.	2 / 5
Completeness	It answers both "what" (cross-language testing strategies and patterns) and "when" (explicit "Triggers on:" list), which places it at score 4. It is not a 5 because the "what" is abstract rather than enumerating concrete capabilities, and not a 3 because explicit trigger guidance is present (the guideline caps completeness at 3 only when trigger guidance is missing).	4 / 5
Trigger Term Quality	An explicit "Triggers on:" list gives strong natural terms with synonyms (test pyramid, unit/integration/e2e test, TDD, BDD, test coverage, mocking strategy, test doubles, test isolation). Good coverage but a few natural variations are missing (e.g. test fixtures, test suites), so it falls just short of the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche (cross-language testing patterns) with a distinct, specific trigger list means minimal conflict risk with unrelated skills. Matches the score-5 anchor of a clear niche with distinct triggers.	5 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

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: NeverSight/skills_feed
Path: data/skills-md/0xdarkmatter/claude-mods/testing-patterns/SKILL.md
Commit: 2f57aec

Reviewed: about 21 hours ago

Table of Contents

Discovery Implementation Validation

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.