perl-testing

Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology. Use when writing Perl tests with Test2::V0 or Test::More, or measuring coverage.

Quality

81%

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

71%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 highly actionable, well-structured Perl testing reference with broad executable examples and a clear TDD workflow. It is somewhat verbose in its explanatory prose and does not leverage progressive disclosure — all reference material is inlined in a single long file.

Suggestions

Trim explanatory/persuasive prose such as the 'Why Test2?' bullet list, the description-restating opener, and the closing 'Remember:' line to improve token efficiency.

Split the detailed assertion/building-block catalogs and the prove/coverage command reference into separate reference files (e.g. REFERENCE.md, COMMANDS.md) linked from a concise overview, to apply progressive disclosure.

Add an explicit 'if tests fail during refactor, fix and re-run prove' checkpoint to the TDD workflow to strengthen the feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code-heavy content, but includes unnecessary explanation that could be trimmed: the 'Why Test2?' promotional bullet list, one-line intros like 'The standard Perl testing module — widely used, ships with core', a description-restating opener, and the closing 'Remember:' line.	3 / 5
Actionability	Fully executable, copy-paste ready code and commands covering the common cases — Test2::V0/Test::More assertions, deep comparison builders, mocking, prove invocations, and Devel::Cover coverage commands.	5 / 5
Workflow Clarity	The RED-GREEN-REFACTOR TDD cycle is a clear sequenced workflow with a prove run as a checkpoint; minor gap in that error-recovery guidance when tests fail during refactor is only implicit.	4 / 5
Progressive Disclosure	Well-organized with clear headers and a quick-reference table, but it is a ~470-line monolithic file with no external references; detailed assertion catalogs and command references that could live in separate files are inlined.	3 / 5
	Total	15 / 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 tools and activities, includes an explicit 'Use when' trigger clause, and carves out a distinct niche. Trigger term coverage is good but could add common file extensions like '.t'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities — 'Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology' — giving comprehensive coverage of the domain's actions and tooling.	5 / 5
Completeness	Explicitly answers both what ('Perl testing patterns using...') and when ('Use when writing Perl tests with Test2::V0 or Test::More, or measuring coverage') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage including natural terms users say ('writing Perl tests', 'measuring coverage') plus framework names, but missing common synonyms/file extensions like '.t' files or 'test coverage'.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Perl testing with named frameworks/tools) with distinct triggers and minimal overlap risk with non-Perl testing skills.	5 / 5
	Total	19 / 20 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
Path: skills/perl-testing/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.