pest-control

Enforces PHPUnit-only testing in this project. Activates when writing tests, reviewing test files, or when any Pest syntax appears (it(), test(), describe(), uses(), expect() chains, beforeEach/afterEach hooks). Scans for and eliminates all Pest references from code, config, and documentation.

Quality

94%

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

87%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 content is lean, executable, and well-structured, with concrete code and a thorough conversion table. Its main weakness is that the batch Pest-elimination workflow in Rule 6 lacks explicit verification/validation checkpoints, capping workflow clarity.

Suggestions

Add a final verification step to Rule 6's checklist, e.g. run the test suite (phpunit) after conversion and grep the repo for residual 'pest' references to confirm none remain.

Include a feedback loop in the elimination workflow: if tests fail after conversion, fix the converted test and re-run before proceeding.

Consider adding a brief 'verify imports' checkpoint ensuring no `use Pest\...` or `pest.php` bootstrap remains after the config/tooling steps.

Dimension	Reasoning	Score
Conciseness	The body is lean: rules are stated as imperatives with executable code and no padding about what PHPUnit/Pest are or why testing matters. The conversion table is dense and token-efficient, assuming Claude's competence.	5 / 5
Actionability	Provides copy-paste-ready PHP for test class patterns, attributes, assertions, and Livewire testing, plus explicit file placement and a full Pest→PHPUnit conversion table covering common cases.	5 / 5
Workflow Clarity	Rule 6 is a well-sequenced multi-step checklist across composer.json, test files, config/tooling, and docs, but this batch/destructive elimination workflow lacks explicit validation checkpoints (e.g. run phpunit, grep for residual pest references), which caps the score at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed; the ~180-line body is well organized into clearly headed sections (Rules 0–7) with no nested references, satisfying the simple-skill exception for a 5.	5 / 5
	Total	18 / 20 Passed

Description

100%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 concise, concrete, and fully answers both what the skill does and when it activates, with trigger terms a developer would naturally encounter. It occupies a clear niche with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete actions—'Enforces PHPUnit-only testing', 'Scans for and eliminates all Pest references from code, config, and documentation'—with comprehensive coverage across scopes.	5 / 5
Completeness	Explicitly answers both what ('Enforces PHPUnit-only testing') and when ('Activates when writing tests, reviewing test files, or when any Pest syntax appears') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes the exact natural triggers users encounter—'writing tests', 'reviewing test files', and Pest syntax tokens (it(), test(), describe(), uses(), expect(), beforeEach/afterEach)—with comprehensive coverage of syntax-level synonyms.	5 / 5
Distinctiveness Conflict Risk	The PHPUnit-only / Pest-elimination niche has distinct, specific triggers ('any Pest syntax appears') with minimal overlap risk against other skills.	5 / 5
	Total	20 / 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: Bottelet/DaybydayCRM
Path: .claude/skills/pest-control/SKILL.md
Commit: 2199c1e

Reviewed: 14 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.