perl-patterns

Modern Perl 5.36+ idioms, best practices, and conventions for building robust, maintainable Perl applications. Use when writing or reviewing modern Perl 5.36+ code.

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 findings from the security scan

Quality

Content

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

The body is a strong, actionable reference with lean, executable examples and clear topical sections. Its main gap is progressive disclosure: it is a long monolithic file with no external references or split-out detail files.

Suggestions

Move the large configuration blocks (.perltidyrc, .perlcriticrc, cpanfile) and the Quick Reference / Anti-Patterns tables into reference files under ./references/ and link to them from the body.

Trim pedagogical asides Claude already knows (e.g., "a core Perl concept", "a core Perl concept") to lift conciseness toward 5.

Add a short numbered workflow for the most common task (e.g., modernize a legacy script: add `use v5.36` -> convert subs to signatures -> swap two-arg open -> lint with perlcritic) with a validation checkpoint.

Dimension	Reasoning	Score
Conciseness	Largely lean code-with-terse-captions, with only minor over-explanation (e.g., "a core Perl concept", "replaces the old boilerplate") that could be trimmed.	4 / 5
Actionability	Extensive copy-paste-ready, executable code across signatures, dereferencing, OO, regex, file I/O, and tooling config, covering the common modern-Perl cases.	5 / 5
Workflow Clarity	A well-organized topical catalog with clearly labeled sections; not a sequenced multi-step process, but structure is clear and no destructive/batch workflow requires validation checkpoints.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inlined in a ~500-line file; section structure is decent but bulk reference material (perlcritic config, cpanfile, idiom tables) that could live in separate files is not split out.	3 / 5
	Total	16 / 20 Passed

Description

82%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 strong: it states a clear niche, gives concrete trigger guidance, and is third-person. Its only weakness is that the listed actions lean abstract ('idioms', 'best practices') rather than naming concrete operations.

Suggestions

Replace abstract action terms ('idioms, best practices, conventions') with one or two concrete verbs (e.g., 'apply signatures, write Moo classes, refactor legacy Perl').

Add a couple of natural synonyms to the trigger clause (e.g., 'Perl scripts', 'Perl modules') to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and action-areas ("idioms, best practices, and conventions for building robust, maintainable Perl applications") but the actions are abstract rather than concrete verbs like 'extract' or 'refactor'.	3 / 5
Completeness	Explicitly answers both what (idioms, best practices, conventions for robust maintainable Perl apps) and when (writing or reviewing modern Perl 5.36+ code) with a concrete trigger clause.	5 / 5
Trigger Term Quality	"Use when writing or reviewing modern Perl 5.36+ code" supplies natural phrases users would say, though a few synonyms (Perl scripts, Perl modules) are missing.	4 / 5
Distinctiveness Conflict Risk	Version-pinned "modern Perl 5.36+" niche with distinct triggers gives it a clear scope and minimal overlap with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (506 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/perl-patterns/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.