test-expert

Testing methodologies, test-driven development (TDD), unit and integration testing, and testing best practices across multiple frameworks. Use when the user needs to write tests, implement TDD, or improve test coverage and quality.

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 ./claude/skills/test-expert/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.

A thorough, code-rich testing reference that is strong on executable examples but weak on token efficiency and progressive disclosure. It spends heavily restating basic testing concepts Claude already knows and inlines content that would be better split into referenced files.

Suggestions

Trim the explanatory padding for concepts Claude already knows (Test Pyramid ASCII art, FIRST principles, AAA pattern, TDD benefits) and keep only the concrete, non-obvious guidance.

Split language-specific and topic-specific sections (Python/JS/Shell testing, mocking, integration/E2E) into separate reference files linked from a concise overview, improving progressive disclosure.

Replace illustrative stub test bodies (e.g., functions containing only 'pass') with minimal but complete executable assertions so examples are fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The ~414-line body extensively explains concepts Claude already knows (the Test Pyramid ASCII art, FIRST principles, AAA pattern, TDD benefits list, Do's/Don'ts bullets), which is noticeable padding; not a 1 because the concrete code examples do earn their place.	2 / 5
Actionability	Provides mostly executable, copy-paste-ready code across Python (pytest), JavaScript (Jest), and Shell (bats) covering common cases; not a 5 because several examples are illustrative stubs (e.g., test bodies containing only 'pass').	4 / 5
Workflow Clarity	Sequenced processes exist (TDD Red-Green-Refactor, CI workflow steps) but the body is primarily a reference collection rather than a guided workflow, with implicit rather than explicit validation checkpoints.	3 / 5
Progressive Disclosure	Good section headers provide structure, but no bundle files exist and language-specific guides, mocking, and integration sections that clearly belong in separate reference files are all inlined into one long monolithic file.	3 / 5
	Total	12 / 20 Passed

Description

83%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.

A strong, well-structured description that explicitly covers both capabilities and trigger conditions in third person. It is specific and actionable, with only minor gaps in trigger synonyms and some categorical phrasing keeping it just short of exemplary.

Dimension	Reasoning	Score
Specificity	Lists several specific testing domains ('test-driven development (TDD)', 'unit and integration testing', 'testing best practices across multiple frameworks') plus concrete user actions ('write tests, implement TDD, or improve test coverage and quality'), with only minor gaps in coverage; not a 5 because some phrases ('testing methodologies', 'testing best practices') are categories rather than discrete concrete actions.	4 / 5
Completeness	Clearly answers both 'what' (testing methodologies, TDD, unit/integration testing, best practices across frameworks) and 'when' with an explicit 'Use when the user needs to write tests, implement TDD, or improve test coverage and quality' clause containing concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural terms users would say ('write tests', 'TDD', 'test coverage', 'test quality', 'unit and integration testing'); not a 5 because a few natural synonyms (e.g., 'test suite', 'flaky tests', 'testing frameworks') are missing.	4 / 5
Distinctiveness Conflict Risk	The testing niche is mostly distinct with clear triggers, but 'testing best practices across multiple frameworks' is broad enough to risk minor overlap with language-specific testing skills; not a 5 because of that breadth.	4 / 5
	Total	17 / 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: einverne/dotfiles
Path: claude/skills/test-expert/SKILL.md
Commit: 7d18cf4

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.