php-guidelines-from-spatie

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

Quality

42%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/php-guidelines-from-spatie/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague and passive to be effective for skill selection. It tells Claude that the skill 'describes guidelines' but doesn't specify what concrete actions it enables or when it should be triggered. The inclusion of 'PHP', 'Laravel', and 'Spatie' provides some domain anchoring, but the lack of specific capabilities and explicit trigger conditions makes it weak overall.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when writing PHP or Laravel code, when the user asks about Spatie coding standards, or when reviewing code for style and maintainability.'

Replace 'Describes PHP and Laravel guidelines' with specific actions, e.g., 'Enforces Spatie's PHP and Laravel coding conventions including class design, routing patterns, Blade templating, and Eloquent usage.'

Include natural trigger terms users would say, such as 'code style', 'best practices', 'coding standards', 'clean code', 'refactor', or specific Laravel concepts like 'controllers', 'models', 'migrations'.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'guidelines' and 'rules' without listing any concrete actions. It doesn't specify what the skill actually does beyond 'describes guidelines' — no mention of specific coding patterns, conventions, or actionable capabilities.	1 / 3
Completeness	The 'what' is weak (just 'describes guidelines') and there is no 'when' clause at all. There are no explicit triggers telling Claude when to select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the weak 'what' brings it down to 1.	1 / 3
Trigger Term Quality	It includes some relevant keywords like 'PHP', 'Laravel', and 'Spatie' that users might naturally mention. However, it misses common variations like 'coding standards', 'code style', 'best practices', 'linting', or specific Laravel concepts.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Spatie' provides some distinctiveness, and 'PHP and Laravel' narrows the domain. However, it could still overlap with general PHP coding skills or other Laravel-related skills since 'guidelines' is quite broad.	2 / 3
	Total	6 / 12 Passed

Implementation

62%

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

This is a solid coding conventions skill that covers PHP and Laravel standards comprehensively. Its main weaknesses are internal redundancy (several rules stated multiple times across sections) and incomplete examples for some directives. The structure is logical but the document would benefit from deduplication and either trimming the Quick Reference or making it the primary entry point with details in separate files.

Suggestions

Remove duplicate guidance (typed properties over docblocks, splitting compound && conditions, constructor promotion) — state each rule once and reference it if needed elsewhere.

Add concrete code examples for sections that currently lack them: class structure (constructor promotion, trait usage), enums (PascalCase example), string interpolation, and translations.

Consider extracting the detailed Docblock Rules and Control Flow sections into separate reference files, keeping SKILL.md as a concise overview with links.

Dimension	Reasoning	Score
Conciseness	Generally efficient but has some redundancy — typed properties over docblocks is mentioned three times, the compound if/&& rule appears twice, and the Quick Reference section largely repeats earlier content. Some sections like Comments include explanatory prose that could be tightened.	2 / 3
Actionability	Provides concrete code examples for several conventions (control flow, docblocks, validation, artisan commands), but many sections lack examples entirely (class structure mentions constructor promotion and traits with no code, enums say 'PascalCase' with no example, string interpolation has no example). Some guidance is directive but incomplete.	2 / 3
Workflow Clarity	This is a coding style/convention skill, not a multi-step workflow. The single purpose — follow these conventions when writing PHP/Laravel code — is unambiguous. Sections are clearly organized by topic with specific rules, and no destructive or batch operations are involved.	3 / 3
Progressive Disclosure	Content is reasonably well-structured with clear section headers, but it's a long monolithic document (~200+ lines) with no references to external files for deeper topics. The Quick Reference section at the end partially duplicates earlier content rather than serving as a concise entry point with links to details.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	10 / 11 Passed

Repository: freekmurze/dotfiles
Commit: 05d40bb

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.