testing-patterns

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

Quality

66%

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

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is exceptionally concise and well-organized into scannable tables, but it is reference-style rather than instructional: it lacks executable examples, explicit validation checkpoints, and any link to the bundled test_runner.py script.

Suggestions

Add at least one executable code snippet (e.g. a minimal AAA unit test or a mocking example) to lift actionability from descriptive to copy-paste-ready.

Reference the bundled scripts/test_runner.py from the body (e.g. 'For running tests and coverage, see [test_runner.py](scripts/test_runner.py)') so progressive disclosure is one level deep and signaled.

Add an explicit validation/feedback checkpoint for risky operations, such as 'run the suite, fix failures, re-run until green', to reach a workflow_clarity of 3.

Dimension	Reasoning	Score
Conciseness	The body is lean and table-driven, assuming Claude's competence with no explanatory padding about what testing is; every section earns its place and an ASCII pyramid conveys the concept compactly.	3 / 3
Actionability	It offers concrete tabular guidance (AAA steps, mock types, naming patterns) but provides no executable code or commands and several entries are terse labels rather than copy-paste-ready instruction, fitting the 'some concrete guidance but incomplete' anchor.	2 / 3
Workflow Clarity	Setup/teardown phases and test-type selection imply a sequence, but there are no explicit validation checkpoints or feedback loops for batch/destructive testing operations, which the rubric caps at 2.	2 / 3
Progressive Disclosure	The SKILL.md is well-sectioned but a scripts/test_runner.py bundle exists yet is never referenced or signaled from the body, so navigation to the deeper material is missing rather than clearly one-level-deep.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 answers both what and when with a usable trigger clause, but it relies on abstract phrasing ('and principles') and only modest keyword coverage, keeping specificity and trigger quality mid-range.

Suggestions

Drop vague filler like 'and principles' in favor of concrete actions, e.g. 'Write and structure unit, integration, and end-to-end tests; choose mocking strategies.'

Broaden trigger terms to include natural phrasings users say, such as 'test coverage', 'fixtures', 'test doubles', 'stubbing', 'flaky tests'.

Sharpen distinctiveness by naming a unique angle (e.g. test pyramid, AAA pattern) so it does not overlap with general coding-quality skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('Testing patterns and principles') and a few areas (Unit, integration, mocking strategies) but does not list multiple concrete actions like a 3-anchor requires; 'and principles' is abstract padding.	2 / 3
Completeness	The description gives the what ('Testing patterns and principles. Unit, integration, mocking strategies.') and an explicit when clause ('When writing unit tests, integration tests, choosing testing frameworks, or implementing mocking strategies.'), satisfying both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	'unit tests, integration tests, testing frameworks, mocking strategies' are relevant natural terms, but coverage lacks common variations users would say (e.g. 'test coverage', 'stubbing', 'fixtures', 'test doubles').	2 / 3
Distinctiveness Conflict Risk	Testing is a clear niche, but the description is somewhat generic and could overlap with general coding/quality skills; it lacks a sharply distinct trigger set that would prevent overlap.	2 / 3
	Total	9 / 12 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: 04514f0

Reviewed: about 11 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.