CtrlK
BlogDocsLog inGet started
Tessl Logo

php-guidelines-from-spatie

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

53

Quality

60%

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 ./config/claude/skills/php-guidelines-from-spatie/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

The content is a well-organized, mostly actionable style reference with strong code examples, weakened by a few stub bullets lacking examples and by repetition between the main sections and the Quick Reference. Filling in the empty example blocks and de-duplicating would raise both actionability and conciseness.

Suggestions

Complete the bullets that end with a colon but have no example — add concrete PHP snippets for string interpolation, enum PascalCase, typed properties, and one-trait-per-line.

De-duplicate the "Quick Reference" / "Code Quality Reminders" sections against the earlier detailed sections, or convert the Quick Reference into a true one-line summary table that points back to the detailed sections.

Tighten the repeated rules (early returns, avoid else, split compound ifs appear twice) so each rule is stated once and cross-referenced if needed.

DimensionReasoningScore

Conciseness

The body is dense and bullet-driven with almost no explanatory filler, but the "Quick Reference" and "Code Quality Reminders" sections restate rules already covered earlier (typed properties, early returns, constructor promotion, avoid else, split compound ifs), which is avoidable repetition.

2 / 3

Actionability

Most rules are backed by concrete, executable PHP examples, but several bullets are left abstract with an empty trailing colon and no example — e.g. "String interpolation over concatenation:", "Use PascalCase for enum values:", "Use typed properties, not docblocks:", and "One trait per line:" — so guidance is incomplete there.

2 / 3

Workflow Clarity

This is a single-purpose style-reference skill rather than a multi-step process, and its single action (apply these rules to PHP/Laravel code) is unambiguous and well-organized, which the rubric allows to score 3 for simple skills; no destructive or batch workflow requires validation checkpoints.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is one well-sectioned file with a Quick Reference summary, but at ~270 lines it is monolithic and the summary section duplicates earlier content rather than splitting detail into one-level-deep references.

2 / 3

Total

9

/

12

Passed

Description

57%

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 to a clear niche but is missing an explicit usage trigger and concrete action verbs, leaving the "when to use" half implicit. Adding a "Use when writing or reviewing PHP/Laravel code" clause would lift the completeness and trigger-term dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing or reviewing PHP or Laravel code, or when the user asks for Spatie-style coding standards."

Replace the descriptive verb "Describes" with concrete actions such as "Applies" or "Enforces" to convey what Claude will do.

Add natural trigger terms users actually say, such as "coding standards", "style guide", and "code review".

DimensionReasoningScore

Specificity

The description names the domain ("PHP and Laravel guidelines provided by Spatie") but only describes content ("Describes ... guidelines"), not concrete actions Claude will perform such as applying, enforcing, or reviewing code, so it is not fully specific.

2 / 3

Completeness

It answers "what" (PHP and Laravel guidelines) but provides no "Use when..." trigger, so the "when should Claude use it" half is missing; per the rubric a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

It includes real terms ("PHP", "Laravel", "Spatie", "maintainable, and readable code") but omits common natural phrasings a user would say, such as "coding standards", "style guide", or "code review", so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The Spatie/Laravel/PHP niche is narrow and clearly distinguishable from other skills, and the stated focus is unlikely to trigger for the wrong skill.

3 / 3

Total

9

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
freekmurze/dotfiles
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.