molt-fetch
Guide for using molt fetch to migrate data from PostgreSQL, MySQL, Oracle, or MSSQL to CockroachDB. Use when running molt fetch commands, configuring storage backends, handling fetch failures/resumption, or chaining fetch with verify.
97
96%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
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 a strong skill description that clearly identifies the specific tool (molt fetch), source and target databases, and concrete use cases. It follows the recommended pattern with an explicit 'Use when...' clause listing natural trigger scenarios. The description is concise, uses third person voice, and provides enough specificity to distinguish it from other database migration or CockroachDB-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: migrating data from specific source databases (PostgreSQL, MySQL, Oracle, MSSQL) to CockroachDB, running molt fetch commands, configuring storage backends, handling fetch failures/resumption, and chaining fetch with verify. | 3 / 3 |
Completeness | Clearly answers both what ('Guide for using molt fetch to migrate data from PostgreSQL, MySQL, Oracle, or MSSQL to CockroachDB') and when ('Use when running molt fetch commands, configuring storage backends, handling fetch failures/resumption, or chaining fetch with verify') with explicit trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'molt fetch', 'PostgreSQL', 'MySQL', 'Oracle', 'MSSQL', 'CockroachDB', 'migrate data', 'storage backends', 'fetch failures', 'resumption', 'verify'. These cover the specific tool name and common database names users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific tool name 'molt fetch' and the specific target database 'CockroachDB'. This is unlikely to conflict with other skills due to the narrow, well-defined niche of a specific migration tool and specific database combinations. | 3 / 3 |
Total | 12 / 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 delivers dense, actionable migration guidance with excellent use of tables, concrete commands, and error recovery patterns. The workflow coverage from dry-run through failure resumption is thorough with appropriate validation checkpoints. The only weakness is the reference to a flags file that doesn't exist in the bundle, slightly undermining progressive disclosure.
Suggestions
Either include the referenced 'references/flags.md' file in the bundle or remove the reference to avoid a broken link.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude knows what PostgreSQL, S3, and connection strings are. Every section delivers new, non-obvious information (flags, gotchas, error recovery) without padding or explaining basic concepts. | 3 / 3 |
Actionability | Provides fully executable bash commands for every workflow (dry-run, full migration, resume, compile-only). Flag examples are concrete with real values, and the error recovery table gives specific fixes. Commands are copy-paste ready. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced (validate → migrate → resume → verify). The dry-run validation step, resume-after-failure workflow with fetch-id tokens, and the explicit 'after fetch, run molt verify' guidance provide clear validation checkpoints and error recovery loops. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, and references a flags reference file. However, the bundle has no supporting files, so the reference to 'references/flags.md' is unresolvable. The content is moderately long but appropriately organized for a single file; some sections 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.
- Repository
- cockroachlabs/cockroachdb-skills
- Commit
84bc1e4
- 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.