Skip to content
Agentmart
Submit a tool

snow-perf

Use when a Snowflake query is slow or expensive, a warehouse costs too much, or you are tuning tables, clustering or warehouse sizing.

Skill by Srimukh99

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/srimukh99-snow-perf

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when a Snowflake query is slow or expensive, a warehouse costs too much, or you are tuning tables, clustering or warehouse sizing.

Use cases: data

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/snow-perf

What's inside

Skill name
snow-perf
Description
Use when a Snowflake query is slow or expensive, a warehouse costs too much, or you are tuning tables, clustering or warehouse sizing.
License
MIT
Instructions
32 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# snow-perf

## 1. Find what costs most

Query `SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY` (and `WAREHOUSE_METERING_HISTORY` for credits) to rank queries and warehouses by time and cost.

## 2. Read the Query Profile

| You see | Meaning | Try |
| --- | --- | --- |
| Partitions scanned close to total | Poor pruning | Filter on columns the data is naturally ordered by; consider a clustering key on large tables |
| Bytes spilled to local or remote storage | Not enough memory | Reduce data early (filter, project); size the warehouse up for this workload |
| Join output far larger than inputs | Exploding join | Fix join keys or duplicates |
| Most time in one operator | That's the bottleneck | Rewrite that step first |

## 3. Fix options

- Select only needed columns; filter as early as possible.
- Clustering keys only on large tables with measured pruning problems; reclustering costs credits.
- Search optimization for selective point lookups.
- Dynamic tables or materialized views for repeated heavy aggregations.
- Remember the result cache: re-running an identical query can look fast without being faster.

## 4. Warehouse hygiene

Auto-suspend at around 60 seconds, auto-resume on, right-size per workload, multi-cluster for concurrency (not single-query speed), and resource monitors with alerts.

## Prove it

Report elapsed time, bytes scanned and credits before and after (`ship`).

From Srimukh99/rubric, MIT.

More from Srimukh99/rubric

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Oct 2, 2026 (26 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Srimukh99

Cite this page

snow-perf skill. Agent Mart. https://agentmart.dev/skills/srimukh99-snow-perf (last updated 2026-10-24)