Agent skill

snowflake-rate-limits

Handle Snowflake concurrency limits, warehouse queuing, and query throttling. Use when queries are queuing, hitting concurrency limits, or needing to optimize warehouse sizing for throughput. Trigger with phrases like "snowflake rate limit", "snowflake throttling", "snowflake queuing", "snowflake concurrency", "snowflake warehouse sizing". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill snowflake-rate-limits --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Version: 1.5.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEdit
Requires: Designed for Claude Code
Path: plugins/saas-packs/snowflake-pack/skills/snowflake-rate-limits/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Snowflake Rate Limits & Concurrency ## Overview Snowflake doesn't use traditional API rate limits. Instead, concurrency is governed by warehouse size, multi-cluster configuration, and per-session/account limits. ## Key Limits | Resource | Limit | Notes | |----------|-------|-------| | Concurrent queries per warehouse | 8 (XS) to 64+ (4XL) | Depends on warehouse size | | Queued queries per warehouse | Unlimited (queued, not rejected) | But users experience latency | | SQL API requests | 10 concurrent per user | Via REST `/api/v2/statements` | | Snowpipe file notifications | 10,000/sec per pipe | Per-pipe limit | | Login rate | Throttled per account | Avoid rapid connect/disconnect | | COPY INTO files per command | 1,000 files recommended | Performance degrades beyond | ## Instructions ### Step 1: Detect Queuing Issues ```sql -- Check warehouse load — avg_queued_load > 0 means queries are waiting SELECT warehouse_name, start_time, avg_running, avg_queued_load, avg_blocked FROM TABLE(INFORMATION_SCHEMA.WAREHOUSE_LOAD_HISTORY( DATE_RANGE_START => DATEADD(hours, -4, CURRENT_TIMESTAMP()) )) WHERE avg_queued_load > 0 ORDER BY start_time DESC; -- Find queries that waited in queue SELECT

What's inside
Steps it walks through
  1. Overview
  2. Key Limits
  3. Instructions
  4. Step 1: Detect Queuing Issues
  5. Step 2: Right-Size Your Warehouse
  6. Step 3: Multi-Cluster Warehouse for High Concurrency
  7. Step 4: Application-Level Concurrency Control
  8. Step 5: SQL API Rate Limiting
  9. Error Handling
  10. Resources
  11. Next Steps
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the snowflake-rate-limits skill do?

Handle Snowflake concurrency limits, warehouse queuing, and query throttling. Use when queries are queuing, hitting concurrency limits, or needing to optimize warehouse sizing for throughput. Trigger with phrases like "snowflake rate limit", "snowflake throttling", "snowflake queuing", "snowflake concurrency", "snowflake warehouse sizing". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill snowflake-rate-limits --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going