perl-patterns

Modern Perl 5.36+ idioms, best practices, and conventions for building robust, maintainable Perl applications.

Quality

57%

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-patterns/SKILL.md

Quality

Content

65%

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

The skill body is a strong, action-oriented Perl reference packed with executable, copy-paste-ready examples. Its weaknesses are token-efficiency (it restates concepts Claude knows) and a monolithic structure with no progressive disclosure into bundle files.

Suggestions

Trim concept restatements like 'a core Perl concept' and the generic 'How It Works' preamble; assume Claude's knowledge of scalar/list context.

Split large sections (OO with Moo, regexes, tooling configs) into referenced files under references/ and link to them from a concise overview to improve progressive disclosure.

Consider a short validation/verification note for the destructive or security-sensitive patterns (two-arg open, string eval) to raise workflow clarity beyond a pure reference.

Dimension	Reasoning	Score
Conciseness	Most sections are lean executable snippets, but phrases like "Understand scalar vs list context — a core Perl concept" and explanatory preamble in "How It Works" explain concepts Claude already knows, matching the level-2 anchor of mostly efficient with some unnecessary explanation.	2 / 3
Actionability	The body is dominated by complete, executable Perl with concrete Good/Bad pairs (e.g. the `use v5.36` preamble, Moo class, three-arg open) that are copy-paste ready, matching the level-3 anchor for fully executable examples.	3 / 3
Workflow Clarity	A clear "When to Activate" list and well-ordered principle sections provide structure, but this is a reference/patterns skill with no sequenced multi-step workflow or validation checkpoints; it sits at level-2 'steps present but no explicit sequence/checkpoints' rather than level-1's missing structure.	2 / 3
Progressive Disclosure	The file is a single ~500-line monolith with no bundle files; distinct topics (OO, regexes, tooling configs) are inline rather than split into referenced files, fitting the level-2 anchor of some structure but content that should be separate is inline.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 clearly identifies the Perl 5.36+ niche and its focus on idioms and best practices, but it omits an explicit "Use when..." trigger clause and natural user phrasings. It is competent but not as actionable as the top-anchor examples.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers, e.g. 'Use when writing new Perl, refactoring legacy Perl to 5.36+, or reviewing Perl for modern idiom compliance.'

Include concrete actions users would name, such as 'adopts signatures, Moo classes, and three-arg open' to lift specificity toward level 3.

Surface common user phrasings (e.g. 'Perl best practices', 'modern Perl', 'Perl module design') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Quotes "idioms, best practices, and conventions for building robust, maintainable Perl applications" name the Perl domain and some actions, but do not enumerate multiple concrete capabilities, matching the level-2 anchor rather than the level-3 list of specific actions.	2 / 3
Completeness	It states what the skill covers but never says when to use it; per the rubric guidelines a missing "Use when..." clause caps completeness at 2, even though the body later provides trigger guidance.	2 / 3
Trigger Term Quality	The only natural keyword is "Perl"; there is no "Use when..." clause or common user phrasings (e.g. "writing Perl", "refactoring Perl"), so it has some relevant keywords but misses common variations per the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The Perl 5.36+ niche is fairly specific, but without explicit trigger terms the description could still overlap with a generic "coding best practices" skill, fitting the level-2 "somewhat specific but could still overlap" anchor.	2 / 3
	Total	8 / 12 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
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.