testing-patterns

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

Quality

43%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

64%

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

This skill excels at concise, well-structured reference material for testing principles using efficient tables and visual hierarchy. However, it lacks executable code examples that would make it immediately actionable, and reads more as a reference guide than a skill that teaches Claude how to perform specific testing tasks.

Suggestions

Add concrete, executable code examples for at least unit tests and mocking (e.g., Python pytest or JavaScript Jest examples showing the AAA pattern in practice)

Include a brief workflow section showing the step-by-step process for writing a test from scratch, with validation checkpoints

Consider splitting detailed sections (like mocking strategies or test data patterns) into separate reference files with clear links from the main skill

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient use of tables and visual hierarchy. No unnecessary explanations of concepts Claude already knows; every section delivers actionable principles without padding.	3 / 3
Actionability	Provides clear principles and guidelines but lacks executable code examples. The content describes what to do (e.g., 'Use factories', 'Mock external APIs') without showing concrete implementation in any language.	2 / 3
Workflow Clarity	The testing pyramid and setup/teardown phases provide some workflow structure, but there's no explicit step-by-step process for writing tests or validation checkpoints. The content is more reference-oriented than workflow-oriented.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but it's a monolithic document with no references to external files for deeper dives on specific topics like mocking strategies or integration test examples.	2 / 3
	Total	9 / 12 Passed

Description

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is essentially a topic list rather than a functional skill description. It lacks concrete actions Claude would perform, provides no explicit trigger guidance for when to use the skill, and uses abstract terms like 'patterns and principles' instead of actionable capabilities.

Suggestions

Add concrete actions describing what Claude does, e.g., 'Writes unit tests, creates integration test suites, implements mock objects and test doubles'

Add a 'Use when...' clause with trigger terms like 'write tests', 'test coverage', 'mock this dependency', 'TDD', 'test-driven'

Include common variations and file patterns users might mention: 'test files', '.test.js', '.spec.ts', 'pytest', 'jest', 'testing framework'

Dimension	Reasoning	Score
Specificity	The description uses abstract language like 'patterns and principles' and 'strategies' without listing concrete actions. It names a domain (testing) but doesn't describe what Claude actually does with it.	1 / 3
Completeness	The 'what' is very weak (no concrete actions described) and there is no 'when' clause or explicit trigger guidance. It's essentially a topic list rather than a functional description.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('unit', 'integration', 'mocking') that users might say, but missing common variations like 'test', 'tests', 'mock', 'stub', 'TDD', 'test-driven', or specific frameworks.	2 / 3
Distinctiveness Conflict Risk	Testing is a specific domain which provides some distinctiveness, but the vague phrasing could overlap with general coding skills or documentation skills that also mention testing.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: lchenrique/politron-ide
Commit: 7114206

Reviewed: 5 months 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.