tidy-tests

Use after implementation or refactoring, or during test-quality review, to tidy up tests left behind. Removes temporary or duplicate tests, restores `.only` or `.skip`, or cleans orphaned test resources; not for merely adding tests or running tests. Do not apply mechanically during implementation just because the work follows TDD; use only when the user asks for test-tidying or an explicit test-tidying phase begins.

Quality

90%

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

Quality

Content

88%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 well-structured, highly actionable instruction skill with a clear workflow and validation loop. The main weaknesses are mild repetition and a single-file layout that inlines all examples rather than splitting detail into reference files.

Suggestions

Consolidate the repeated 'do not expand the scope' warnings into a single stated boundary to reduce repetition.

Consider moving the eight worked examples (or the full Report Format template) into a references/ file, keeping SKILL.md as a leaner overview that links one level deep.

Trim the opening context paragraph ('Work can produce tests… This is unavoidable in agentic coding…') to the minimum needed to frame the skill.

Dimension	Reasoning	Score
Conciseness	The novel taxonomy (Throwaway/Regression/Redundant/Complementary Test) and worked examples earn their place, but the scope-expansion warning is repeated several times and a few passages could be tightened.	4 / 5
Actionability	A concrete 5-step procedure, eight worked examples (user instruction → agent action → decision → action), explicit 'ask the user' triggers, and a copy-paste report template give fully actionable guidance.	5 / 5
Workflow Clarity	The procedure is a clear sequenced workflow with an explicit validation feedback loop in step 5 ('Run the affected tests… Fix defects… run the tests again') and decision checkpoints ('Ask the user when…').	5 / 5
Progressive Disclosure	Well-organized into clear sections (Working Mode, Procedure, Decision Criteria and Examples, Report Format) with no nested references, but as a long single-file skill everything is inlined rather than split into a lean overview plus reference files.	4 / 5
	Total	18 / 20 Passed

Description

92%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, specific description that names concrete actions, gives explicit trigger conditions, and sharply delineates the skill from related test work. The only mild gap is keyword synonym breadth.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Removes temporary or duplicate tests, restores `.only` or `.skip`, or cleans orphaned test resources' — giving comprehensive coverage of the skill's domain.	5 / 5
Completeness	Explicitly answers both what ('tidy up tests left behind…') and when ('Use after implementation or refactoring, or during test-quality review', 'use only when the user asks for test-tidying or an explicit test-tidying phase begins').	5 / 5
Trigger Term Quality	Good natural keyword coverage ('test-quality review', 'tidy up tests', 'test-tidying', 'TDD', 'refactoring') but a few common synonyms (e.g. 'clean up tests') are missing and no file extensions apply.	4 / 5
Distinctiveness Conflict Risk	Clear niche with explicit negative boundaries — 'not for merely adding tests or running tests' and 'Do not apply mechanically during implementation just because the work follows TDD' — minimizing overlap with adjacent skills.	5 / 5
	Total	19 / 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: choegyumin/agent-skills
Path: skills/instruction/tidy-tests/SKILL.md
Commit: 62ef4cc

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