Guide for using molt verify to compare source and target databases for schema and row-level consistency after a migration. Use when running verify commands, tuning concurrency/sharding, handling schema mismatches, or validating data integrity post-migration.
93
91%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
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.
This is a well-crafted skill description that clearly identifies the tool (molt verify), the domain (database migration verification), and includes an explicit 'Use when' clause with relevant trigger scenarios. The specificity of actions could be slightly improved by listing more concrete operations, but overall it performs strongly across all dimensions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (database migration verification) and some actions (compare databases, tune concurrency/sharding, handle schema mismatches), but doesn't list multiple concrete granular actions—it stays at a moderate level of specificity. | 2 / 3 |
Completeness | Clearly answers both 'what' (guide for using molt verify to compare source and target databases for schema and row-level consistency) and 'when' (explicit 'Use when' clause covering verify commands, tuning concurrency/sharding, handling schema mismatches, or validating data integrity post-migration). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would actually say: 'molt verify', 'verify commands', 'schema mismatches', 'data integrity', 'post-migration', 'concurrency', 'sharding', 'source and target databases'. These cover the likely vocabulary a user would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—'molt verify' is a specific tool, and the description targets a clear niche of database migration verification. Unlikely to conflict with other skills due to the specific tool name and domain. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides comprehensive, actionable guidance for using molt verify. It excels at conciseness and actionability with executable commands, clear workflow scenarios, and a thorough error recovery table. The only minor weakness is that the content is moderately long for a single file and references a flags file that isn't provided in the bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude knows what databases, migrations, and CLI tools are. Every section delivers actionable information without preamble or unnecessary explanation. The tables and code blocks are dense with useful information. | 3 / 3 |
Actionability | Provides fully executable bash commands with realistic connection strings, concrete flag combinations for different scenarios, and specific output format examples. The error recovery table maps exact error messages to specific fixes. The workflows are copy-paste ready. | 3 / 3 |
Workflow Clarity | The verification phases are clearly sequenced (schema first, then rows). The common workflows section provides five distinct, well-ordered scenarios. The error recovery table serves as a validation/feedback loop, mapping specific errors to fixes. The 'Gotchas' section includes the critical checkpoint: 'always run verify before cutover to confirm data integrity.' | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and good use of tables, but it's somewhat long for a single file. The reference to 'references/flags.md' at the end is good progressive disclosure, but no bundle files exist to validate this reference. Some content like source-specific prerequisites could potentially be split out. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
84bc1e4
Table of Contents
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.