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".
60
72%
Does it follow best practices?
Impact
—
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 'Process use when you need to work with schema comparison' is grammatically awkward and the description lacks specific concrete actions beyond 'diff and sync'. The phrase 'comprehensive guidance and automation' is vague filler that doesn't add informational value.
Suggestions
Replace vague language like 'comprehensive guidance and automation' with specific concrete actions such as 'detect column changes, generate migration scripts, compare table structures across databases'.
Fix the grammatically broken opening sentence 'Process use when you need to work with schema comparison' — rewrite in proper third person voice like 'Compares and synchronizes database schemas.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (database schema comparison) and mentions 'diff and sync' as actions, but doesn't list specific concrete actions like 'detect added/removed columns, generate migration scripts, compare table structures'. | 2 / 3 |
Completeness | Answers both 'what' (database schema diff and sync) and 'when' (explicit trigger phrases provided: 'compare schemas', 'diff databases', 'sync database schemas'). | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases like 'compare schemas', 'diff databases', and 'sync database schemas' which are terms users would naturally use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on database schema comparison and synchronization is a clear niche that is unlikely to conflict with other skills; the trigger terms are specific to this domain. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a comprehensive and well-structured workflow for database schema comparison with good sequencing and a critical validation step. However, it suffers from being monolithic — all content for multiple database engines and numerous comparison dimensions is packed into one file, making it token-heavy. The actionability is hampered by incomplete code fragments that describe rather than fully implement the comparison process.
Suggestions
Split database-engine-specific instructions (PostgreSQL vs MySQL) into separate referenced files to improve progressive disclosure and reduce the main file's token footprint.
Provide a complete, executable comparison script (e.g., a Python or shell script) that ties all steps together rather than individual SQL fragments that require manual assembly.
Remove the Resources section with well-known URLs and the narrative example scenarios, replacing them with a concise input/output example showing actual diff output format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient 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 trimmed, and the resources section lists well-known URLs Claude already has knowledge of. However, the core instructions are reasonably dense with useful information. | 2 / 3 |
Actionability | Provides specific SQL queries and CLI commands which is good, but many are incomplete fragments (e.g., the EXCEPT query assumes both databases are accessible from the same connection, which is rarely the case). No complete executable script is provided — the instructions describe what to do at each step but don't provide a copy-paste-ready workflow or script that ties it all together. | 2 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced from extraction through comparison, report generation, migration SQL generation, and crucially includes step 10 as an explicit validation checkpoint (apply migration to a copy and re-run diff to confirm zero differences). The error handling table provides recovery guidance for common failure modes, and the output section clearly defines expected deliverables. | 3 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no bundle files and no references to supporting documents. All detailed instructions for PostgreSQL, MySQL, tables, columns, indexes, constraints, functions, enums, etc. are inlined in a single file. This would benefit greatly from splitting database-specific details, example scripts, and the error handling table into separate referenced files. | 1 / 3 |
Total | 8 / 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
4801da6
- 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.