CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

82%

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

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-organized reference with executable examples and useful pitfalls/do-don't lists. Its weaknesses are padding from basic Test::More tutorial content and a monolithic single-file structure where reference material should be split into bundle files.

Suggestions

Move Test::More fundamentals (basic assertions, SKIP/TODO blocks) into a references/ file (or drop them, since Claude already knows this material), keeping SKILL.md focused on Test2::V0 patterns, prove workflows, and coverage.

Split the Devel::Cover section into a references/coverage.md file and keep only the essential commands inline, shrinking the SKILL.md body to a navigable overview.

Add explicit validation checkpoints to the TDD workflow, e.g. 'Step 1 ends only when prove shows the new test failing (red)' and 'do not refactor until prove is fully green'.

DimensionReasoningScore

Conciseness

The body is mostly concrete patterns, but the 'Test::More Fundamentals' section (basic is/ok/is_deeply/like/isa_ok assertions and SKIP/TODO blocks) and the 'Why Test2?' pitch re-teach material Claude already knows, which could be trimmed or cut.

3 / 5

Actionability

Code is copy-paste ready and executable throughout (Test2 builders, dies/lives, prove flags, Devel::Cover commands), and the Quick Reference table covers the common cases compactly.

5 / 5

Workflow Clarity

The RED-GREEN-REFACTOR cycle is explicitly sequenced with run commands, but explicit checkpoints (e.g., 'confirm the test fails before implementing', 'confirm green before refactor') and error-recovery guidance are only implicit.

4 / 5

Progressive Disclosure

Section headers are clear, but ~470 lines are all inline with no bundle files; the Test::More fundamentals and Devel::Cover coverage details clearly belong in separate reference files per the progressive-disclosure rationale.

3 / 5

Total

15

/

20

Passed

Description

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

The description is well-formed: third-person, explicit 'Use when...' triggers, and a specific, distinct Perl-testing niche. Its only weakness is that the 'what' reads as a tool list rather than concrete actions, and a few natural trigger synonyms (TAP, .t files) are absent.

DimensionReasoningScore

Specificity

Names the domain and several concrete capabilities ('prove runner, mocking, coverage with Devel::Cover, and TDD methodology'), but it is a tool inventory phrased as 'patterns using X' rather than action verbs, leaving minor gaps versus a comprehensive action list.

4 / 5

Completeness

Explicitly answers both what ('Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology') 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

'writing Perl tests', 'Test2::V0', 'Test::More', and 'measuring coverage' are phrases users would naturally say, but common variations like 'TAP', '.t files', 'prove', or 'test suite' are missing from the trigger set.

4 / 5

Distinctiveness Conflict Risk

A clear Perl-testing niche gated by language-specific triggers (Test2::V0, Test::More, Devel::Cover); it would not fire for testing work in other languages, so conflict risk is minimal.

5 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

skills/perl-testing/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.