CtrlK
BlogDocsLog inGet started
Tessl Logo

phpunit-test-naming

Enforces grammatically correct, intention-revealing PHPUnit test method names

61

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/phpunit-test-naming/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tight, highly actionable convention guide with executable examples, a verification audit command, and a validation checklist, all well-organized into clear sections without padding.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's PHP/PHPUnit competence with no concept padding; minor redundancy (the authorized_user examples recur in both the ✅ Correct list and the it_user smell section) keeps it just below a 5.

4 / 5

Actionability

Provides fully executable, copy-paste-ready PHP examples, a runnable grep audit command, a fix table mapping bad names to corrected ones, and a concrete writing checklist.

5 / 5

Workflow Clarity

A single-purpose naming skill with an unambiguous action, an explicit 5-point writing checklist as a validation checkpoint, and a verification audit command; the simple-skill exception applies and no destructive/batch operation is involved.

5 / 5

Progressive Disclosure

Self-contained, well-organized with clear section headers (Rule, Correct, Wrong, Smell, Attribute, Checklist, Audit), and needs no external references; no bundle files exist, and the structure is easy to navigate.

5 / 5

Total

19

/

20

Passed

Description

53%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 specific and distinctive about a narrow PHPUnit naming niche, but it states only the "what" and omits an explicit "Use when..." trigger clause, leaving completeness and trigger-term quality at the mid-level anchors.

Suggestions

Append an explicit "Use when..." clause to the description (e.g., "Use when writing, reviewing, or renaming PHPUnit test methods") to raise completeness above 3.

Add natural trigger keywords users would say ("test names", "naming tests", "renaming tests") rather than relying only on the formal action phrasing.

Enumerate concrete actions (e.g., "enforces, audits, and renames test method names") to broaden capability coverage toward the higher specificity anchors.

DimensionReasoningScore

Specificity

Names the domain ("PHPUnit test method names") and one concrete action ("Enforces...naming") but does not list several specific actions, fitting the 1-2-actions anchor rather than the comprehensive 4/5 anchors.

3 / 5

Completeness

Provides a clear "what" but no "when"/"Use when..." clause in the description (trigger guidance lives in the separate frontmatter `triggers` field), which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Contains relevant keywords ("PHPUnit", "test method names") but lacks the natural phrasings a user would actually say (e.g., "naming tests", "renaming test methods"), matching the some-keywords-missing-variations anchor.

3 / 5

Distinctiveness Conflict Risk

A clearly distinct niche (PHPUnit test-method naming) with minimal conflict risk, though the description alone lacks the explicit trigger phrasing that would push it to a 5.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Bottelet/DaybydayCRM
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.