database-migrations
tessl i github:ThibautBaissac/rails_ai_agents --skill database-migrationsCreates safe database migrations with proper indexes and rollback strategies. Use when creating tables, adding columns, creating indexes, handling zero-downtime migrations, or when user mentions migrations, schema changes, or database structure.
Validation
69%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Implementation
77%This is a strong, actionable skill with excellent executable code examples and clear multi-step workflows including validation checkpoints. The main weaknesses are moderate verbosity in the overview section and a monolithic structure that could benefit from progressive disclosure through linked reference files for advanced topics like index strategies and data migrations.
Suggestions
Remove the overview section explaining why safe migrations matter - Claude already knows this context
Split advanced topics (Index Strategies, Data Migrations, Strong Migrations Gem) into separate linked reference files to improve progressive disclosure
Remove redundant checklist at the end that duplicates the Safety Checklist at the top
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanation (e.g., 'Safe database migrations are critical for production stability' overview section). The content is mostly efficient but could be tightened by removing obvious context Claude already knows. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all Ruby migrations are copy-paste ready with proper class names, file paths, and complete syntax. Bash commands are specific and immediately usable. | 3 / 3 |
Workflow Clarity | Clear multi-step processes with explicit validation checkpoints. The two-step NOT NULL pattern, three-step column type change, and the safety checklist all demonstrate proper sequencing with verification steps. Testing section includes rollback verification workflow. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear headers, but it's a monolithic document that could benefit from splitting into separate files (e.g., INDEX_STRATEGIES.md, DATA_MIGRATIONS.md). No references to external files for advanced topics. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms that developers would use, explicitly states both what the skill does and when to use it, and carves out a distinct niche around database migrations that won't conflict with other database-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates safe database migrations with proper indexes and rollback strategies' followed by specific use cases like 'creating tables, adding columns, creating indexes, handling zero-downtime migrations'. | 3 / 3 |
Completeness | Clearly answers both what ('Creates safe database migrations with proper indexes and rollback strategies') and when ('Use when creating tables, adding columns, creating indexes, handling zero-downtime migrations, or when user mentions migrations, schema changes, or database structure'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'migrations', 'schema changes', 'database structure', 'creating tables', 'adding columns', 'creating indexes', 'zero-downtime migrations'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on database migrations and schema changes. The specific triggers like 'migrations', 'schema changes', 'zero-downtime migrations' are distinct and unlikely to conflict with general database query skills or other development tools. | 3 / 3 |
Total | 12 / 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.