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:
Quick answer
Snowflake semantic views is a free Muse skill for the full workflow of Snowflake semantic views through the snow CLI, but it requires a paid Snowflake account. It confirms database, schema, role, warehouse and final view name, checks the model follows a star schema, drafts the create or alter semantic view DDL with synonyms, and validates the DDL against Snowflake.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 82701c2Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/github/awesome-copilot/82701c24b99488536ca399ff4789a458b7a05db7/skills/snowflake-semanticview/SKILL.md Pinned version: install the code at commit 82701c24b99488536ca399ff4789a458b7a05db7 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 82701c2 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.