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] 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.