clustering

DE//AGENT currently lists 3 resources under clustering: 2 tutorials, 1 skill. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Documented learning objectives across these resources:

• Separate scan inefficiency from compute inefficiency — via Warehouse Clustering Advisor
• Choose a clustering key from predicate selectivity — via Warehouse Clustering Advisor
• Right-size a virtual warehouse from queue time — via Warehouse Clustering Advisor
• Name the three numbers that describe a warehouse query — bytes scanned, partitions scanned ratio, queue time — via The warehouse mental model — micro-partitions, clustering, scan vs compute
• Explain why a table is a set of micro-partitions and what a clustering key prunes — via The warehouse mental model — micro-partitions, clustering, scan vs compute
• Separate a scan problem from a compute problem before touching any knob — via The warehouse mental model — micro-partitions, clustering, scan vs compute
• Prove pruning with partitions_scanned versus partitions_total — via Make queries prune — clustering keys and scan diagnosis
• Fix the scan or compute problem you actually measured — via Make queries prune — clustering keys and scan diagnosis

These resources map to stage: Warehousing (3). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. Warehouse Clustering Advisor score 36.5 — advanced
2. The warehouse mental model — micro-partitions, clustering, scan vs compute score 34.15 — beginner
3. Make queries prune — clustering keys and scan diagnosis score 34.15 — intermediate

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Start here if you're new: The warehouse mental model — micro-partitions, clustering, scan vs compute.

Reach for these with production experience: Warehouse Clustering Advisor.

Security-flagged entries: Warehouse Clustering Advisor (2 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• Warehouse Clustering Advisor — Advises on Snowflake/BigQuery/Redshift tuning: clustering keys, warehouse sizing, result caching, and the difference between a scan problem and a compute problem. details
• The warehouse mental model — micro-partitions, clustering, scan vs compute — Build the map before tuning anything: a table is a set of micro-partitions, every query is described by bytes scanned, partitions scanned ratio, and queue time, a clustering key de… details
• Make queries prune — clustering keys and scan diagnosis — Choose a clustering key from the predicates of your most expensive queries, prove the prune with partitions_scanned versus partitions_total, and fix the disease you actually have —… details

Real install commands from the registry — read the source before running any of them:

npx de-agent-platform add warehouse-clustering-advisor

Warehouse Clustering Advisor — review first

Adjacent topics: tutorial (2 shared), performance (2 shared), warehousing (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.