code-convention

Apply battle-tested code conventions when writing or modifying code in Laravel/PHP projects (with React/TypeScript frontend support). Use this skill whenever the user is writing a new feature, refactoring existing code, creating a controller/action/migration/model/test, or asks 'how should I structure this', 'what's the convention for X', 'is this the right pattern'. Also use proactively before producing non-trivial code so the output follows conventions the first time instead of needing rewrites.

Quality

87%

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

78%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 highly actionable with concrete PREFERRED/AVOID examples throughout and a usable self-review workflow, and it largely avoids padding with known concepts. Its main weaknesses are the large monolithic size with no progressive disclosure into reference files and rationale sections that could be tightened.

Suggestions

Split the largest sections (e.g., Comments, Frontend/React, Testing) into reference files under references/ and keep SKILL.md as a concise overview with one-level-deep links, improving progressive_disclosure and token efficiency.

Trim the repeated 'Why this matters' rationale blocks to one or two sentences each; the code examples plus a short 'why' already carry the guidance.

Add an explicit validate-fix-retry loop to the pre-PR 'Things Always Worth Catching' pass (e.g., re-run the check after each fix) to lift workflow_clarity.

Dimension	Reasoning	Score
Conciseness	It avoids padding with concepts Claude already knows (no explaining what controllers/enums/REST are) and each rule's rationale is project-specific judgment rather than fluff, but the cumulative volume of 'Why this matters' blocks across many rules could still be trimmed, so it sits above efficient-but-untightened rather than at lean.	4 / 5
Actionability	Every rule pairs PREFERRED/AVOID code in PHP or JSX with real class signatures and method bodies, producing copy-paste-ready examples that cover the common Laravel/frontend cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	A clear 3-step 'How to use this skill' sequence plus a 34-item 'Things Always Worth Catching' self-review pass before a PR gives a real validation checkpoint, but it is a one-shot checklist rather than an explicit validate-fix-retry loop.	4 / 5
Progressive Disclosure	The single file is well-organized into clearly-headed sections, but at ~650 lines with no bundle files and no external references, large tracts that could live in separate reference files are inlined — fitting 'some structure, content that should be separate is inline'.	3 / 5
	Total	16 / 20 Passed

Description

96%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 specific, complete, and rich with natural trigger phrases, cleanly answering both what and when in third person. Its only weakness is a broad proactive-use clause that slightly raises overlap risk with generic coding skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions tied to the domain — 'writing a new feature, refactoring existing code, creating a controller/action/migration/model/test' — covering the Laravel/PHP lifecycle comprehensively, matching the 'lists multiple specific concrete actions' anchor.	5 / 5
Completeness	Explicitly answers both what ('Apply battle-tested code conventions when writing or modifying code in Laravel/PHP projects') and when via a clear 'Use this skill whenever...' clause with concrete trigger phrases and proactive-use guidance.	5 / 5
Trigger Term Quality	Includes verbatim natural phrases users say ('how should I structure this', 'what's the convention for X', 'is this the right pattern') plus concrete artifact types, giving comprehensive coverage of natural terms and synonyms.	5 / 5
Distinctiveness Conflict Risk	The Laravel/PHP + React/TS niche and specific artifact types give it a clear niche, but the broad proactive trigger 'before producing non-trivial code' could overlap with general coding skills, keeping it just below the minimal-conflict anchor.	4 / 5
	Total	19 / 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
skill_md_line_count	SKILL.md is long (651 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: figlabhq/agent-skills
Path: code-convention/SKILL.md
Commit: abac51b

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.