php-guidelines-from-spatie

Describes PHP and Laravel guidelines provided by Spatie. These rules result in more maintainable, and readable code.

Quality

56%

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

Fix and improve this skill with Tessl

tessl review fix ./config/claude/skills/php-guidelines-from-spatie/SKILL.md

Quality

Content

63%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 well-structured, actionable PHP/Laravel standards reference with strong good/bad code examples, but it is inflated by a duplicated Quick Reference/Code Quality section, several empty-colon bullets, and no progressive disclosure despite its length.

Suggestions

Remove or consolidate the duplicated 'Quick Reference' > 'Code Quality Reminders' section, which restates rules already covered in the topic sections above.

Complete the empty bullets that end in a colon with no example (e.g. 'String interpolation over concatenation:', 'Use PascalCase for enum values:', 'Use __() function over @lang:') with a short code snippet each.

Move the bulkier reference material (e.g. full docblock rules, quick-reference tables) into a referenced file such as REFERENCE.md and keep SKILL.md as a lean overview, enabling one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Individual rules are terse and assume Claude's knowledge, but the 'Quick Reference' and 'Code Quality Reminders' sections largely restate rules already given above (naming conventions, early returns, constructor promotion, string interpolation), adding duplicated content that could be trimmed — fitting 'Mostly efficient but includes some unnecessary... could be tightened'.	3 / 5
Actionability	Rules are concrete with copy-paste-ready good/bad PHP examples (control flow, docblocks, artisan output) covering common cases; minor gaps come from bullets ending in a colon with no example ('String interpolation over concatenation:', 'Use PascalCase for enum values:').	4 / 5
Workflow Clarity	As a clear, well-organized single-purpose reference it qualifies for the simple-skill exception, with a guiding 'Core Laravel Principle' up top and topical sections; it stays below 5 because the duplicated sections and absence of any guidance on when/how to apply the rules leave minor organizational gaps.	4 / 5
Progressive Disclosure	All ~270 lines live inline in SKILL.md with no bundle/reference files, so the >50-line simple-skill exemption to score 5 does not apply; headers give some structure, but sizable reference material (docblock rules, quick reference) stays inline with no one-level-deep references, matching 'Some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

48%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 identifies the skill's domain clearly and in third person, but it lacks explicit trigger guidance and offers only generic actions, capping completeness and specificity. It is reasonably distinctive thanks to the Spatie attribution.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when writing or reviewing PHP/Laravel code and the user references Spatie's guidelines, coding standards, or conventions.'

Replace the generic verbs with concrete actions the skill performs, e.g. 'Enforces Spatie's PHP/Laravel coding standards covering class structure, docblocks, control flow, and naming conventions.'

Include common synonyms ('coding standards', 'conventions', 'best practices') in the description itself, not just tags, to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('PHP and Laravel guidelines provided by Spatie') but the only 'actions' are the generic 'Describes... guidelines' and 'result in more maintainable, and readable code' — no concrete actions like formatting, enforcing PSR-12, or scaffolding are listed, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It clearly states what the skill does ('Describes PHP and Laravel guidelines provided by Spatie') but provides no 'Use when...' or equivalent trigger guidance; per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	'PHP', 'Laravel', and 'Spatie' are natural terms a user would say, but the description misses common synonyms such as 'coding standards', 'conventions', or 'best practices' (which only appear in tags), so coverage has relevant keywords but is missing variations.	3 / 5
Distinctiveness Conflict Risk	The 'provided by Spatie' attribution carves a clear niche with minimal conflict risk, though 'PHP and Laravel guidelines' could still overlap with generic Laravel coding-standards skills, fitting 'Mostly distinct; minor overlap risk'.	4 / 5
	Total	12 / 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: freekmurze/dotfiles
Path: config/claude/skills/php-guidelines-from-spatie/SKILL.md
Commit: a7899fe

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.