laravel-project-starter

Scaffold and develop a Laravel 11.x application with PHP 8.3+, Eloquent ORM, queue workers, API resources, Sanctum auth, and Pest testing.

Quality

71%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./backend-php/laravel-project-starter/SKILL.md

Quality

Content

77%

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

This is a strong, actionable Laravel starter skill with excellent code examples that are immediately executable. The main weaknesses are verbosity (explaining concepts Claude knows, like what models and factories are) and lack of progressive disclosure for what is a very long document. The workflow guidance is clear for a scaffolding/reference skill.

Suggestions

Remove explanatory comments like 'HTTP controllers', 'Eloquent models', 'Queueable jobs' from the project structure - Claude knows what these are

Split into multiple files: keep SKILL.md as a quick-start overview, move detailed patterns to PATTERNS.md and testing examples to TESTING.md

Trim the Key Conventions section - statements like 'One model per database table' and 'Never commit .env' are Laravel basics Claude already knows

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some content Claude already knows (basic project structure explanations, what factories/seeders are). The code examples are valuable but the surrounding explanations could be tighter.	2 / 3
Actionability	Excellent executable code examples throughout - complete model, migration, factory, controller, test, and job implementations that are copy-paste ready. Commands are specific and immediately usable.	3 / 3
Workflow Clarity	Clear 'First Steps After Scaffold' sequence with numbered steps. The scaffold command sequence is explicit. For a reference/starter skill, the workflows are appropriately clear without needing validation loops since operations are non-destructive.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but this is a monolithic 400+ line file that could benefit from splitting advanced patterns (jobs, testing, integration) into separate reference files. No external file references are provided.	2 / 3
	Total	10 / 12 Passed

Description

64%

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 excels at specificity and trigger term quality with comprehensive Laravel ecosystem terminology and concrete capabilities. However, it critically lacks a 'Use when...' clause, which is essential for Claude to know when to select this skill over others. The technical depth is strong but the missing trigger guidance significantly limits its effectiveness for skill selection.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to build a Laravel application, work with Eloquent models, set up API authentication, or write Pest tests.'

Include common user phrasings such as 'Laravel project', 'PHP web app', 'REST API with Laravel', or 'authentication setup' to improve selection accuracy.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and technologies: 'Scaffold and develop', 'Eloquent ORM', 'queue workers', 'API resources', 'Sanctum auth', and 'Pest testing' - all concrete, actionable capabilities.	3 / 3
Completeness	While the 'what' is well-defined (scaffold and develop Laravel apps with specific features), there is no 'Use when...' clause or equivalent explicit trigger guidance explaining when Claude should select this skill.	1 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'Laravel 11.x', 'PHP 8.3+', 'Eloquent', 'queue workers', 'API resources', 'Sanctum', 'Pest testing' - these are all terms developers naturally use when working with Laravel.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with specific version numbers (Laravel 11.x, PHP 8.3+) and Laravel-specific terminology (Eloquent, Sanctum, Pest) that clearly distinguishes it from generic PHP or web development skills.	3 / 3
	Total	10 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (535 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: achreftlili/deep-dev-skills
Commit: 181fcbc

Reviewed: 4 months 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.