dms-schema-conversion

Handles the full DMS Schema Conversion lifecycle including creating migration projects, converting database schemas to a target engine, running compatibility assessments, navigating metadata trees, exporting converted DDL to S3, applying schema changes to a target database, and converting SQL statements between database engines.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable procedural skill with explicit wait/validation checkpoints and a clean one-level-deep reference layout; its only weakness is minor verbosity from duplicated menu variants and repeated phrasing that could be tightened.

Suggestions

Collapse the two near-identical Actions Menu lists (SQL Server→PostgreSQL vs other engines) into one menu with a single conditional entry for "Convert statement" to remove duplication.

Factor the repeated selection-rules guidance into one shared note referenced by each operation instead of restating it in Convert Database, Assess Database, Convert Statement, and Database Statistics.

Trim the repeated "After completing, ask the customer what they'd like to do next" lines by stating this expectation once near the Actions Menu.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean procedural guidance with executable commands and little re-explanation of concepts Claude knows, but it could be tightened: the Actions Menu is duplicated across two engine combinations, selection-rules guidance is re-stated in several sections, and the recurring "ask the customer what they'd like to do next" adds light padding.	2 / 3
Actionability	Concrete, executable `aws dms` commands appear throughout with explicit waiter calls, parameter names, selection-rules handling, and S3 download steps — copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	Every operation is a clear numbered sequence with explicit validation checkpoints (DMS waiters gate each step), dependency-ordered deletion with confirmation gating in Clean Up, and an error-recovery feedback loop via troubleshooting.md.	3 / 3
Progressive Disclosure	SKILL.md is a clear overview that offloads detail to well-signaled, one-level-deep references (setup-wizard.md, action-items.md, troubleshooting.md, cancel-operations.md, schema-conversion-operations.md), all of which are real files, giving easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, action-rich description that clearly conveys capabilities and occupies a distinct niche, but it lacks an explicit "Use when..." trigger clause so it does not fully answer when Claude should invoke the skill.

Suggestions

Append an explicit "Use when..." clause, e.g. "Use when the user needs DMS Schema Conversion setup, schema conversion, compatibility assessment, or SQL statement conversion between database engines."

Add a few casual trigger variants users might say (e.g., "convert my SQL Server schema to PostgreSQL", "run a DMS migration assessment") alongside the product terms.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — "creating migration projects", "converting database schemas to a target engine", "running compatibility assessments", "navigating metadata trees", "exporting converted DDL to S3", "applying schema changes to a target database", "converting SQL statements between database engines" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	It clearly answers "what" the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at 2.	2 / 3
Trigger Term Quality	Contains natural terms a user would actually say for this work — "DMS Schema Conversion", "migration projects", "database schemas", "compatibility assessments", "SQL statements", "target database" — giving good coverage rather than only technical jargon.	3 / 3
Distinctiveness Conflict Risk	It targets a specific, distinct AWS niche (DMS Schema Conversion lifecycle) with triggers unlikely to overlap with unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: aws/agent-toolkit-for-aws
Path: skills/specialized-skills/migration-and-modernization-skills/dms-schema-conversion/SKILL.md
Commit: 222ce56

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.