CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-audit

Audit existing tests for low-value, duplicated or implementation-coupled cases and the test-only code they keep alive, then remove or rewrite them on evidence. /test-audit full covers the whole suite and also lists public contracts no test guards. Use for test-audit, /test-audit <scope>, /test-audit full, a test sweep, or pruning tests. Not for writing a new test; the project's Tests rule gates that.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 dense, expert-oriented audit methodology with excellent sequencing, evidence requirements, and validation feedback loops for its destructive operations. Its weaknesses are structural: the whole method lives monolithically in SKILL.md with no progressive disclosure, the scripts its proofs rely on are named rather than supplied, and the LICENSE link is dangling.

Suggestions

Move the Junk patterns catalog and Evidence-tier proof details into references/ files, keeping SKILL.md to the bar, the workflow, and clearly signaled one-level pointers.

Ship the Shape/Duplicate member-listing and matching scripts in scripts/ (or inline minimal runnable versions) so the tier proofs are executable as written rather than described.

Fix or remove the dangling [LICENSE](LICENSE) link: include the LICENSE file in the bundle or state the license attribution in plain text.

DimensionReasoningScore

Conciseness

The body is dense expert prose with no padding and no explanations of concepts Claude already knows ("A dead-code tool in production mode, such as `knip --production`, lists them"), but keep/cut rules recur across "The bar", "Junk patterns", "Retention bar" and "Evidence tiers" — internal entries are defined in both "The bar" and the Internal tier — and several multi-clause sentences could be tightened. Not 5: minor redundancy across sections; not 3: almost every token earns its place.

4 / 5

Actionability

Concrete procedures and named tools throughout ("Prove the first edit by mutating a scratch copy of the owner so the behavior breaks, and run the test", `knip --production`, a `git grep` of each name, the project's delete-by-title codemod), and validation steps name what to run. Not 5: the Shape and Duplicate proofs depend on listing/matching scripts that are described but never provided or sketched; not 3: the guidance is specific and executable, not high-level hints.

4 / 5

Workflow Clarity

A numbered discovery sequence with explicit validation gates ("Report the evidence before editing", prove both edits on scratch copies), a Validate section with feedback loops ("Run each rewritten test against its named mutant and see it fail, and against its named refactor and see it pass"), and a per-candidate checklist with a readiness rule ("a missing field means it is not ready"). Not 4: checkpoints are explicit for every destructive or batch edit, including full-suite mode's ledger-resume protocol.

5 / 5

Progressive Disclosure

Internally well-structured with clear sections and anchor links, but the entire methodology — a 16-item junk-pattern catalog, tier proof rules, and the Full-mode ledger protocol — is inlined in a single ~115-line SKILL.md with no references/ split, and the one external link, [LICENSE](LICENSE), does not resolve to a file in the bundle. Not 4: reference-grade catalogs clearly belong in separate files; not 2: the structure is good and nothing is buried.

3 / 5

Total

16

/

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 description: third-person, concrete about every capability mode, with an explicit trigger list covering command invocations and natural phrases, plus a clear exclusion boundary. The only weakness is moderate synonym coverage in the trigger terms.

DimensionReasoningScore

Specificity

"Audit existing tests for low-value, duplicated or implementation-coupled cases... then remove or rewrite them on evidence" plus "lists public contracts no test guards" names multiple concrete actions covering audit, removal, rewriting, and gap listing. Not 4: the actions cover all of the skill's modes with no minor gaps.

5 / 5

Completeness

Explicitly answers what ("Audit existing tests... remove or rewrite them on evidence", "lists public contracts no test guards") and when, with a concrete "Use for..." trigger list and an explicit exclusion ("Not for writing a new test; the project's Tests rule gates that"). Not 4: the when-clause is explicit with concrete trigger phrases, not merely present-but-improvable.

5 / 5

Trigger Term Quality

"Use for test-audit, /test-audit <scope>, /test-audit full, a test sweep, or pruning tests" gives good natural triggers including command forms, but common phrasings users might say such as "delete tests", "test cleanup", or "remove duplicate tests" are missing. Not 5 (synonym coverage is incomplete); not 3 (more than just "some relevant keywords" — both command forms and natural phrases are present).

4 / 5

Distinctiveness Conflict Risk

Clear niche — auditing and pruning existing tests — with distinct triggers, and the main overlap risk (test-writing skills) is explicitly disclaimed by "Not for writing a new test". Not 4: the primary confusion vector is directly fenced off.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

udecode/plate

Path

.agents/skills/test-audit/SKILL.md

Reviewed

Table of Contents

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.