Snowflake semantic views: build, validate and troubleshoot via CLI
Create and alter Snowflake semantic views and validate the DDL against Snowflake with the snow CLI
- What
- Create and alter Snowflake semantic views and validate the DDL against Snowflake with the snow CLI
- Cost
- Free
- Needs
- the Snowflake CLI (snow) installed, a configured Snowflake connection (snow connection add), and a Snowflake account β Snowflake is pay-as-you-go (trial credits expire)
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
Curated by Skill Harbor β π³ **Paid API required** β requires a Snowflake account; Snowflake is pay-as-you-go (trial credits expire). The full workflow for Snowflake semantic views through the `snow` CLI: confirm database, schema, role, warehouse and final view name, check the model follows a star schema, draft the CREATE/ALTER SEMANTIC VIEW DDL with synonyms and comments (preferring existing Snowflake comments as the source, drafting only with approval), then always validate against Snowflake with `snow sql` under a temporary `__tmp_validate` name before applying the real name β iterating until it succeeds β and finish with a sample query and cleanup of the temp view. By @github, listed here with credit to its creator. Honest caveats: needs the Snowflake CLI installed and a configured connection (`snow connection add`); flag names can drift between CLI versions, so check `snow sql --help` when in doubt; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: the Snowflake CLI (snow) installed, a configured Snowflake connection (snow connection add), and a Snowflake account β Snowflake is pay-as-you-go (trial credits expire) Install "Snowflake semantic views: build, validate and troubleshoot via CLI" for me. Give my agent the snowflake-semanticview workflow: one-time setup (snow CLI install, connection), then per request β confirm database/schema/role/warehouse/view name, star-schema check, draft CREATE/ALTER SEMANTIC VIEW DDL with synonyms and comments, validate with snow sql under a temporary __tmp_validate name, iterate on failure, apply the final DDL, run a sample query, and clean up the temp view. Never skip validation. Repository: https://github.com/github/awesome-copilot/blob/main/skills/snowflake-semanticview/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "snowflake-semanticview". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the Snowflake CLI and configure my connection with snow connection add). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat β credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.