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

—

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

Content

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/Laravel standards comprehensively with good structure and many useful code examples. Its main weaknesses are redundancy between the main content and the Quick Reference section, and several incomplete sections that promise examples but don't deliver them. The content would benefit from deduplication and completing the stub sections.

Suggestions

Complete the stub sections (Class Structure, Strings & Formatting, Enums, Translations) with actual code examples showing the correct patterns, or remove the trailing colons that imply examples should follow.

Remove the Quick Reference section's duplicated content — either make it a standalone cheat sheet in a separate file or eliminate the redundant earlier sections.

Add concrete before/after examples for 'typed properties over docblocks' and 'constructor property promotion' to make those rules fully actionable.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but has some redundancy — several conventions are stated twice (e.g., typed properties over docblocks appears in both 'Type Declarations' and 'Quick Reference'; splitting compound if conditions appears in both 'Control Flow' and 'Code Quality Reminders'). The Quick Reference section largely duplicates earlier content. Some sections like Comments include explanatory prose that could be tightened.	2 / 3
Actionability	Many sections provide concrete code examples (control flow, docblocks, validation, artisan commands), but several sections are incomplete — 'Class Structure', 'Strings & Formatting', 'Enums', and 'Translations' list bullet points with colons but no actual code examples following them. Some guidance like 'Use typed properties, not docblocks' lacks a before/after example showing the correct pattern.	2 / 3
Workflow Clarity	This is a conventions/style guide skill rather than a multi-step workflow skill. The single purpose — applying coding conventions — is unambiguous. Sections are clearly organized by topic with specific rules that are easy to follow sequentially. No destructive or batch operations require validation checkpoints.	3 / 3
Progressive Disclosure	The content is reasonably well-organized with clear section headers, but it's a long monolithic document (~250 lines) with no references to external files. The Quick Reference section at the end duplicates earlier content rather than serving as a concise entry point. Some sections (like the detailed docblock rules) could be split into a separate reference file.	2 / 3
	Total	9 / 12 Passed

Description

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 fails to specify concrete actions the skill enables and lacks any explicit trigger guidance for when Claude should use it. The mention of PHP, Laravel, and Spatie provides some domain specificity but is insufficient for reliable skill matching.

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 compliance.'

Replace 'Describes guidelines' with specific concrete actions, e.g., 'Enforces Spatie's PHP and Laravel coding conventions including class structure, naming conventions, route definitions, Eloquent usage patterns, and test organization.'

Include natural trigger terms users would say, such as 'coding standards', 'best practices', 'code style', 'clean code', 'refactor', or specific Spatie package names.

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

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: ef5ffa0

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.