perl-testing

Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/perl-testing/SKILL.md

Quality

Content

77%

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

The content is highly actionable with executable code and a clear TDD workflow, but it is over-long for a single SKILL.md and keeps detail inline rather than splitting it into referenced files. Tightening introductory prose and externalizing reference material would improve both conciseness and progressive disclosure.

Suggestions

Trim explanatory prose Claude already knows (e.g. the 'Why Test2?' bullets and module introductions) to tighten conciseness.

Move detailed API examples (Test2 builders, mocking variants, coverage recipes) into referenced files like REFERENCES.md or EXAMPLES.md, keeping SKILL.md a concise overview with one-level-deep links.

Add a brief validation checkpoint note after coverage runs (e.g. fail CI if total < 80%) to make the coverage feedback loop explicit.

Dimension	Reasoning	Score
Conciseness	The 470-line body includes introductory prose Claude already knows ('The standard Perl testing module — widely used, ships with core', the 'Why Test2?' bullet list, and restated DO/DON'T items), so it is mostly efficient but padded in places.	2 / 3
Actionability	It provides fully executable Perl code, specific prove/cover commands, and a copy-paste Quick Reference table, matching the anchor for fully executable, copy-paste-ready guidance.	3 / 3
Workflow Clarity	The TDD red-green-refactor cycle is a clearly sequenced process with an explicit feedback loop ('Run: prove -lv t/unit/calculator.t'), satisfying the anchor for a clear sequence with validation/feedback steps.	3 / 3
Progressive Disclosure	No bundle files exist and all content is inline in one ~470-line file; material that could be split out (full builder examples, the quick reference) is inline rather than organized into one-level-deep references.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 is specific and distinctive, naming concrete Perl testing tools and methodology with natural trigger terms. Its main weakness is the absence of an explicit 'Use when...' clause, which caps completeness at 2.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when writing or debugging Perl tests, setting up prove/Test2 infrastructure, or reviewing Perl test coverage.'

Include common user phrasings like 'failing Perl tests' or 'Perl test coverage' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capabilities ('Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology') rather than vague language, matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2 rather than 3.	2 / 3
Trigger Term Quality	It includes natural terms a user would actually say ('Perl testing', 'Test::More', 'prove', 'TDD', 'mocking', 'coverage') with good coverage rather than abstract jargon.	3 / 3
Distinctiveness Conflict Risk	Perl testing with these specific tools is a clear niche with distinct triggers that is unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Commit: 754b8dd

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.