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

—

Does it follow best practices?

Impact

92%

1.17x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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-structured and actionable with executable examples and concrete tooling, but it loses points for restating widely-known testing concepts and for referencing bundle files that are absent. Adding the missing reference/script files would most improve the score.

Suggestions

Create the referenced bundle files (./references/tdd-workflow.md, mocking-strategies.md, test-data-patterns.md, ci-testing.md, and ./scripts/coverage-check.sh) so the signaled navigation actually resolves.

Trim content that restates knowledge Claude already has (e.g., the ASCII test pyramid and the unit/integration/e2e Scope/Speed/Dependencies tables) and keep only the skill-specific guidance that earns its tokens.

If a procedural workflow is intended (e.g., a TDD red-green-refactor cycle), present it as an explicit numbered sequence with validation checkpoints; otherwise clarify that this is a reference catalog.

Dimension	Reasoning	Score
Conciseness	The body uses compact tables and code blocks rather than verbose prose, but it restates concepts Claude already knows (test pyramid, unit/integration/e2e distinctions, AAA, the test-doubles taxonomy), so it is not fully lean; the score-2 anchor fits better than 3.	2 / 3
Actionability	It provides an executable Python AAA example, a concrete naming convention, concrete test-double code snippets, and named tools (WireMock, MSW, VCR, Pact), matching the score-3 'copy-paste ready' anchor rather than the pseudocode score-2 anchor.	3 / 3
Workflow Clarity	This is a reference catalog, not a sequenced procedural workflow; AAA is a sequence and the checklist gives structure, but there are no explicit validation checkpoints or feedback loops, and it is not a single unambiguous task that would qualify for 3.	2 / 3
Progressive Disclosure	The body is well-organized with clearly signaled one-level references in 'Additional Resources' and 'Scripts', but the referenced files (./references/tdd-workflow.md, mocking-strategies.md, test-data-patterns.md, ci-testing.md and ./scripts/coverage-check.sh) do not exist, so navigation is broken and it cannot reach the score-3 'easy navigation' anchor.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 strong: explicit trigger guidance with natural terms gives it high completeness and trigger quality, and the testing niche is distinctive. The only weakness is that the 'what' statement ('strategies and patterns') is somewhat generic rather than listing concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('Cross-language testing strategies and patterns') but does not enumerate multiple concrete actions as the score-3 anchor requires; it is more specific than the vague score-1 example yet not comprehensive.	2 / 3
Completeness	It states what the skill does ('Cross-language testing strategies and patterns') and gives explicit when-guidance via 'Triggers on:', satisfying the score-3 anchor; the explicit trigger clause means it is not capped at 2.	3 / 3
Trigger Term Quality	The 'Triggers on' list (test pyramid, unit test, integration test, e2e test, TDD, BDD, test coverage, mocking strategy, test doubles, test isolation) is a strong set of natural terms a user would actually say, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The testing-specific triggers (TDD, BDD, test doubles, mocking strategy, test isolation) form a clear niche unlikely to fire for unrelated skills, matching the score-3 anchor.	3 / 3
	Total	11 / 12 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
Commit: 26d37ce

Reviewed: 4 days 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.