[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7966CAP0EKK3E2EX2Z87TX3":3,"skill-same:01M7966CAP0EKK3E2EX2Z87TX3":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},"01M7966CAP0EKK3E2EX2Z87TX3","snowflake-performance-tuning",null,"Optimize Snowflake query performance with clustering, materialized views, caching, and query profiling.\nUse when queries are slow, analyzing QUERY_HISTORY for bottlenecks,\nor optimizing warehouse utilization and data scanning.\nTrigger with phrases like \"snowflake performance\", \"optimize snowflake\",\n\"snowflake slow query\", \"snowflake clustering\", \"snowflake query profile\".","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-performance-tuning\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: snowflake-performance-tuning\ndescription: |\n  Optimize Snowflake query performance with clustering, materialized views, caching, and query profiling.\n  Use when queries are slow, analyzing QUERY_HISTORY for bottlenecks,\n  or optimizing warehouse utilization and data scanning.\n  Trigger with phrases like \"snowflake performance\", \"optimize snowflake\",\n  \"snowflake slow query\", \"snowflake clustering\", \"snowflake query profile\".\nallowed-tools: Read, Write, Edit\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 Performance Tuning\n\n## Overview\n\nOptimize Snowflake query performance using clustering keys, materialized views, result caching, query profiling, and warehouse tuning.\n\n## Prerequisites\n\n- Access to `SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY`\n- Understanding of micro-partitions and pruning\n- Role with `MONITOR` privilege on warehouses\n\n## Instructions\n\n### Step 1: Identify Slow Queries\n\n```sql\n-- Top 20 slowest queries in last 24 hours\nSELECT query_id, query_text, total_elapsed_time \u002F 1000 AS seconds,\n       bytes_scanned \u002F 1e9 AS gb_scanned,\n       partitions_scanned, partitions_total,\n       ROUND(partitions_scanned \u002F NULLIF(partitions_total, 0) * 100, 1) AS pct_scanned,\n       warehouse_name, warehouse_size\nFROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY\nWHERE execution_status = 'SUCCESS'\n  AND start_time >= DATEADD(hours, -24, CURRENT_TIMESTAMP())\n  AND query_type = 'SELECT'\nORDER BY total_elapsed_time DESC\nLIMIT 20;\n\n-- Queries scanning too many partitions (poor pruning)\nSELECT query_id, query_text,\n       partitions_scanned, partitions_total,\n       bytes_scanned \u002F 1e9 AS gb_scanned\nFROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY\nWHERE partitions_scanned > partitions_total * 0.5\n  AND partitions_total > 100\n  AND start_time >= DATEADD(hours, -24, CURRENT_TIMESTAMP())\nORDER BY partitions_scanned DESC\nLIMIT 10;\n```\n\n### Step 2: Add Clustering Keys\n\n```sql\n-- Clustering improves pruning for large tables (> 1TB)\n-- Choose columns used in WHERE and JOIN clauses\n\n-- Cluster by date (most common filter)\nALTER TABLE orders CLUSTER BY (order_date);\n\n-- Multi-column clustering\nALTER TABLE events CLUSTER BY (event_date, event_type);\n\n-- Check clustering depth (lower = better)\nSELECT SYSTEM$CLUSTERING_INFORMATION('orders', '(order_date)');\n\n-- Monitor automatic reclustering\nSELECT table_name, num_rows, bytes,\n       SYSTEM$CLUSTERING_DEPTH('orders') AS clustering_depth\nFROM INFORMATION_SCHEMA.TABLES\nWHERE table_name = 'ORDERS';\n```\n\n### Step 3: Use Materialized Views\n\n```sql\n-- Pre-compute expensive aggregations\nCREATE OR REPLACE MATERIALIZED VIEW daily_revenue_mv\n  CLUSTER BY (metric_date)\nAS\n  SELECT\n    DATE_TRUNC('day', order_date) AS metric_date,\n    COUNT(*) AS order_count,\n    SUM(amount) AS total_revenue,\n    AVG(amount) AS avg_order_value\n  FROM orders\n  GROUP BY DATE_TRUNC('day', order_date);\n\n-- Query the MV instead of base table — automatic rewrite may also apply\nSELECT * FROM daily_revenue_mv\nWHERE metric_date >= DATEADD(days, -30, CURRENT_DATE());\n\n-- Check MV freshness\nSELECT name, is_secure, text, refresh_on\nFROM INFORMATION_SCHEMA.MATERIALIZED_VIEWS\nWHERE name = 'DAILY_REVENUE_MV';\n```\n\n### Step 4: Leverage Result Caching\n\n```sql\n-- Result cache is ON by default — same query returns instantly\n-- Cache is valid for 24 hours if underlying data hasn't changed\n\n-- Check if a query used cache\nSELECT query_id, query_text,\n       CASE WHEN bytes_scanned = 0 AND rows_produced > 0\n            THEN 'CACHE HIT' ELSE 'CACHE MISS' END AS cache_status,\n       total_elapsed_time\nFROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY\nWHERE start_time >= DATEADD(hours, -1, CURRENT_TIMESTAMP())\nORDER BY start_time DESC;\n\n-- Disable cache for benchmarking\nALTER SESSION SET USE_CACHED_RESULT = FALSE;\n-- Re-enable\nALTER SESSION SET USE_CACHED_RESULT = TRUE;\n```\n\n### Step 5: Optimize Common Query Patterns\n\n```sql\n-- ANTI-PATTERN: SELECT * on wide tables\n-- SELECT * FROM events;  -- Scans all columns\n\n-- BETTER: Select only needed columns\nSELECT event_id, event_type, event_date FROM events WHERE event_date = CURRENT_DATE();\n\n-- ANTI-PATTERN: Cartesian joins\n-- SELECT * FROM a, b WHERE a.id = b.id;\n\n-- BETTER: Explicit JOIN with filter pushdown\nSELECT a.id, a.name, b.amount\nFROM customers a\nINNER JOIN orders b ON a.id = b.customer_id\nWHERE b.order_date >= '2026-01-01';\n\n-- ANTI-PATTERN: LIKE with leading wildcard\n-- WHERE name LIKE '%smith%'  -- Full scan\n\n-- BETTER: Use search optimization service for LIKE queries\nALTER TABLE customers ADD SEARCH OPTIMIZATION ON EQUALITY(name), SUBSTRING(name);\n\n-- ANTI-PATTERN: Many small queries in a loop\n-- for row in rows: execute(f\"INSERT INTO t VALUES ({row})\")\n\n-- BETTER: Batch inserts\nINSERT INTO target_table\nSELECT * FROM source_table WHERE condition;\n```\n\n### Step 6: Query Profile Analysis\n\n```sql\n-- Use EXPLAIN to see execution plan\nEXPLAIN SELECT * FROM orders WHERE order_date = CURRENT_DATE();\n\n-- Get query profile data programmatically\nSELECT *\nFROM TABLE(GET_QUERY_OPERATOR_STATS('\u003Cquery_id>'));\n\n-- Key metrics to watch:\n-- TableScan: partitions_scanned vs partitions_total\n-- Filter: if filter is AFTER scan, consider clustering\n-- Sort: high spilling_to_remote_storage = needs bigger warehouse\n-- Join: broadcast vs hash, skew detection\n```\n\n### Step 7: Warehouse Tuning\n\n```sql\n-- Match warehouse size to workload\n-- Small: simple queries, \u003C 100GB scans\n-- Medium: moderate joins, 100GB-1TB\n-- Large: complex analytics, > 1TB scans\n\n-- Scale up for single-query performance\nALTER WAREHOUSE ANALYTICS_WH SET WAREHOUSE_SIZE = 'LARGE';\n\n-- Scale out for concurrent queries (multi-cluster)\nALTER WAREHOUSE ANALYTICS_WH SET\n  MIN_CLUSTER_COUNT = 1\n  MAX_CLUSTER_COUNT = 4\n  SCALING_POLICY = 'STANDARD';\n\n-- Monitor warehouse efficiency\nSELECT warehouse_name,\n       SUM(credits_used) AS total_credits,\n       COUNT(DISTINCT query_id) AS total_queries,\n       SUM(credits_used) \u002F NULLIF(COUNT(DISTINCT query_id), 0) AS credits_per_query\nFROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY q\nJOIN SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY w\n  ON q.warehouse_name = w.warehouse_name\n  AND DATE_TRUNC('hour', q.start_time) = w.start_time\nWHERE q.start_time >= DATEADD(days, -7, CURRENT_TIMESTAMP())\nGROUP BY warehouse_name\nORDER BY total_credits DESC;\n```\n\n## Performance Benchmarks\n\n| Optimization | Typical Improvement |\n|-------------|-------------------|\n| Clustering key on filter column | 10-100x fewer partitions scanned |\n| Materialized view | 10-1000x for aggregation queries |\n| Result cache hit | Instant (0ms scan) |\n| Column pruning (SELECT specific cols) | 2-10x less data scanned |\n| Search optimization service | 10-100x for point lookups |\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Spilling to disk | Warehouse too small for query | Scale up warehouse size |\n| High partition scan ratio | No clustering on filter column | Add clustering key |\n| MV stale | Background refresh delayed | Check MV refresh status |\n| Cache miss on same query | Data changed or session setting | Verify `USE_CACHED_RESULT = TRUE` |\n\n## Resources\n\n- [Query Performance](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Fperformance-query-exploring)\n- [Clustering Keys](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Ftables-clustering-keys)\n- [Materialized Views](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Fviews-materialized)\n- [Search Optimization](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Fsearch-optimization-service)\n\n## Next Steps\n\nFor cost optimization, see `snowflake-cost-tuning`.\n","# Snowflake Performance Tuning\n\n## Overview\n\nOptimize Snowflake query performance using clustering keys, materialized views, result caching, query profiling, and warehouse tuning.\n\n## Prerequisites\n\n- Access to `SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY`\n- Understanding of micro-partitions and pruning\n- Role with `MONITOR` privilege on warehouses\n\n## Instructions\n\n### Step 1: Identify Slow Queries\n\n```sql\n-- Top 20 slowest queries in last 24 hours\nSELECT query_id, query_text, total_elapsed_time \u002F 1000 AS seconds,\n       bytes_scanned \u002F 1e9 AS gb_scanned,\n       partitions_scanned, partitions_total,\n       ROUND(partitions_scanned \u002F NULLIF(partitions_total, 0) * 100, 1) AS pct_scanned,\n       warehouse_name, warehouse_size\nFROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY\nWHERE execution_status = 'SUCCESS'\n  AND start_time >= DATEADD(hours, -24, CURRENT_TIMESTAMP())\n  AND query_type = 'SELECT'\nORDER BY total_elapsed_time DESC\nLIMIT 20;\n\n-- Queries scanning too many partitions (poor pruning)\nSELECT query_id, query_text,\n       partitions_scanned, partitions_total,\n       bytes_scanned \u002F 1e9 AS gb_scanned\nFROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY\nWHERE partitions_scanned > partitions_total * 0.5\n  AND partitions_total > 100\n  AND start_time >= DATEADD(hours, -24, CURRENT_TIMESTAMP())\nORDER BY partitions_scanned DESC\nLIMIT 10;\n```\n\n### Step 2: Add Clustering Keys\n\n```sql\n-- Clustering improves pruning for large tables (> 1TB)\n-- Choose columns used in WHERE and JOIN clauses\n\n-- Cluster by date (most common filter)\nALTER TABLE orders CLUSTER BY (order_date);\n\n-- Multi-column clustering\nALTER TABLE events CLUSTER BY (event_date, event_type);\n\n-- Check clustering depth (lower = better)\nSELECT SYSTEM$CLUSTERING_INFORMATION('orders', '(order_date)');\n\n-- Monitor automatic reclustering\nSELECT table_name, num_rows, bytes,\n       SYSTEM$CLUSTERING_DEPTH('orders') AS clustering_depth\nFROM INFORMATION_SCHEMA.TABLES\nWHERE table_name = 'ORDERS';\n```\n\n### Step 3: Use Materialized Views\n\n```sql\n-- Pre-compute expensive aggregations\nCREATE OR REPLACE MATERIALIZED VIEW daily_revenue_mv\n  CLUSTER BY (metric_date)\nAS\n  SELECT\n    DATE_TRUNC('day', order_date) AS metric_date,\n    COUNT(*) AS order_count,\n    SUM(amount) AS total_revenue,\n    AVG(amount) AS avg_order_value\n  FROM orders\n  GROUP BY DATE_TRUNC('day', order_date);\n\n-- Query the MV instead of base table — automatic rewrite may also apply\nSELECT * FROM daily_revenue_mv\nWHERE metric_date >= DATEADD(days, -30, CURRENT_DATE());\n\n-- Check MV freshness\nSELECT name, is_secure, text, refresh_on\nFROM INFORMATION_SCHEMA.MATERIALIZED_VIEWS\nWHERE name = 'DAILY_REVENUE_MV';\n```\n\n### Step 4: Leverage Result Caching\n\n```sql\n-- Result cache is ON by default — same query returns instantly\n-- Cache is valid for 24 hours if underlying data hasn't changed\n\n-- Check if a query used cache\nSELECT query_id, query_text,\n       CASE WHEN bytes_scanned = 0 AND rows_produced > 0\n            THEN 'CACHE HIT' ELSE 'CACHE MISS' END AS cache_status,\n       total_elapsed_time\nFROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY\nWHERE start_time >= DATEADD(hours, -1, CURRENT_TIMESTAMP())\nORDER BY start_time DESC;\n\n-- Disable cache for benchmarking\nALTER SESSION SET USE_CACHED_RESULT = FALSE;\n-- Re-enable\nALTER SESSION SET USE_CACHED_RESULT = TRUE;\n```\n\n### Step 5: Optimize Common Query Patterns\n\n```sql\n-- ANTI-PATTERN: SELECT * on wide tables\n-- SELECT * FROM events;  -- Scans all columns\n\n-- BETTER: Select only needed columns\nSELECT event_id, event_type, event_date FROM events WHERE event_date = CURRENT_DATE();\n\n-- ANTI-PATTERN: Cartesian joins\n-- SELECT * FROM a, b WHERE a.id = b.id;\n\n-- BETTER: Explicit JOIN with filter pushdown\nSELECT a.id, a.name, b.amount\nFROM customers a\nINNER JOIN orders b ON a.id = b.customer_id\nWHERE b.order_date >= '2026-01-01';\n\n-- ANTI-PATTERN: LIKE with leading wildcard\n-- WHERE name LIKE '%smith%'  -- Full scan\n\n-- BETTER: Use search optimization service for LIKE queries\nALTER TABLE customers ADD SEARCH OPTIMIZATION ON EQUALITY(name), SUBSTRING(name);\n\n-- ANTI-PATTERN: Many small queries in a loop\n-- for row in rows: execute(f\"INSERT INTO t VALUES ({row})\")\n\n-- BETTER: Batch inserts\nINSERT INTO target_table\nSELECT * FROM source_table WHERE condition;\n```\n\n### Step 6: Query Profile Analysis\n\n```sql\n-- Use EXPLAIN to see execution plan\nEXPLAIN SELECT * FROM orders WHERE order_date = CURRENT_DATE();\n\n-- Get query profile data programmatically\nSELECT *\nFROM TABLE(GET_QUERY_OPERATOR_STATS('\u003Cquery_id>'));\n\n-- Key metrics to watch:\n-- TableScan: partitions_scanned vs partitions_total\n-- Filter: if filter is AFTER scan, consider clustering\n-- Sort: high spilling_to_remote_storage = needs bigger warehouse\n-- Join: broadcast vs hash, skew detection\n```\n\n### Step 7: Warehouse Tuning\n\n```sql\n-- Match warehouse size to workload\n-- Small: simple queries, \u003C 100GB scans\n-- Medium: moderate joins, 100GB-1TB\n-- Large: complex analytics, > 1TB scans\n\n-- Scale up for single-query performance\nALTER WAREHOUSE ANALYTICS_WH SET WAREHOUSE_SIZE = 'LARGE';\n\n-- Scale out for concurrent queries (multi-cluster)\nALTER WAREHOUSE ANALYTICS_WH SET\n  MIN_CLUSTER_COUNT = 1\n  MAX_CLUSTER_COUNT = 4\n  SCALING_POLICY = 'STANDARD';\n\n-- Monitor warehouse efficiency\nSELECT warehouse_name,\n       SUM(credits_used) AS total_credits,\n       COUNT(DISTINCT query_id) AS total_queries,\n       SUM(credits_used) \u002F NULLIF(COUNT(DISTINCT query_id), 0) AS credits_per_query\nFROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY q\nJOIN SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY w\n  ON q.warehouse_name = w.warehouse_name\n  AND DATE_TRUNC('hour', q.start_time) = w.start_time\nWHERE q.start_time >= DATEADD(days, -7, CURRENT_TIMESTAMP())\nGROUP BY warehouse_name\nORDER BY total_credits DESC;\n```\n\n## Performance Benchmarks\n\n| Optimization | Typical Improvement |\n|-------------|-------------------|\n| Clustering key on filter column | 10-100x fewer partitions scanned |\n| Materialized view | 10-1000x for aggregation queries |\n| Result cache hit | Instant (0ms scan) |\n| Column pruning (SELECT specific cols) | 2-10x less data scanned |\n| Search optimization service | 10-100x for point lookups |\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Spilling to disk | Warehouse too small for query | Scale up warehouse size |\n| High partition scan ratio | No clustering on filter column | Add clustering key |\n| MV stale | Background refresh delayed | Check MV refresh status |\n| Cache miss on same query | Data changed or session setting | Verify `USE_CACHED_RESULT = TRUE` |\n\n## Resources\n\n- [Query Performance](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Fperformance-query-exploring)\n- [Clustering Keys](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Ftables-clustering-keys)\n- [Materialized Views](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Fviews-materialized)\n- [Search Optimization](https:\u002F\u002Fdocs.snowflake.com\u002Fen\u002Fuser-guide\u002Fsearch-optimization-service)\n\n## Next Steps\n\nFor cost optimization, see `snowflake-cost-tuning`.\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","Optimize Snowflake query performance with clustering, materialized views, caching, and query profiling.\nUse when queries are slow, analyzing QUERY_HISTORY for bottlenecks,\nor optimizing warehouse utilization and data scanning.\nTrigger with phrases like \"snowflake performance\", \"optimize snowflake\",\n\"snowflake slow query\", \"snowflake clustering\", \"snowflake query profile\".\n","Read, Write, Edit","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--snowflake-pack--snowflake-performance-tuning",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-performance-tuning",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill snowflake-performance-tuning",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill snowflake-performance-tuning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--snowflake-pack--snowflake-performance-tuning\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",[],[]]