From a45f295c11dcf3ca3d741faf5ceb71fc0e8c5bec Mon Sep 17 00:00:00 2001 From: Miguel P Z <60221874+MiguelElGallo@users.noreply.github.com> Date: Sun, 18 Jan 2026 13:57:54 +0200 Subject: [PATCH 1/5] Enhance the skill to include sampling of data, to detect better joins. --- skills/snowflake-semanticview/SKILL.md | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/skills/snowflake-semanticview/SKILL.md b/skills/snowflake-semanticview/SKILL.md index f373025f..17a40690 100644 --- a/skills/snowflake-semanticview/SKILL.md +++ b/skills/snowflake-semanticview/SKILL.md @@ -1,5 +1,5 @@ --- -name: snowflake-semanticview +name: snowflake-semantic-views description: Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup. --- @@ -22,13 +22,26 @@ description: Create, alter, and validate Snowflake semantic views using Snowflak - Read Snowflake table/view/column comments first (preferred source): - https://docs.snowflake.com/en/sql-reference/sql/comment - If comments or synonyms are missing, ask whether you can create them, whether the user wants to provide text, or whether you should draft suggestions for approval. -5. Create a temporary validation name (for example, append `__tmp_validate`) while keeping the same database and schema. -6. Always validate by sending the DDL to Snowflake via Snowflake CLI before finalizing: +5. Use select statement with distinct and limit max 1000 rows, for finding out relationships between fact and dimension tables. Also to find out the data types of the columns. And lastly to create more meaningful comments/synonyms for the columns. +6. Create a temporary validation name (for example, append `__tmp_validate`) while keeping the same database and schema. +7. Always validate by sending the DDL to Snowflake via Snowflake CLI before finalizing: - Use `snow sql` to execute the statement with the configured connection. - If flags differ by version, check `snow sql --help` and use the connection option shown there. -7. If validation fails, iterate on the DDL and re-run the validation step until it succeeds. -8. Apply the final DDL (create or alter) using the real semantic view name. -9. Clean up any temporary semantic view created during validation. +8. If validation fails, iterate on the DDL and re-run the validation step until it succeeds. +9. Apply the final DDL (create or alter) using the real semantic view name. +10. Run a sample query against the final semantic view to confirm it works as expected. It has a different SQL syntax as can be seen here: https://docs.snowflake.com/en/user-guide/views-semantic/querying#querying-a-semantic-view +Example: + +```SQL +SELECT * FROM SEMANTIC_VIEW( + my_semview_name + DIMENSIONS customer.customer_market_segment + METRICS orders.order_average_value + ) + ORDER BY customer_market_segment; +``` + +11. Clean up any temporary semantic view created during validation. ## Synonyms And Comments (Required) From 79ecf7a17c4c2b40f71b1c040554e9730cb9f176 Mon Sep 17 00:00:00 2001 From: Miguel P Z <60221874+MiguelElGallo@users.noreply.github.com> Date: Sun, 18 Jan 2026 14:02:27 +0200 Subject: [PATCH 2/5] fix(docs): correct skill name from 'snowflake-semanticview' to 'snowflake-semantic-views' --- docs/README.skills.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/README.skills.md b/docs/README.skills.md index b83420f1..18c863d8 100644 --- a/docs/README.skills.md +++ b/docs/README.skills.md @@ -27,7 +27,7 @@ Skills differ from other primitives by supporting bundled assets (scripts, code | [azure-role-selector](../skills/azure-role-selector/SKILL.md) | When user is asking for guidance for which role to assign to an identity given desired permissions, this agent helps them understand the role that will meet the requirements with least privilege access and how to apply that role. | `LICENSE.txt` | | [github-issues](../skills/github-issues/SKILL.md) | Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task. | `references/templates.md` | | [nuget-manager](../skills/nuget-manager/SKILL.md) | Manage NuGet packages in .NET projects/solutions. Use this skill when adding, removing, or updating NuGet package versions. It enforces using `dotnet` CLI for package management and provides strict procedures for direct file edits only when updating versions. | None | -| [snowflake-semanticview](../skills/snowflake-semanticview/SKILL.md) | Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup. | None | +| [snowflake-semantic-views](../skills/snowflake-semanticview/SKILL.md) | Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup. | None | | [vscode-ext-commands](../skills/vscode-ext-commands/SKILL.md) | Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices | None | | [vscode-ext-localization](../skills/vscode-ext-localization/SKILL.md) | Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices | None | | [web-design-reviewer](../skills/web-design-reviewer/SKILL.md) | This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level. | `references/framework-fixes.md`
`references/visual-checklist.md` | From 1a9caa9762b8785825956d130388a70ddc30fa79 Mon Sep 17 00:00:00 2001 From: Miguel P Z <60221874+MiguelElGallo@users.noreply.github.com> Date: Sun, 18 Jan 2026 14:10:56 +0200 Subject: [PATCH 3/5] fix(docs): correct skill name from 'snowflake-semantic-views' to 'snowflake-semanticview' --- docs/README.skills.md | 2 +- skills/snowflake-semanticview/SKILL.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/README.skills.md b/docs/README.skills.md index 18c863d8..b83420f1 100644 --- a/docs/README.skills.md +++ b/docs/README.skills.md @@ -27,7 +27,7 @@ Skills differ from other primitives by supporting bundled assets (scripts, code | [azure-role-selector](../skills/azure-role-selector/SKILL.md) | When user is asking for guidance for which role to assign to an identity given desired permissions, this agent helps them understand the role that will meet the requirements with least privilege access and how to apply that role. | `LICENSE.txt` | | [github-issues](../skills/github-issues/SKILL.md) | Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task. | `references/templates.md` | | [nuget-manager](../skills/nuget-manager/SKILL.md) | Manage NuGet packages in .NET projects/solutions. Use this skill when adding, removing, or updating NuGet package versions. It enforces using `dotnet` CLI for package management and provides strict procedures for direct file edits only when updating versions. | None | -| [snowflake-semantic-views](../skills/snowflake-semanticview/SKILL.md) | Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup. | None | +| [snowflake-semanticview](../skills/snowflake-semanticview/SKILL.md) | Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup. | None | | [vscode-ext-commands](../skills/vscode-ext-commands/SKILL.md) | Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices | None | | [vscode-ext-localization](../skills/vscode-ext-localization/SKILL.md) | Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices | None | | [web-design-reviewer](../skills/web-design-reviewer/SKILL.md) | This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level. | `references/framework-fixes.md`
`references/visual-checklist.md` | diff --git a/skills/snowflake-semanticview/SKILL.md b/skills/snowflake-semanticview/SKILL.md index 17a40690..df468bc1 100644 --- a/skills/snowflake-semanticview/SKILL.md +++ b/skills/snowflake-semanticview/SKILL.md @@ -1,5 +1,5 @@ --- -name: snowflake-semantic-views +name: snowflake-semanticview description: Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup. --- From 54431b34e4b5defd6587cbc37e82becede898c7d Mon Sep 17 00:00:00 2001 From: Miguel P Z <60221874+MiguelElGallo@users.noreply.github.com> Date: Sun, 18 Jan 2026 14:11:36 +0200 Subject: [PATCH 4/5] Update skills/snowflake-semanticview/SKILL.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- skills/snowflake-semanticview/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/snowflake-semanticview/SKILL.md b/skills/snowflake-semanticview/SKILL.md index df468bc1..e2aae99b 100644 --- a/skills/snowflake-semanticview/SKILL.md +++ b/skills/snowflake-semanticview/SKILL.md @@ -22,7 +22,7 @@ description: Create, alter, and validate Snowflake semantic views using Snowflak - Read Snowflake table/view/column comments first (preferred source): - https://docs.snowflake.com/en/sql-reference/sql/comment - If comments or synonyms are missing, ask whether you can create them, whether the user wants to provide text, or whether you should draft suggestions for approval. -5. Use select statement with distinct and limit max 1000 rows, for finding out relationships between fact and dimension tables. Also to find out the data types of the columns. And lastly to create more meaningful comments/synonyms for the columns. +5. Use SELECT statements with DISTINCT and LIMIT (maximum 1000 rows) to discover relationships between fact and dimension tables, identify column data types, and create more meaningful comments and synonyms for columns. 6. Create a temporary validation name (for example, append `__tmp_validate`) while keeping the same database and schema. 7. Always validate by sending the DDL to Snowflake via Snowflake CLI before finalizing: - Use `snow sql` to execute the statement with the configured connection. From 6c059c1744fc077b4bee9ef7cd1e087125494906 Mon Sep 17 00:00:00 2001 From: Miguel P Z <60221874+MiguelElGallo@users.noreply.github.com> Date: Sun, 18 Jan 2026 14:12:03 +0200 Subject: [PATCH 5/5] Update skills/snowflake-semanticview/SKILL.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- skills/snowflake-semanticview/SKILL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/skills/snowflake-semanticview/SKILL.md b/skills/snowflake-semanticview/SKILL.md index e2aae99b..8f749381 100644 --- a/skills/snowflake-semanticview/SKILL.md +++ b/skills/snowflake-semanticview/SKILL.md @@ -37,8 +37,8 @@ SELECT * FROM SEMANTIC_VIEW( my_semview_name DIMENSIONS customer.customer_market_segment METRICS orders.order_average_value - ) - ORDER BY customer_market_segment; +) +ORDER BY customer_market_segment; ``` 11. Clean up any temporary semantic view created during validation.