managing-database-migrations
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-database-migrationsProcess use when you need to work with database migrations. This skill provides schema migration management with comprehensive guidance and automation. Trigger with phrases like "create migration", "run migrations", or "manage schema versions".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill is a generic template with no database migration-specific content. It reads like a general project management checklist rather than actionable guidance for schema migrations. There are no concrete commands, no migration tool examples (Alembic, Flyway, Rails migrations, etc.), no SQL examples, and no migration-specific workflows like handling conflicts, rollbacks, or version tracking.
Suggestions
Add concrete migration commands for at least one tool (e.g., `alembic revision --autogenerate -m 'add users table'`, `alembic upgrade head`)
Include executable SQL or ORM examples showing actual migration content (CREATE TABLE, ALTER TABLE, etc.)
Add migration-specific validation steps: checking current migration state, testing rollback before deploying, verifying schema matches expected state
Remove generic project management content (prerequisites about 'understanding system architecture', generic error handling) and focus on migration-specific guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Explains obvious concepts like 'backup critical data' and 'test in staging first' that Claude already knows. No database migration-specific content despite the title. | 1 / 3 |
Actionability | No concrete code, commands, or migration-specific examples. Entirely abstract guidance like 'Execute implementation' without any actual migration commands (e.g., no `alembic`, `flyway`, `knex migrate`, or SQL examples). | 1 / 3 |
Workflow Clarity | Steps are generic project management phases, not migration-specific workflows. No validation checkpoints for migrations (e.g., checking migration status, verifying schema state, testing rollbacks). Missing critical migration concepts like up/down migrations, version tracking, or conflict resolution. | 1 / 3 |
Progressive Disclosure | References external files in a structured way (templates, docs, examples), but the main content is a wall of generic text. The referenced files use placeholder paths that may not exist, and the 'Examples' section is empty placeholder text. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
90%The description effectively communicates when to use the skill with good trigger terms and explicit usage guidance. However, it lacks specificity in describing concrete actions - 'comprehensive guidance and automation' is vague compared to listing specific capabilities like creating migration files, running up/down migrations, or checking migration status.
Suggestions
Replace 'comprehensive guidance and automation' with specific actions like 'create migration files, run up/down migrations, check migration status, rollback changes'
Add file type or framework context if applicable (e.g., 'SQL migrations', 'Rails migrations', '.sql files')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (database migrations) and mentions 'schema migration management' with 'guidance and automation', but lacks specific concrete actions like 'create tables', 'rollback changes', or 'track version history'. | 2 / 3 |
Completeness | Explicitly answers both what ('schema migration management with comprehensive guidance and automation') and when ('Trigger with phrases like "create migration", "run migrations", or "manage schema versions"'). | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'create migration', 'run migrations', 'manage schema versions', and 'database migrations' - these are terms developers commonly use. | 3 / 3 |
Distinctiveness Conflict Risk | Database migrations is a clear niche with distinct triggers; unlikely to conflict with general database query skills or other document processing skills due to specific migration-focused terminology. | 3 / 3 |
Total | 11 / 12 Passed |
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.