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

72%

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/symfony-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 solid, highly actionable Symfony starter skill with excellent executable code examples and clear workflows. The main weaknesses are moderate verbosity (some explanations Claude doesn't need) and a monolithic structure that could benefit from progressive disclosure via separate reference files for the detailed code patterns.

Suggestions

Consider moving the detailed code examples (Entity, Repository, Controller, Service, Messenger patterns) to a separate PATTERNS.md or EXAMPLES.md file, keeping SKILL.md as a concise overview with links

Trim explanatory comments in the project structure section - Claude understands what 'Doctrine migrations' and 'HTTP controllers' are without the inline descriptions

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some content Claude would already know (e.g., basic Symfony concepts, what directories contain). The extensive code examples are valuable but could be trimmed in places where patterns are standard.	2 / 3
Actionability	Excellent actionability with fully executable code examples throughout - complete entity, repository, controller, service, message handler, and test examples that are copy-paste ready. Commands are specific and complete.	3 / 3
Workflow Clarity	Clear 'First Steps After Scaffold' section provides explicit sequenced steps. The scaffold command sequence is clear, and common commands are well-organized. For a project starter skill, the workflow is appropriately structured.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic document that could benefit from splitting detailed patterns (Entity, Repository, Controller examples) into separate reference files. No external file references are provided.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 with a well-defined technology stack and version requirements, making it highly distinctive. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select this skill, and could benefit from more natural keyword variations users might say.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when the user asks to create a Symfony project, build a PHP API, or work with Doctrine entities'

Include common keyword variations users might say: 'symfony project', 'php api', 'doctrine migrations', 'symfony console', '.php files'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete technologies and actions: 'Scaffold and develop', 'Symfony 7.x', 'PHP 8.3+', 'Doctrine ORM', 'API Platform', 'Messenger async processing', and 'Twig templating'.	3 / 3
Completeness	Clearly answers 'what' (scaffold and develop Symfony apps with specific stack), but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill.	2 / 3
Trigger Term Quality	Includes relevant technical keywords like 'Symfony', 'PHP', 'Doctrine', 'API Platform', 'Messenger', 'Twig' that users would mention, but missing common variations like 'symfony project', 'php framework', 'doctrine entities', or file extensions.	2 / 3
Distinctiveness Conflict Risk	Very specific niche with Symfony 7.x, PHP 8.3+, and the particular stack (Doctrine, API Platform, Messenger, Twig) makes it clearly distinguishable from generic PHP or other framework skills.	3 / 3
	Total	10 / 12 Passed

Validation

90%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 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.