drupal-development
Expert guidance for Drupal 10 module development with PHP 8+, SOLID principles, and Drupal coding standards
39
Quality
27%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./drupal-development/SKILL.mdQuality
Discovery
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 a clear technical domain (Drupal 10 module development) and mentions relevant standards, but lacks concrete actions and completely omits trigger guidance. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill from a large skill library.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Drupal modules, custom plugins, hooks, services, or Drupal PHP development'
List specific concrete actions such as 'Create custom modules, implement hooks, define services, write entity handlers, configure routing'
Include additional natural trigger terms users might say: 'Drupal plugin', 'custom module', '.module file', 'Drupal hooks', 'dependency injection in Drupal'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Drupal 10 module development) and mentions PHP 8+, SOLID principles, and coding standards, but doesn't list concrete actions like 'create custom modules', 'implement hooks', or 'write services'. | 2 / 3 |
Completeness | Describes what it does ('Expert guidance for Drupal 10 module development') but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 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', 'custom module', 'hooks', 'services', or '.module files'. | 2 / 3 |
Distinctiveness Conflict Risk | Drupal 10 specificity helps distinguish from generic PHP or CMS skills, but 'module development' could overlap with other Drupal-related skills or general PHP development skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a checklist of Drupal development principles than actionable guidance. It lacks concrete code examples, executable patterns, and step-by-step workflows that would help Claude actually implement Drupal modules. The content assumes Claude needs reminders about general programming principles (SOLID, DRY) while failing to provide the Drupal-specific syntax and patterns that would be genuinely useful.
Suggestions
Add concrete, executable code examples for each major section (e.g., a complete service definition with services.yml entry, a Form API implementation, a hook example)
Include a step-by-step workflow for creating a new Drupal module with validation checkpoints
Remove general programming principles Claude already knows (SOLID, DRY, PSR-12) and focus on Drupal-specific patterns and gotchas
Add specific file structure examples and common Drupal CLI commands (drush) for module scaffolding and testing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some guidance Claude already knows (SOLID principles, DRY, PSR-12 basics). The bullet-point format is lean, but many items are general best practices rather than Drupal-specific knowledge. | 2 / 3 |
Actionability | The skill provides only abstract guidance with no concrete code examples, commands, or executable snippets. Statements like 'Use Drupal's database API' and 'Register services properly in services.yml' describe rather than instruct with specific syntax or patterns. | 1 / 3 |
Workflow Clarity | No multi-step workflows are defined. The content lists categories of concerns but provides no sequenced processes, validation checkpoints, or feedback loops for common Drupal development tasks like creating a module or implementing a service. | 1 / 3 |
Progressive Disclosure | The content has reasonable section organization with headers, but everything is inline with no references to detailed documentation. For a comprehensive topic like Drupal development, this would benefit from linking to separate files for services, forms, security, etc. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- Repository
- mindrally/skills
- Commit
47f47c1
- Reviewed
Table of Contents
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.