testing-patterns

Testing patterns and principles. Unit, integration, mocking strategies.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/testing-patterns/SKILL.md

Quality

Content

50%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 well-structured, compact tabular reference of testing principles, but it largely restates commonly known concepts, includes no executable code examples, and keeps everything monolithic in SKILL.md without signaling the bundled script.

Suggestions

Add a few short, executable test code snippets illustrating the AAA and mocking patterns so the guidance is copy-paste ready.

Reference scripts/test_runner.py from the body (e.g. a 'Run tests' section) so the bundled asset is discoverable.

Trim sections that restate widely known concepts (testing pyramid, FAST principles) to only the non-obvious guidance that earns its tokens.

Dimension	Reasoning	Score
Conciseness	The body is lean in form (compact tables, no padded prose), but much of the substance — testing pyramid, AAA, FAST principles, mock types — restates knowledge Claude already has, so not every token earns its place.	3 / 5
Actionability	Concrete decision rules and thresholds are present (e.g. 'Fast < 100ms each', 'One assert per test', naming patterns), but a code-centric topic ships with zero executable test examples, leaving key details missing.	3 / 5
Workflow Clarity	Sequenced reference patterns exist (AAA: Arrange/Act/Assert; setup/teardown phases) but there is no end-to-end workflow with validation checkpoints, so it sits at the 'steps listed but checkpoints missing' anchor.	3 / 5
Progressive Disclosure	Content is well-organized into 10 numbered sections but is entirely inline in one ~170-line file, and the bundled scripts/test_runner.py is never referenced from the body.	3 / 5
	Total	12 / 20 Passed

Description

57%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 compact and names a clear domain with three relevant sub-areas and natural trigger terms, but it omits an explicit 'Use when...' clause and uses no action verbs, capping completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing unit tests, integration tests, choosing a testing framework, or implementing mocking strategies.'

Replace noun-only phrasing with concrete actions, e.g. 'Write unit and integration tests, choose mocking strategies, and structure test suites.'

Add common synonyms users say ('test framework', 'stub', 'spy', 'fixtures', 'TDD') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the testing domain and enumerates three concrete sub-areas ("Unit, integration, mocking strategies") but uses no action verbs, landing between the 'names domain' (2) and 'domain plus concrete actions' (3) anchors.	3 / 5
Completeness	The description field gives a clear 'what' but contains no 'Use when...' trigger clause, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	"Testing", "Unit", "integration", and "mocking" are natural terms users say, giving good keyword coverage, though synonyms like 'test framework', 'stub', or 'fixtures' are absent.	4 / 5
Distinctiveness Conflict Risk	The broad 'Testing patterns and principles' framing could overlap with many testing-related skills, matching the 'somewhat specific but could still overlap' anchor.	3 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/testing-patterns/SKILL.md
Commit: 211561c

Reviewed: 8 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.