analyzing-range-distribution

A guide for examining how CockroachDB splits and distributes stored data across servers. A range is a partition of a table or index that CockroachDB replicates and places in the cluster.

In plain words
What is it for?
Finding fragmented or uneven tables and indexes, read hotspots, replication issues, and effects of placement rules on data distribution.
Why use it?
Uneven range sizes, concentrated leaders, or missing replicas can create hotspots and replication problems. The checks use SQL rather than the database web console.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/cockroachdb/cursor-plugin/analyzing-range-distribution
Any agent
npx skills add cockroachdb/cursor-plugin --skill analyzing-range-distribution
Clone the repo
git clone --depth 1 https://github.com/cockroachdb/cursor-plugin

Made for: Claude Code, Codex.

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,438 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00060 $0.03438
Opus 5 $0.00030 $0.01719
Sonnet 5 $0.00012 $0.00688
Haiku 4.5 $0.00006 $0.00344

Measured 2d ago against content hash cf58bb366258, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

analyzing-range-distribution scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to analyzing-range-distribution — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/cockroachdb-observability-and-diagnostics/analyzing-range-distribution/SKILL.md · 347 lines

How it starts

The opening of the file, as written. The whole thing — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analyzing Range Distribution

Analyzes CockroachDB range distribution, leaseholder placement, and zone configuration compliance using SHOW RANGES and SHOW ZONE CONFIGURATIONS commands. Identifies range count anomalies, size imbalances, leaseholder hotspots, and replication issues - entirely via SQL without requiring DB Console access.

Complement to profiling skills: This skill analyzes range-level data distribution; for query performance patterns, see profiling-statement-fingerprints. For schema change storage planning, see analyzing-schema-change-storage-risk.

When to Use This Skill

  • Identify tables/indexes with excessive range counts indicating fragmentation
  • Detect range size imbalances or uneven data distribution across nodes
  • Investigate leaseholder concentration causing read hotspots
  • Validate zone configuration effects on range placement and replica distribution
  • Diagnose range-level replication issues (under-replicated or unavailable ranges)
  • Analyze range split patterns from high write volume
  • SQL-only range analysis without DB Console access

For schema change planning: Use analyzing-schema-change-storage-risk to estimate storage requirements before CREATE INDEX or ADD COLUMN operations.

Prerequisites

  • SQL connection to CockroachDB cluster
  • Admin role OR ZONECONFIG system privilege
  • Understanding of CockroachDB range architecture (default 512MB max size; verify with SHOW ZONE CONFIGURATION FOR RANGE default)
  • Knowledge of cluster topology (node IDs, regions, availability zones)

Check your privileges:

SHOW SYSTEM GRANTS FOR <username>;  -- Should show admin or ZONECONFIG

See permissions reference for RBAC setup.

Core Concepts

Ranges: Units of Data Distribution

Range: Contiguous key space segment (default 512MB max size, configurable via zone config range_max_bytes) Raft group: Each range replicated across nodes (default 3 replicas) Leaseholder: Single replica handling reads and coordinating writes for a range

Read the full file on GitHub · 347 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 347 lines · 60 tokens per session scan A cf58bb366258

Subscribe to this mod's changes

analyzing-range-distribution is a skill published in the GitHub repository cockroachdb/cursor-plugin (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 3,438 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to analyzing-range-distribution, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

designing-application-transactions

Guides application developers in designing correct and performant transaction patterns for CockroachDB, covering transaction lifetime, implicit vs explicit transactions, retry handling with exponential backoff, pushing invariants into SQL, selective pessimistic locking, set-based operations, connection pooling…

cockroachdb/claude-plugin · 102 tokens

profiling-transaction-fingerprints

Analyzes transaction fingerprints using aggregated statistics from crdbinternal.transactionstatistics to identify high-retry transactions, contention patterns, and commit latency issues. Provides historical transaction-level analysis to understand which statement combinations are causing retries, contention, or…

cockroachdb/claude-plugin · 80 tokens

auditing-cloud-cluster-security

Audits the security posture of a CockroachDB cluster (Cloud or self-hosted) across network, authentication, authorization, encryption, audit logging, and backup dimensions. Use when assessing cluster security readiness, preparing for compliance reviews, or investigating security configuration gaps.

cockroachdb/claude-plugin · 59 tokens

configuring-sso-and-scim

Configures SSO authentication and SCIM 2.0 provisioning for CockroachDB across four distinct layers — Cloud Console SSO (SAML/OIDC), DB Console SSO (OIDC), SQL/Cluster SSO (JWT or LDAP/AD), and SCIM 2.0 automated provisioning. Use when enabling centralized identity management, setting up SSO for compliance, or…

cockroachdb/claude-plugin · 91 tokens

analyzing-range-distribution

Analyzes CockroachDB range distribution across tables and indexes using SHOW RANGES to identify range count, size patterns, leaseholder placement, and replication health. Use when investigating hotspots, uneven data distribution, range fragmentation, or validating zone configuration effects without DB Console access.

cockroachdb/claude-plugin · 60 tokens

auditing-table-statistics

Audits optimizer table statistics for staleness, missing coverage, and data quality issues using SHOW STATISTICS. Use when diagnosing poor query performance, unexpected plan changes, or after bulk data changes to identify stale statistics requiring refresh via CREATE STATISTICS.

cockroachdb/claude-plugin · 55 tokens