drupal-development

Expert guidance for Drupal 10 module development with PHP 8+, SOLID principles, and Drupal coding standards

Quality

20%

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 ./drupal-development/SKILL.md

Quality

Content

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

This skill reads as a generic checklist of Drupal development best practices that Claude already knows, offering no concrete code examples, specific commands, or novel project-specific guidance. It lacks actionable instructions, executable examples, and any workflow sequencing. The content would need a fundamental rewrite to provide value beyond what Claude's training data already covers.

Suggestions

Replace vague directives with concrete, executable code examples — e.g., show a complete minimal module with .info.yml, .services.yml, a controller, and a route definition.

Add a step-by-step workflow for common tasks like 'creating a new custom module' with validation checkpoints (e.g., drush cr, phpunit commands to verify).

Remove generic advice Claude already knows (SOLID, DRY, PSR-12, 'sanitize all user input') and focus on Drupal-specific patterns, gotchas, or project-specific conventions that are genuinely novel.

Include concrete file structure examples and templates showing exact file paths, naming conventions, and boilerplate code for services.yml, routing.yml, and hook implementations.

Dimension	Reasoning	Score
Conciseness	The content is largely a list of general best practices and principles that Claude already knows well (SOLID, DRY, PSR-12, dependency injection, sanitize input, etc.). Very little here is novel or specific enough to justify the token cost. It reads like a generic Drupal development guide rather than targeted instructions.	1 / 3
Actionability	The skill provides no concrete code examples, no executable commands, no specific file templates, and no copy-paste ready snippets. Every item is a vague directive like 'Use Drupal's database API' or 'Implement proper access checks' without showing how.	1 / 3
Workflow Clarity	There is no sequenced workflow, no step-by-step process for creating a module, no validation checkpoints, and no feedback loops. The content is organized as flat bullet-point lists of principles without any procedural guidance.	1 / 3
Progressive Disclosure	The content has some structural organization with headers and subsections (Services, Routing, Forms, etc.), which aids navigation. However, there are no references to external files, no links to deeper documentation, and all content is inline at the same level of abstraction.	2 / 3
	Total	5 / 12 Passed

Description

32%

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 identifies the domain (Drupal 10 module development) and some relevant technologies but remains too high-level and lacks concrete actions or explicit trigger guidance. It reads more like a tagline than a functional skill description, using the vague term 'expert guidance' instead of listing specific capabilities. Adding a 'Use when...' clause and concrete actions would significantly improve skill selection accuracy.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Drupal module', 'custom module', 'hook', 'plugin', 'Drupal service', 'routing', '.module file', 'Drupal entity'.

Replace 'Expert guidance' with specific concrete actions such as 'Creates custom Drupal 10 modules, implements hooks, defines routes and controllers, builds plugin classes, and configures dependency injection.'

Include common file extensions or patterns users might reference, such as '.module', '.routing.yml', '.services.yml', 'composer.json' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Drupal 10 module development) and mentions some relevant concepts (PHP 8+, SOLID principles, coding standards), but does not list concrete actions like 'create custom modules', 'define routes', 'implement hooks', or 'write plugin classes'.	2 / 3
Completeness	Describes what it does at a high level ('expert guidance for Drupal 10 module development') but has no 'Use when...' clause or explicit trigger guidance, and the 'what' is itself vague ('guidance' rather than concrete actions). Missing 'when' caps this at 2, and the weak 'what' brings it to 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Drupal 10', 'module development', 'PHP 8+', and 'SOLID principles' that users might mention, but misses common variations like 'Drupal plugin', 'hook implementation', 'custom module', 'services', 'dependency injection', or '.module files'.	2 / 3
Distinctiveness Conflict Risk	Specifying 'Drupal 10' and 'module development' provides some distinctiveness, but 'expert guidance' and 'SOLID principles' are generic enough to overlap with general PHP development or other CMS skills. The lack of explicit triggers increases conflict risk.	2 / 3
	Total	7 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: mindrally/skills
Commit: 05a7130

Reviewed: 14 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.