CtrlK
BlogDocsLog inGet started
Tessl Logo

migrating-to-amazon-redshift

Guides an end-to-end data-warehouse migration to Amazon Redshift — discovery, schema/SQL/stored-procedure/macro/script conversion, data migration, validation, performance comparison, and reporting. Source-routed via `references/<source>/`; Teradata (Vantage) is the supported source; additional sources are added as their own `references/<source>/` sets. Text-only knowledge (no executable code) — the AI generates all execution at runtime. Applies when a user wants to migrate Teradata to Amazon Redshift, convert Teradata DDL/SQL/stored procedures/macros/BTEQ to Redshift/RSQL, or assess Teradata-to-Redshift migration complexity. Applies only to migrations targeting Amazon Redshift; migrations to other platforms (Snowflake, BigQuery, Databricks, etc.) are out of scope regardless of source. Does not cover general Redshift administration, performance tuning, or troubleshooting of existing Redshift clusters (no migration involved), or sources not listed under references/.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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

A well-structured, actionable instruction-only skill with clear phased workflow and excellent progressive disclosure through real reference files. The main weakness is redundancy — credential/secrets and the 'knowledge over code' principle are repeated across sections and could be consolidated.

Suggestions

De-duplicate credential/secret guidance: state the read-only-user, IAM-roles-over-users, and Secrets Manager/Parameter Store rules once in 'Operating principles' (or 'Security considerations') and cross-reference from the other section instead of restating verbatim.

State the 'no executable code / AI generates execution' design principle once in 'What this skill is' and reference it elsewhere rather than re-explaining it in Operating principles, Conversion, and Security.

Make per-phase validation gating explicit (e.g., 'do not proceed to Data migration until Conversion result/ is reviewed and manual_review.json is triaged') to lift workflow clarity from implied to explicit feedback loops.

DimensionReasoningScore

Conciseness

Mostly efficient and purposeful, but credential/secret guidance (read-only user, IAM roles over users, Secrets Manager/Parameter Store) is restated nearly verbatim across 'Operating principles' and 'Security considerations', and the 'no executable code / AI generates execution' principle is repeated in 3+ sections — could be tightened by stating once and cross-referencing.

3 / 5

Actionability

For an instruction-only skill it gives concrete, specific directives — exact per-phase reference file paths, AWS hardening specifics (COPY IAM_ROLE, aws:SourceAccount/aws:SourceArn/sts:ExternalId condition keys), and a concrete DBQL fallback (DBC.AMPUsageV); stopped at 4 because the executable bulk lives in the referenced files rather than inline copy-paste content.

4 / 5

Workflow Clarity

Six phases are clearly sequenced with each phase's result/ feeding the next and a state.md cursor for resumability, plus a dedicated Validation phase and blast-radius gating; falls just short of 5 because per-step validate→fix→retry feedback loops are implied (common-errors.md) rather than spelled out as gated checkpoints.

4 / 5

Progressive Disclosure

SKILL.md acts as a lean overview/router with a References table mapping each of 13 one-level-deep reference files to its topic; every referenced path resolves to a real file under references/teradata/, and content is appropriately split for easy navigation.

5 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 is highly specific, with concrete trigger phrases, explicit what/when guidance, and strong boundary scoping that minimizes conflict risk. It is somewhat long and could trim implementation detail (source-routing mechanics) but no dimension is materially weakened by it.

DimensionReasoningScore

Specificity

Names the full migration lifecycle concretely — 'discovery, schema/SQL/stored-procedure/macro/script conversion, data migration, validation, performance comparison, and reporting' — covering multiple specific actions comprehensively, matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' (end-to-end migration to Redshift with the listed phases) and 'when' via a concrete 'Applies when a user wants to...' trigger clause, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Includes natural user phrasings and synonyms — 'migrate Teradata to Amazon Redshift', 'convert Teradata DDL/SQL/stored procedures/macros/BTEQ to Redshift/RSQL', 'assess Teradata-to-Redshift migration complexity' — with comprehensive coverage of the specific source/target and object-type terms.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Teradata→Redshift migration) and explicitly excludes other targets (Snowflake, BigQuery, Databricks) and general Redshift admin/troubleshooting, giving minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 31 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
aws/agent-toolkit-for-aws
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.