Drupal ddev operations
Skill siva01c/claude-plugins/ddev-tools/skills/drupal-ddev-operations
Use for operational Drupal 11 workflows in DDEV environments, including safe updates, backup-first procedures, and troubleshooting commands.From its SKILL.md
npx -y skills add siva01c/claude-plugins --skill drupal-ddev-operationsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 8 commands, including `ddev list` and 7 more.
SKILL.md
1.0 KB, 216 tokens by cl100k_base, as published. Nobody here has run it
Drupal DDEV Operations Skill
Purpose
Use this skill for safe day-to-day Drupal 11 environment operations in DDEV projects.
When to apply
- Running updates (core or contrib).
- Importing/exporting databases and configuration.
- Diagnosing local environment issues.
Standard operating procedure
- Verify project status with
ddev listandddev describe. - Create a backup before destructive changes.
- Apply Composer updates and then Drush database updates.
- Rebuild caches and confirm site health.
- Export and commit configuration updates when needed.
Safe update flow
ddev export-db --file=pre-update-backup.sql
ddev composer update drupal/core* --with-dependencies
ddev drush updb -y
ddev drush cr
ddev drush config:status
Troubleshooting shortcuts
ddev logs web
ddev logs db
ddev drush status
ddev drush watchdog:show
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most operations skills give in 216 tokens
Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07
- Collect monitoring data throughout the simulationin 14 of 483, across 6 files
- Set the random seed for reproducibilityin 14 of 483, across 6 files
- Validate simulations against analytical solutionsin 12 of 483, across 4 files
- Clarify goals, constraints, and inputsin 11 of 483, across 2 files
- Implement contract tests for integration pointsin 11 of 483, across 2 files
- Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
- Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
- Avoid Python blocking calls in processesin 10 of 483, across 3 files
- Use resource context managers for automatic cleanupin 9 of 483, across 2 files
- Maintain consistent time unitsin 9 of 483, across 2 files
- Validate outcomes against success criteriain 8 of 483, across 1 file
- Analyze the legacy codebase for technical debtin 8 of 483, across 1 file
Said here and by no other author read
- verify project status
- create a backup before destructive changes
- apply composer updates
- apply drush database updates
- rebuild caches
- confirm site health
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.