database-migrations
Creates 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.
Install with Tessl CLI
npx tessl i github:ThibautBaissac/rails_ai_agents --skill database-migrations90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that follows best practices. It uses third person voice, lists specific concrete capabilities, includes an explicit 'Use when...' clause with comprehensive trigger terms, and carves out a distinct niche around database migrations specifically. The description effectively differentiates itself from general database skills by focusing on migration-specific concerns like rollback strategies and zero-downtime deployments.
| 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 when discussing database work. | 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 |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent executable code examples and clear multi-step workflows for safe database migrations. The main weakness is its length - it's comprehensive to the point of being verbose, and could benefit from splitting into a quick-start overview with references to detailed pattern files. The safety checklist and validation steps are well-designed.
Suggestions
Split advanced topics (Strong Migrations gem, Index Strategies, Data Migrations) into separate reference files and link from a concise overview
Remove the overview section bullets - they explain concepts Claude already understands about why migrations matter
| 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 - the overview bullets and some inline comments explain concepts Claude already knows. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all migrations are copy-paste ready with proper class names, file paths, and Rails 8.0 syntax. Includes specific bash commands, model code, and even spec examples. Every pattern has concrete, runnable code. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation steps. The two-step NOT NULL pattern, three-step column type change, and the safety checklist all provide clear workflows. The 'Test Rollback' section includes explicit verification commands. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear headers and logical grouping, but it's a monolithic document (~300 lines) that could benefit from splitting advanced topics (data migrations, strong_migrations config, index strategies) into separate reference files. No external file references are provided. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 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.