altimate-setup
Altimate Setup
Guide the user through configuring their Altimate platform credentials.
Steps
-
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:
- Altimate URL (default:
https://api.myaltimate.com) - Instance name (their tenant/org name, e.g.
megatenant) - API key (from Altimate platform settings)
- MCP server URL (optional, default:
https://mcpserver.getaltimate.com/sse)
- Altimate URL (default:
-
Write config: Create
~/.altimate/directory if needed, then write~/.altimate/altimate.json:{ "altimateUrl": "<url>", "altimateInstanceName": "<instance>",
More from altimateai/altimate-code
data-viz
>
6schema-migration
Analyze DDL migrations for data loss risks — type narrowing, missing defaults, dropped constraints, breaking column changes. Use before applying schema changes to production.
3dbt-unit-tests
Generate dbt unit tests automatically for any model. Analyzes SQL logic (CASE/WHEN, JOINs, window functions, NULLs), creates type-correct mock inputs from manifest schema, and assembles complete YAML. Use when a user says "generate tests", "add unit tests", "test this model", or "test coverage" for dbt models.
3dbt-test
Add schema tests, unit tests, and data quality checks to dbt models. Use when validating data integrity, adding test definitions to schema.yml, writing unit tests, or practicing test-driven development in dbt. Powered by altimate-dbt.
2dbt-docs
Document dbt models and columns in schema.yml with business context — model descriptions, column definitions, and doc blocks. Use when adding or improving documentation for discoverability. Powered by altimate-dbt.
2sql-review
Pre-merge SQL quality gate — lint 26 anti-patterns, grade readability/performance A-F, validate syntax, and scan for injection threats. Use before committing or reviewing SQL changes.
2