[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7965DG3T8C5DYTP113F92JN":3,"skill-same:01M7965DG3T8C5DYTP113F92JN":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M7965DG3T8C5DYTP113F92JN","snowflake-known-pitfalls",null,"Identify and avoid Snowflake anti-patterns and common mistakes in SQL,\nwarehouse management, data loading, and access control.\nUse when reviewing Snowflake configurations, onboarding new users,\nor auditing existing Snowflake deployments for best practices.\nTrigger with phrases like \"snowflake mistakes\", \"snowflake anti-patterns\",\n\"snowflake pitfalls\", \"snowflake what not to do\", \"snowflake code review\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--snowflake-pack--snowflake-known-pitfalls\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: snowflake-known-pitfalls\ndescription: |\n  Identify and avoid Snowflake anti-patterns and common mistakes in SQL,\n  warehouse management, data loading, and access control.\n  Use when reviewing Snowflake configurations, onboarding new users,\n  or auditing existing Snowflake deployments for best practices.\n  Trigger with phrases like \"snowflake mistakes\", \"snowflake anti-patterns\",\n  \"snowflake pitfalls\", \"snowflake what not to do\", \"snowflake code review\".\nallowed-tools: Read, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, data-warehouse, analytics, snowflake]\ncompatible-with: claude-code\n---\n\n# Snowflake Known Pitfalls\n\n## Overview\n\nCommon mistakes and anti-patterns when using Snowflake, with real SQL examples and fixes.\n\n## Pitfall #1: Leaving Warehouses Running (Cost Killer)\n\n**Anti-Pattern:**\n```sql\n-- Warehouse with auto_suspend = 0 (never suspends)\nCREATE WAREHOUSE ALWAYS_ON_WH\n  WAREHOUSE_SIZE = 'XLARGE'\n  AUTO_SUSPEND = 0;\n-- 16 credits\u002Fhour = ~$1,152\u002Fday at $3\u002Fcredit\n```\n\n**Fix:**\n```sql\nALTER WAREHOUSE ALWAYS_ON_WH SET\n  AUTO_SUSPEND = 120,    -- Suspend after 2 min idle\n  AUTO_RESUME = TRUE;    -- Resume on next query\n\n-- Audit all warehouses for high auto_suspend\nSELECT name, size, auto_suspend, state\nFROM INFORMATION_SCHEMA.WAREHOUSES\nWHERE auto_suspend > 600 OR auto_suspend = 0;\n```\n\n---\n\n## Pitfall #2: Using ACCOUNTADMIN for Everything\n\n**Anti-Pattern:**\n```sql\n-- Human users with ACCOUNTADMIN default role\nALTER USER analyst SET DEFAULT_ROLE = 'ACCOUNTADMIN';\n-- One bad query can drop production databases\n```\n\n**Fix:**\n```sql\n-- Use least-privilege roles\nALTER USER analyst SET DEFAULT_ROLE = 'DATA_ANALYST';\n\n-- Audit ACCOUNTADMIN usage\nSELECT grantee_name, role\nFROM SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_USERS\nWHERE role = 'ACCOUNTADMIN' AND deleted_on IS NULL;\n-- Should be \u003C 3 users, all named admins\n```\n\n---\n\n## Pitfall #3: SELECT * on Wide Tables\n\n**Anti-Pattern:**\n```sql\n-- Scans ALL columns (Snowflake stores columnar — unused cols waste I\u002FO)\nSELECT * FROM events;  -- 200 columns, only need 3\n```\n\n**Fix:**\n```sql\n-- Select only needed columns — dramatically reduces bytes scanned\nSELECT event_id, event_type, event_timestamp FROM events;\n\n-- Check column pruning impact\nSELECT bytes_scanned FROM TABLE(INFORMATION_SCHEMA.QUERY_HISTORY_BY_SESSION())\nORDER BY start_time DESC LIMIT 1;\n```\n\n---\n\n## Pitfall #4: Clustering Keys on Small Tables\n\n**Anti-Pattern:**\n```sql\n-- Clustering key on a 10,000 row table\nALTER TABLE config_settings CLUSTER BY (category);\n-- Costs credits for reclustering with zero performance benefit\n```\n\n**Fix:**\n```sql\n-- Only cluster tables > 1TB with frequent filter queries\n-- Check table size before clustering\nSELECT table_name, row_count, bytes \u002F 1e9 AS gb\nFROM INFORMATION_SCHEMA.TABLES\nWHERE table_name = 'CONFIG_SETTINGS';\n-- If \u003C 1 GB, clustering is waste\n\n-- Remove unnecessary clustering\nALTER TABLE config_settings DROP CLUSTERING KEY;\n```\n\n---\n\n## Pitfall #5: Not Using MERGE for Idempotent Loads\n\n**Anti-Pattern:**\n```sql\n-- INSERT creates duplicates on retry\nINSERT INTO dim_orders SELECT * FROM staging_orders;\n-- Network blip → retry → duplicate rows\n```\n\n**Fix:**\n```sql\n-- MERGE is idempotent — safe to retry\nMERGE INTO dim_orders AS target\nUSING staging_orders AS source\nON target.order_id = source.order_id\nWHEN MATCHED THEN UPDATE SET\n  target.amount = source.amount,\n  target.updated_at = CURRENT_TIMESTAMP()\nWHEN NOT MATCHED THEN INSERT\n  (order_id, amount, created_at)\nVALUES (source.order_id, source.amount, CURRENT_TIMESTAMP());\n```\n\n---\n\n## Pitfall #6: Ignoring Stale Streams\n\n**Anti-Pattern:**\n```sql\n-- Stream goes stale when retention period is exceeded\n-- (source table changes exceed DATA_RETENTION_TIME_IN_DAYS)\n-- Result: DATA LOSS — changes between old and new offset are gone\n```\n\n**Fix:**\n```sql\n-- Monitor stream staleness\nSELECT stream_name, stale\nFROM INFORMATION_SCHEMA.STREAMS\nWHERE stale = TRUE;\n\n-- Increase retention on source tables\nALTER TABLE raw_orders SET DATA_RETENTION_TIME_IN_DAYS = 14;\n\n-- Set up alert for stale streams\nCREATE ALERT stale_stream_alert\n  WAREHOUSE = ADMIN_WH\n  SCHEDULE = '30 MINUTE'\n  IF (EXISTS (SELECT 1 FROM INFORMATION_SCHEMA.STREAMS WHERE stale = TRUE))\n  THEN CALL SYSTEM$SEND_EMAIL(...);\n```\n\n---\n\n## Pitfall #7: Loading Many Small Files\n\n**Anti-Pattern:**\n```bash\n# 100,000 small files (\u003C 100KB each) in stage\n# Each file = separate micro-partition = metadata overhead\n```\n\n**Fix:**\n```sql\n-- Combine small files before loading\n-- Or use Snowpipe with recommended file sizes (100-250 MB)\n\n-- Check COPY history for file size issues\nSELECT file_name, file_size, row_count\nFROM TABLE(INFORMATION_SCHEMA.COPY_HISTORY(\n  TABLE_NAME => 'MY_TABLE',\n  START_TIME => DATEADD(hours, -24, CURRENT_TIMESTAMP())\n))\nWHERE file_size \u003C 100000  -- Files under 100KB\nORDER BY file_size;\n```\n\n---\n\n## Pitfall #8: No Resource Monitors\n\n**Anti-Pattern:**\n```sql\n-- No resource monitors = unlimited credit consumption\n-- A runaway query or always-on warehouse can burn thousands of credits\n```\n\n**Fix:**\n```sql\nCREATE RESOURCE MONITOR monthly_budget\n  WITH CREDIT_QUOTA = 2000\n  FREQUENCY = MONTHLY\n  START_TIMESTAMP = IMMEDIATELY\n  TRIGGERS\n    ON 75 PERCENT DO NOTIFY\n    ON 100 PERCENT DO SUSPEND\n    ON 110 PERCENT DO SUSPEND_IMMEDIATE;\n\nALTER ACCOUNT SET RESOURCE_MONITOR = monthly_budget;\n```\n\n---\n\n## Pitfall #9: Using Transient Tables for Important Data\n\n**Anti-Pattern:**\n```sql\n-- Transient tables have NO Fail-safe (7 days of extra recovery)\n-- and max 1 day of Time Travel\nCREATE TRANSIENT TABLE critical_orders (...);\n-- Data loss risk if table is accidentally dropped after 1 day\n```\n\n**Fix:**\n```sql\n-- Use permanent tables for important data\nCREATE TABLE critical_orders (...);\nALTER TABLE critical_orders SET DATA_RETENTION_TIME_IN_DAYS = 14;\n\n-- Use transient only for truly temporary data\nCREATE TRANSIENT TABLE temp_staging_batch (...);\n```\n\n---\n\n## Pitfall #10: Wrong Account Identifier Format\n\n**Anti-Pattern:**\n```typescript\n\u002F\u002F Using the full URL instead of account identifier\nconst conn = snowflake.createConnection({\n  account: 'myaccount.us-east-1.snowflakecomputing.com',  \u002F\u002F WRONG\n});\n\u002F\u002F Results in: \"Could not connect to Snowflake backend\"\n```\n\n**Fix:**\n```typescript\nconst conn = snowflake.createConnection({\n  account: 'myorg-myaccount',  \u002F\u002F Correct: orgname-accountname format\n});\n\u002F\u002F For legacy locator format: 'xy12345.us-east-1' (include region)\n```\n\n## Quick Audit Script\n\n```sql\n-- Run this monthly to catch common pitfalls\nSELECT 'Always-on warehouses' AS check,\n       COUNT(*) AS issues\nFROM INFORMATION_SCHEMA.WAREHOUSES\nWHERE auto_suspend = 0 OR auto_suspend > 3600\n\nUNION ALL\n\nSELECT 'ACCOUNTADMIN default role',\n       COUNT(*)\nFROM SNOWFLAKE.ACCOUNT_USAGE.USERS\nWHERE default_role = 'ACCOUNTADMIN' AND disabled = 'false'\n\nUNION ALL\n\nSELECT 'Stale streams',\n       COUNT(*)\nFROM INFORMATION_SCHEMA.STREAMS\nWHERE stale = TRUE\n\nUNION ALL\n\nSELECT 'No resource monitor',\n       CASE WHEN COUNT(*) = 0 THEN 1 ELSE 0 END\nFROM INFORMATION_SCHEMA.RESOURCE_MONITORS\n\nUNION ALL\n\nSELECT 'Tables without clustering (>1TB)',\n       COUNT(*)\nFROM INFORMATION_SCHEMA.TABLES\nWHERE bytes > 1e12\n  AND auto_clustering_on = 'NO';\n```\n\n## Quick Reference Card\n\n| Pitfall | Detection | Prevention |\n|---------|-----------|------------|\n| Always-on warehouse | `auto_suspend = 0` | Set 60-300s |\n| ACCOUNTADMIN abuse | `GRANTS_TO_USERS` audit | Enforce least privilege |\n| SELECT * | High `bytes_scanned` | Column pruning |\n| Unnecessary clustering | Small table \u003C 1TB | Only cluster large tables |\n| INSERT duplicates | Row count mismatch | Use MERGE |\n| Stale streams | `stale = TRUE` | Increase retention |\n| Small files | COPY_HISTORY file_size | Batch files to 100-250MB |\n| No resource monitor | Account check | Create immediately |\n| Transient for critical data | Table type audit | Use permanent tables |\n| Wrong account format | Connection error | Use `orgname-accountname` |\n\n## Resources\n\n- [Warehouse Considerations](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Fwarehouses-considerations)\n- [Access Control Best Practices](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Fsecurity-access-control-considerations)\n- [Data Loading Best Practices](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Fdata-load-considerations-prepare)\n","# Snowflake Known Pitfalls\n\n## Overview\n\nCommon mistakes and anti-patterns when using Snowflake, with real SQL examples and fixes.\n\n## Pitfall #1: Leaving Warehouses Running (Cost Killer)\n\n**Anti-Pattern:**\n```sql\n-- Warehouse with auto_suspend = 0 (never suspends)\nCREATE WAREHOUSE ALWAYS_ON_WH\n  WAREHOUSE_SIZE = 'XLARGE'\n  AUTO_SUSPEND = 0;\n-- 16 credits\u002Fhour = ~$1,152\u002Fday at $3\u002Fcredit\n```\n\n**Fix:**\n```sql\nALTER WAREHOUSE ALWAYS_ON_WH SET\n  AUTO_SUSPEND = 120,    -- Suspend after 2 min idle\n  AUTO_RESUME = TRUE;    -- Resume on next query\n\n-- Audit all warehouses for high auto_suspend\nSELECT name, size, auto_suspend, state\nFROM INFORMATION_SCHEMA.WAREHOUSES\nWHERE auto_suspend > 600 OR auto_suspend = 0;\n```\n\n---\n\n## Pitfall #2: Using ACCOUNTADMIN for Everything\n\n**Anti-Pattern:**\n```sql\n-- Human users with ACCOUNTADMIN default role\nALTER USER analyst SET DEFAULT_ROLE = 'ACCOUNTADMIN';\n-- One bad query can drop production databases\n```\n\n**Fix:**\n```sql\n-- Use least-privilege roles\nALTER USER analyst SET DEFAULT_ROLE = 'DATA_ANALYST';\n\n-- Audit ACCOUNTADMIN usage\nSELECT grantee_name, role\nFROM SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_USERS\nWHERE role = 'ACCOUNTADMIN' AND deleted_on IS NULL;\n-- Should be \u003C 3 users, all named admins\n```\n\n---\n\n## Pitfall #3: SELECT * on Wide Tables\n\n**Anti-Pattern:**\n```sql\n-- Scans ALL columns (Snowflake stores columnar — unused cols waste I\u002FO)\nSELECT * FROM events;  -- 200 columns, only need 3\n```\n\n**Fix:**\n```sql\n-- Select only needed columns — dramatically reduces bytes scanned\nSELECT event_id, event_type, event_timestamp FROM events;\n\n-- Check column pruning impact\nSELECT bytes_scanned FROM TABLE(INFORMATION_SCHEMA.QUERY_HISTORY_BY_SESSION())\nORDER BY start_time DESC LIMIT 1;\n```\n\n---\n\n## Pitfall #4: Clustering Keys on Small Tables\n\n**Anti-Pattern:**\n```sql\n-- Clustering key on a 10,000 row table\nALTER TABLE config_settings CLUSTER BY (category);\n-- Costs credits for reclustering with zero performance benefit\n```\n\n**Fix:**\n```sql\n-- Only cluster tables > 1TB with frequent filter queries\n-- Check table size before clustering\nSELECT table_name, row_count, bytes \u002F 1e9 AS gb\nFROM INFORMATION_SCHEMA.TABLES\nWHERE table_name = 'CONFIG_SETTINGS';\n-- If \u003C 1 GB, clustering is waste\n\n-- Remove unnecessary clustering\nALTER TABLE config_settings DROP CLUSTERING KEY;\n```\n\n---\n\n## Pitfall #5: Not Using MERGE for Idempotent Loads\n\n**Anti-Pattern:**\n```sql\n-- INSERT creates duplicates on retry\nINSERT INTO dim_orders SELECT * FROM staging_orders;\n-- Network blip → retry → duplicate rows\n```\n\n**Fix:**\n```sql\n-- MERGE is idempotent — safe to retry\nMERGE INTO dim_orders AS target\nUSING staging_orders AS source\nON target.order_id = source.order_id\nWHEN MATCHED THEN UPDATE SET\n  target.amount = source.amount,\n  target.updated_at = CURRENT_TIMESTAMP()\nWHEN NOT MATCHED THEN INSERT\n  (order_id, amount, created_at)\nVALUES (source.order_id, source.amount, CURRENT_TIMESTAMP());\n```\n\n---\n\n## Pitfall #6: Ignoring Stale Streams\n\n**Anti-Pattern:**\n```sql\n-- Stream goes stale when retention period is exceeded\n-- (source table changes exceed DATA_RETENTION_TIME_IN_DAYS)\n-- Result: DATA LOSS — changes between old and new offset are gone\n```\n\n**Fix:**\n```sql\n-- Monitor stream staleness\nSELECT stream_name, stale\nFROM INFORMATION_SCHEMA.STREAMS\nWHERE stale = TRUE;\n\n-- Increase retention on source tables\nALTER TABLE raw_orders SET DATA_RETENTION_TIME_IN_DAYS = 14;\n\n-- Set up alert for stale streams\nCREATE ALERT stale_stream_alert\n  WAREHOUSE = ADMIN_WH\n  SCHEDULE = '30 MINUTE'\n  IF (EXISTS (SELECT 1 FROM INFORMATION_SCHEMA.STREAMS WHERE stale = TRUE))\n  THEN CALL SYSTEM$SEND_EMAIL(...);\n```\n\n---\n\n## Pitfall #7: Loading Many Small Files\n\n**Anti-Pattern:**\n```bash\n# 100,000 small files (\u003C 100KB each) in stage\n# Each file = separate micro-partition = metadata overhead\n```\n\n**Fix:**\n```sql\n-- Combine small files before loading\n-- Or use Snowpipe with recommended file sizes (100-250 MB)\n\n-- Check COPY history for file size issues\nSELECT file_name, file_size, row_count\nFROM TABLE(INFORMATION_SCHEMA.COPY_HISTORY(\n  TABLE_NAME => 'MY_TABLE',\n  START_TIME => DATEADD(hours, -24, CURRENT_TIMESTAMP())\n))\nWHERE file_size \u003C 100000  -- Files under 100KB\nORDER BY file_size;\n```\n\n---\n\n## Pitfall #8: No Resource Monitors\n\n**Anti-Pattern:**\n```sql\n-- No resource monitors = unlimited credit consumption\n-- A runaway query or always-on warehouse can burn thousands of credits\n```\n\n**Fix:**\n```sql\nCREATE RESOURCE MONITOR monthly_budget\n  WITH CREDIT_QUOTA = 2000\n  FREQUENCY = MONTHLY\n  START_TIMESTAMP = IMMEDIATELY\n  TRIGGERS\n    ON 75 PERCENT DO NOTIFY\n    ON 100 PERCENT DO SUSPEND\n    ON 110 PERCENT DO SUSPEND_IMMEDIATE;\n\nALTER ACCOUNT SET RESOURCE_MONITOR = monthly_budget;\n```\n\n---\n\n## Pitfall #9: Using Transient Tables for Important Data\n\n**Anti-Pattern:**\n```sql\n-- Transient tables have NO Fail-safe (7 days of extra recovery)\n-- and max 1 day of Time Travel\nCREATE TRANSIENT TABLE critical_orders (...);\n-- Data loss risk if table is accidentally dropped after 1 day\n```\n\n**Fix:**\n```sql\n-- Use permanent tables for important data\nCREATE TABLE critical_orders (...);\nALTER TABLE critical_orders SET DATA_RETENTION_TIME_IN_DAYS = 14;\n\n-- Use transient only for truly temporary data\nCREATE TRANSIENT TABLE temp_staging_batch (...);\n```\n\n---\n\n## Pitfall #10: Wrong Account Identifier Format\n\n**Anti-Pattern:**\n```typescript\n\u002F\u002F Using the full URL instead of account identifier\nconst conn = snowflake.createConnection({\n  account: 'myaccount.us-east-1.snowflakecomputing.com',  \u002F\u002F WRONG\n});\n\u002F\u002F Results in: \"Could not connect to Snowflake backend\"\n```\n\n**Fix:**\n```typescript\nconst conn = snowflake.createConnection({\n  account: 'myorg-myaccount',  \u002F\u002F Correct: orgname-accountname format\n});\n\u002F\u002F For legacy locator format: 'xy12345.us-east-1' (include region)\n```\n\n## Quick Audit Script\n\n```sql\n-- Run this monthly to catch common pitfalls\nSELECT 'Always-on warehouses' AS check,\n       COUNT(*) AS issues\nFROM INFORMATION_SCHEMA.WAREHOUSES\nWHERE auto_suspend = 0 OR auto_suspend > 3600\n\nUNION ALL\n\nSELECT 'ACCOUNTADMIN default role',\n       COUNT(*)\nFROM SNOWFLAKE.ACCOUNT_USAGE.USERS\nWHERE default_role = 'ACCOUNTADMIN' AND disabled = 'false'\n\nUNION ALL\n\nSELECT 'Stale streams',\n       COUNT(*)\nFROM INFORMATION_SCHEMA.STREAMS\nWHERE stale = TRUE\n\nUNION ALL\n\nSELECT 'No resource monitor',\n       CASE WHEN COUNT(*) = 0 THEN 1 ELSE 0 END\nFROM INFORMATION_SCHEMA.RESOURCE_MONITORS\n\nUNION ALL\n\nSELECT 'Tables without clustering (>1TB)',\n       COUNT(*)\nFROM INFORMATION_SCHEMA.TABLES\nWHERE bytes > 1e12\n  AND auto_clustering_on = 'NO';\n```\n\n## Quick Reference Card\n\n| Pitfall | Detection | Prevention |\n|---------|-----------|------------|\n| Always-on warehouse | `auto_suspend = 0` | Set 60-300s |\n| ACCOUNTADMIN abuse | `GRANTS_TO_USERS` audit | Enforce least privilege |\n| SELECT * | High `bytes_scanned` | Column pruning |\n| Unnecessary clustering | Small table \u003C 1TB | Only cluster large tables |\n| INSERT duplicates | Row count mismatch | Use MERGE |\n| Stale streams | `stale = TRUE` | Increase retention |\n| Small files | COPY_HISTORY file_size | Batch files to 100-250MB |\n| No resource monitor | Account check | Create immediately |\n| Transient for critical data | Table type audit | Use permanent tables |\n| Wrong account format | Connection error | Use `orgname-accountname` |\n\n## Resources\n\n- [Warehouse Considerations](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Fwarehouses-considerations)\n- [Access Control Best Practices](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Fsecurity-access-control-considerations)\n- [Data Loading Best Practices](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Fdata-load-considerations-prepare)\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","data-warehouse","analytics","snowflake","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Identify and avoid Snowflake anti-patterns and common mistakes in SQL,\nwarehouse management, data loading, and access control.\nUse when reviewing Snowflake configurations, onboarding new users,\nor auditing existing Snowflake deployments for best practices.\nTrigger with phrases like \"snowflake mistakes\", \"snowflake anti-patterns\",\n\"snowflake pitfalls\", \"snowflake what not to do\", \"snowflake code review\".\n","Read, Grep","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--snowflake-pack--snowflake-known-pitfalls",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill snowflake-known-pitfalls",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill snowflake-known-pitfalls",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill snowflake-known-pitfalls","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--snowflake-pack--snowflake-known-pitfalls\u002FSKILL.md",true,[],[58,65,72,79,86,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]