Download for MacApple silicon, macOS 14+
Skill

ts-convert-from-snowflake-sv

@thoughtspot Updated 2026-11-01

Convert or import a Snowflake Semantic View into ThoughtSpot as a Model. Use when Snowflake is the source and the goal is a ThoughtSpot Model — whether migrating Snowflake metrics and semantic definitions into ThoughtSpot or making a Semantic View available for Spotter and search-based analytics. Direction is always Snowflake → ThoughtSpot. Not for ThoughtSpot → Snowflake, standalone DDL generation, or adding AI context to existing ThoughtSpot models.

Install

With your agent

Install OMGSkills skill "thoughtspot/thoughtspot-agent-skills:ts-convert-from-snowflake-sv" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/thoughtspot/thoughtspot-agent-skills /tmp/thoughtspot-agent-skills && ln -s /tmp/thoughtspot-agent-skills/agents/cli/ts-convert-from-snowflake-sv ~/.claude/skills/ts-convert-from-snowflake-sv

From README

Snowflake Semantic View → ThoughtSpot Model Converts a Snowflake Semantic View into a ThoughtSpot Model. Reads the semantic view DDL via GETDDL, then uses three deterministic CLI commands — ts snowflake parse-sv (DDL → structured JSON), ts snowflake translate-formulas (SQL → ThoughtSpot formulas), and ts snowflake build-model (JSON → Model TML + import) — to map tables, relationships, dimensions, and metrics to ThoughtSpot TML. Two scenarios are supported: Scenario A (existing tables): ThoughtSpot Table objects already exist for the Snowflake objects the semantic view references. Reuses those existing Table objects. Scenario B (new tables): No ThoughtSpot Table objects exist yet for the Snowflake objects the semantic view references. Creates new Table objects pointing to those objects. Ask one question at a time for dependent decisions (each answer narrows the next — target database, then schema, then table). Batch independent questions when possible — e.g.