Tessl • The management layer for AI agent skills

SkillPublic

symfony-project-starter

Scaffold and develop a Symfony 7.x application with PHP 8.3+, Doctrine ORM, API Platform, Messenger async processing, and Twig templating.

Quality

75%

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/symfony-project-starter/SKILL.md

Quality

Content

71%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 excellent command and code coverage and a verified first-steps sequence. Its weaknesses are token weight from boilerplate accessors and a monolithic single-file layout with no progressive disclosure into reference files.

Suggestions

Trim the Product entity example to fields/attributes plus one or two representative accessors (note 'remaining getters as usual') to cut ~70 lines of boilerplate.

Split extended patterns (entity/service/messenger examples, command catalog) into references/ files (e.g., PATTERNS.md, COMMANDS.md) and link them from the body, keeping SKILL.md as an overview.

Add a short error-recovery note to the first-steps sequence (e.g., re-run migrations after fixing schema errors, check MESSENGER_TRANSPORT_DSN if consuming fails) to add feedback loops around the database/Messenger steps.

Dimension	Reasoning	Score
Conciseness	Almost no conceptual padding — the body is commands and code — but the ~100-line Product entity with full getter/setter boilerplate and the standard ServiceEntityRepository constructor are code Claude generates reflexively and could be trimmed to signatures. More than 'minor' over-length, so anchor 3 rather than 4.	3 / 5
Actionability	Fully executable throughout: copy-paste scaffold commands, complete entity/repository/controller/service/message/handler/config/template/test examples, and a catalog of exact console commands. Matches anchor 5's 'copy-paste ready, covers the common cases'.	5 / 5
Workflow Clarity	'First Steps After Scaffold' is a clear 5-step sequence that ends in an explicit verification checkpoint (open http://localhost:8000/api). Below 5 because there is no error-recovery guidance (e.g., what to do when migrations fail) and the database steps lack feedback loops.	4 / 5
Progressive Disclosure	Sections are well-organized with clear ## / ### headers, but the ~440-line file inlines everything with no reference files; the extended entity/service/handler patterns clearly belong in a references/ bundle. Anchor 3 ('content that should be separate is inline'), not 2 since structure is good, not minimal.	3 / 5
	Total	15 / 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 that names a concrete tech stack and actions, written in appropriate third-person style. Its main weakness is the missing 'Use when...' trigger clause, which caps completeness and slightly limits trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when creating or extending a Symfony 7.x PHP application, or when the user mentions Symfony, Doctrine, API Platform, Messenger, or Twig.'

Add natural synonym variations users might say ('PHP backend', 'build a Symfony app', '.php files') to broaden trigger matching.

Optionally enumerate one or two more capabilities (migrations, functional testing) to close the small coverage gap.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('Scaffold and develop a Symfony 7.x application', 'Messenger async processing', 'Twig templating') with a fully named stack (Doctrine ORM, API Platform). Not a 5 because coverage has minor gaps (testing, migrations, auth unmentioned); clearly above anchor 3's '1-2 concrete actions'.	4 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Strong natural keywords users would say: 'Symfony', 'PHP 8.3+', 'Doctrine ORM', 'API Platform', 'Twig'. A few natural variations are missing ('PHP project', 'build a Symfony app', '.php'), matching anchor 4 rather than 5's comprehensive synonym/extension coverage.	4 / 5
Distinctiveness Conflict Risk	'Symfony 7.x application with PHP 8.3+, Doctrine ORM, API Platform, Messenger, Twig' carves out a clear niche with distinct triggers and minimal conflict risk — only a very generic 'PHP backend' skill could overlap.	5 / 5
	Total	16 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: achreftlili/deep-dev-skills
Path: backend-php/symfony-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.

symfony-project-starter

Table of Contents

Is this your skill?