SKILLEMALL.ai
GitHub ↗ RU Sign in

BF 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/.

ClawHub Agent Skills author: Amazon Web Services 1 file body ≈ 2 460 tokens Open the sourceclawhub.ai↗ analyzed 12 h ago

Guides an end-to-end data-warehouse migration to Amazon Redshift — discovery, schema/SQL/stored-procedure/macro/script conversion, data migration, validation…

As a process F 47/100 · Will not run — References files that are not bundled: references/<source>/, references/teradata/, references/teradata/discovery-queries.md

ProcedureGoogle CloudAWSData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
F
47/100
Will not run
References files that are not bundled: references/<source>/, references/teradata/, references/teradata/discovery-queries.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
30
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/<source>/
  • warning missing-ref reference to a missing file: references/teradata/
  • warning missing-ref reference to a missing file: references/teradata/discovery-queries.md
  • warning missing-ref reference to a missing file: references/teradata/conversion-rules.md
  • warning missing-ref reference to a missing file: references/teradata/orchestration.md
  • warning missing-ref reference to a missing file: references/teradata/data-type-mapping.md
  • warning missing-ref reference to a missing file: references/teradata/architecture-mapping.md
  • warning missing-ref reference to a missing file: references/teradata/stored-procedure-migration.md
  • warning missing-ref reference to a missing file: references/teradata/bteq-to-rsql.md
  • warning missing-ref reference to a missing file: references/teradata/common-errors.md
  • warning missing-ref reference to a missing file: references/teradata/data-migration-patterns.md
  • warning missing-ref reference to a missing file: references/teradata/validation-patterns.md
  • warning missing-ref reference to a missing file: references/teradata/performance.md
  • warning missing-ref reference to a missing file: references/teradata/sizing.md
  • warning missing-ref reference to a missing file: references/teradata/reporting.md

Process rating: all ten parameters 47/100

Will not run. References files that are not bundled: references/<source>/, references/teradata/, references/teradata/discovery-queries.md
  • 0Tools and files. 15 referenced file(s) missing: references/<source>/, references/teradata/, references/teradata/discovery-queries.md
  • 0Result and completion. Does not say what the result is
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 1 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 25 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2460 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 10 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +3Description length 978: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 25 items
  • +4Has examples (1 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.