Tessl • The management layer for AI agent skills

SkillPublic

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

78%

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

Fix and improve this skill with Tessl

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

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.

A highly actionable, executable skill body with a clear first-steps workflow and almost no padding. Its main structural weakness is that it is a monolithic ~535-line single file: the ten full code patterns should be split into referenced files with a lean overview in SKILL.md.

Suggestions

Split the 'Essential Patterns' code examples into references/ files (e.g. references/patterns.md, references/testing.md, references/queues.md) and keep only a short quick-start pattern inline, linked with clear one-level-deep pointers.

Remove duplication: drop the opening blockquote that repeats the description, fold Prerequisites into the frontmatter compatibility field it duplicates, and reconcile 'First Steps' step 3 ('composer install') with the already-run create-project scaffold.

Add an error-recovery loop after the health-endpoint check (e.g. 'if /up fails, check DB_* settings in .env and re-run php artisan migrate') to strengthen the workflow's validation checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence — no explanations of what Laravel or Eloquent is, and nearly every token is executable code or a command. Minor trims remain: the opening blockquote repeats the frontmatter description verbatim, Prerequisites duplicates the frontmatter compatibility field, and 'First Steps' re-covers scaffold-adjacent steps ('composer install' after create-project already installs), so it is not a 5.	4 / 5
Actionability	Fully executable, copy-paste-ready content covering the common cases: scaffold commands, a complete model/migration/factory/seeder set, form request validation, API resource, controller, Sanctum routes, a queue job with dispatch examples, and four realistic Pest tests — specific examples cover the common cases exactly as the 5 anchor requires.	5 / 5
Workflow Clarity	'First Steps After Scaffold' gives a clear numbered sequence with a verification checkpoint (key:generate, migrate, then 'Verify the health endpoint: curl http://localhost:8000/up'), and the scaffold commands form a coherent sequence. It stops short of 5 because there is no error-recovery guidance (what to do if migrate or /up fails) and no validation checkpoint around riskier operations like migrate:fresh --seed.	4 / 5
Progressive Disclosure	The file is well-sectioned with clear headers, but there is no bundle at all (no references/, scripts/, or assets/) — roughly 400 lines of complete pattern examples that belong in one-level-deep reference files are inlined in SKILL.md. This sits between the 2 anchor (content that clearly belongs in separate files is inlined) and the 4 anchor (most content appropriately placed), closer to the middle: good internal structure, but the split across files is missing entirely.	3 / 5
	Total	16 / 20 Passed

Description

70%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.

A specific, distinctive description with good natural trigger terms for the Laravel ecosystem, but it answers only 'what' and never 'when' — adding an explicit 'Use when...' clause would lift its weakest dimension and make it a complete 5-anchor description.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating or extending a Laravel 11.x project, or when the user mentions Laravel, artisan commands, Eloquent models, migrations, or Pest tests.'

Broaden natural keyword coverage with common user phrasings such as 'artisan', 'migrations', 'Blade', and 'PHP web app' to strengthen trigger matching.

Consider naming one or two concrete actions beyond scaffold/develop (e.g. 'run Pest tests, register middleware in bootstrap/app.php') so specificity rests on actions, not only a tech list.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates specific capabilities ('Eloquent ORM, queue workers, API resources, Sanctum auth, and Pest testing'), but the verbs are limited to 'Scaffold and develop' — the specificity comes from a technology list rather than a comprehensive set of concrete actions, which keeps it below the 5 anchor.	4 / 5
Completeness	The 'what' is clearly stated (scaffold and develop a Laravel 11.x app with the listed stack), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because 'when' is entirely absent rather than merely implicit-and-weak.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Laravel', 'Eloquent', 'Sanctum', 'Pest', 'queue workers') with good coverage, but misses common variations users might use such as 'artisan', 'migrations', 'PHP project', or 'Blade', so it falls short of the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche (Laravel 11.x application development) with distinct triggers like 'Sanctum auth' and 'Pest testing' that no adjacent skill (generic PHP, Symfony, WordPress) would claim, so conflict risk is minimal.	5 / 5
	Total	16 / 20 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: achreftlili/deep-dev-skills
Path: backend-php/laravel-project-starter/SKILL.md
Revision: 181fcbc

Reviewed: 7 days ago

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.

laravel-project-starter

Table of Contents

Is this your skill?