comparing-database-schemas
Process use when you need to work with schema comparison. This skill provides database schema diff and sync with comprehensive guidance and automation. Trigger with phrases like "compare schemas", "diff databases", or "sync database schemas".
79
76%
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 ./plugins/database/database-diff-tool/skills/comparing-database-schemas/SKILL.mdQuality
Discovery
89%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 adequately identifies its niche (database schema diff/sync) and provides explicit trigger phrases, making it functional for skill selection. However, the opening sentence is awkwardly phrased ('Process use when you need to work with schema comparison'), and the description lacks specificity about the concrete actions it performs beyond generic 'diff and sync'. Adding more specific capabilities would strengthen it.
Suggestions
List more specific concrete actions such as 'detect column additions/removals, compare indexes, generate migration scripts, identify type mismatches' to improve specificity.
Fix the awkward opening sentence 'Process use when you need to work with schema comparison' — rewrite to something like 'Compares and synchronizes database schemas across environments.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (database schema comparison) and some actions ('diff and sync'), but doesn't list multiple specific concrete actions like detecting column changes, generating migration scripts, or comparing indexes. | 2 / 3 |
Completeness | Explicitly answers both 'what' (database schema diff and sync) and 'when' (trigger phrases like 'compare schemas', 'diff databases', 'sync database schemas'), meeting the criteria for explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'compare schemas', 'diff databases', 'sync database schemas'. These are realistic terms a user would use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on database schema comparison and synchronization is a clear niche with distinct triggers unlikely to conflict with other skills. Terms like 'schema diff' and 'sync database schemas' are highly specific. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive, well-structured workflow for database schema comparison with good sequencing and a validation checkpoint. Its main weaknesses are moderate verbosity, incomplete actionability (queries are fragments rather than complete executable scripts), and a monolithic structure that would benefit from splitting into supporting files for different database engines or detailed reference material.
Suggestions
Provide complete, executable SQL scripts or a Python/shell script template for the full comparison workflow rather than inline query fragments
Split database-engine-specific guidance (PostgreSQL vs MySQL) into separate reference files to reduce the main skill's length and improve progressive disclosure
Trim the prerequisites and examples sections—remove narrative prose and replace with concise bullet points or structured input/output examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably structured but includes some unnecessary verbosity. The prerequisites section explains things Claude would know (like what information_schema is), the examples section uses narrative prose that could be more concise, and the overview sentence is truncated. However, the core instructions are fairly direct without excessive padding. | 2 / 3 |
Actionability | The skill provides specific SQL queries and CLI commands (pg_dump, mysqldump), which is good. However, the queries are inline fragments rather than complete, executable scripts. The migration generation step (9) describes what to do abstractly rather than providing concrete code or a script template. The guidance sits between pseudocode and fully executable examples. | 2 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced from extraction through comparison, report generation, migration creation, and validation. Step 10 explicitly includes a validation/feedback loop: apply migration to a copy, re-run diff, confirm zero differences. This is a strong checkpoint for a destructive/batch operation. The error handling table adds further recovery guidance. | 3 / 3 |
Progressive Disclosure | The content is a monolithic single file with no bundle files or references to supplementary materials. For a skill of this complexity (covering PostgreSQL and MySQL, multiple object types, migration generation, rollback scripts), the content would benefit from being split into separate files for each database engine or for the migration generation logic. The Resources section links to external docs but doesn't organize internal content progressively. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.