用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/AltimateAI/altimate-code --skill sql-translate命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | sql-translate |
| description | Translate SQL queries between database dialects (Snowflake, BigQuery, PostgreSQL, MySQL, etc.) |
Agent: builder or migrator (may write translated SQL to files) Tools used: sql_translate, read, write, altimate_core_validate
Translate SQL queries from one database dialect to another using sqlglot's transpilation engine.
Determine source and target dialects — If the user did not specify both dialects, ask which source and target dialects to use. Common dialects: snowflake, bigquery, postgres, mysql, tsql, hive, spark, databricks, redshift, duckdb.
Get the SQL to translate — Either:
read)Call sql_translate with:
sql: The SQL query textsource_dialect: The source dialecttarget_dialect: The target dialectReview the result:
success is true, present the translated SQLwarnings, explain each one and what may need manual adjustmentsuccess is false, explain the error and suggest fixesFormat the output showing:
Offer next steps if applicable:
altimate_core_validate on the translated SQL to verify syntaxThe user invokes this skill with optional dialect and SQL arguments:
/sql-translate — Interactive: ask for source dialect, target dialect, and SQL/sql-translate snowflake postgres — Translate from Snowflake to PostgreSQL (will ask for SQL)/sql-translate snowflake postgres SELECT DATEADD(day, 7, CURRENT_TIMESTAMP()) — Full inline translation| Dialect | Key |
|---|---|
| Snowflake | snowflake |
| BigQuery | bigquery |
| PostgreSQL | postgres |
| MySQL | mysql |
| SQL Server | tsql |
| Hive | hive |
| Spark SQL | spark |
| Databricks | databricks |
| Redshift | redshift |
| DuckDB | duckdb |
| SQLite | sqlite |
| Oracle | oracle |
| Trino/Presto | trino / presto |
Use the tools: sql_translate, read, write, altimate_core_validate.
Analyze and optimize SQL queries for better performance
Cloudflare-style AI code review for dbt/SQL pull requests. Produces a signed APPROVE/COMMENT/REQUEST_CHANGES verdict where every blocking finding is backed by a deterministic engine call — column-lineage blast radius, query equivalence, PII classification, and A–F grade. Use to review a dbt PR or the working-tree changes before merge.
REQUIRED before writing or modifying ANY dbt model. Invoke this skill FIRST whenever a task says "create", "build", "add", "modify", "update", "fix", or "refactor" a dbt model, staging file, mart, incremental, or snapshot. Skipping this skill is the leading cause of silent-correctness bugs — models that compile and `dbt build` cleanly but produce wrong values. It contains the patterns that prevent the most common such bugs encountered in real dbt projects: • Incremental high-water marks (`>=` vs `>` ties → silent row dropout) • Snapshot strategy selection (timestamp vs check, `unique_key` choice) • `LEFT JOIN + COUNT(*)` phantom rows from unmatched parents • Type harmonization in `COALESCE` / `CASE` / `UNION` legs • Date-spine completeness (every period present, even empty ones) • Off-by-one window boundaries (`BETWEEN d - (N-1) AND d` for N-wide) • Uniqueness enforcement when schema implies a key • Window-function `LIMIT` with deterministic tiebreaker • Verifying transformation correctness with dbt unit te
基于 SOC 职业分类
