Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/AltimateAI/altimate-code --skill altimate-setupThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
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
Based on SOC occupation classification
| name | altimate-setup |
| description | Configure Altimate platform credentials for datamate and API access |
Guide the user through configuring their Altimate platform credentials.
Check existing config: Read ~/.altimate/altimate.json. If it exists and is valid, show the current config (mask the API key) and ask if they want to update it.
Gather credentials: Ask the user for:
https://api.myaltimate.com)megatenant)https://mcpserver.getaltimate.com/sse)Write config: Create ~/.altimate/ directory if needed, then write ~/.altimate/altimate.json:
{
"altimateUrl": "<url>",
"altimateInstanceName": "<instance>",
"altimateApiKey": "<key>",
"mcpServerUrl": "<mcp-url>"
}
Then set permissions to owner-only: chmod 600 ~/.altimate/altimate.json
Validate: Call the datamate_manager tool with operation: "list" to verify the credentials work. Report success or failure to the user.