Skip to content
Agentmart
Submit a tool

documentdb-cluster-sharding

Cluster sizing and sharding guidance for Azure DocumentDB — choosing M-tier (M10–M200+), when to scale vertically vs horizontally, and how to pick a shard key…

Skill by khelanmodi

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/khelanmodi-documentdb-cluster-sharding

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

Cluster sizing and sharding guidance for Azure DocumentDB — choosing M-tier (M10–M200+), when to scale vertically vs horizontally, and how to pick a shard key once the database surpasses terabyte scale. Use when sizing a new cluster, diagnosing capacity issues, deciding whether to shard, or designing a shard key.

Use cases: backend, cloud

Reviews

Write a review

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/documentdb-cluster-sharding

What's inside

Skill name
documentdb-cluster-sharding
Description
Cluster sizing and sharding guidance for Azure DocumentDB — choosing M-tier (M10–M200+), when to scale vertically vs horizontally, and how to pick a shard key once the database surpasses terabyte scale. Use when sizing a new cluster, diagnosing capacity issues, deciding whether to shard, or designing a shard key.
License
MIT
Instructions
11 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • name: "documentdb-cluster-sharding" does not match folder "cluster-sharding"

Files (4)

  • SKILL.md
  • cluster-scale-before-shard.md
  • cluster-shard-key-query-aligned.md
  • cluster-tier-selection.md

SKILL.md (first lines)

# Cluster Design & Sharding — Azure DocumentDB

In Azure DocumentDB, a shard key is **not required** until the database surpasses terabytes. Most scaling decisions are about picking the right M-tier first.

## Rules

- [cluster-tier-selection](cluster-tier-selection.md) — Pick an M-tier (M10–M200+) based on working-set memory, vCPU, and vector-index size.
- [cluster-scale-before-shard](cluster-scale-before-shard.md) — Scale vertically first; DocumentDB doesn't require a shard key until TB scale.
- [cluster-shard-key-query-aligned](cluster-shard-key-query-aligned.md) — When you do shard at TB scale, pick a high-cardinality, query-aligned, immutable shard key.

From khelanmodi/documentdb-agent-kit, MIT.

More from khelanmodi/documentdb-agent-kit

Signals

Stars
0
Forks
1
Open issues
2
Last commit (this folder)
Apr 24, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/khelanmodi/documentdb-agent-kit
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from khelanmodi

Cite this page

documentdb-cluster-sharding skill. Agent Mart. https://agentmart.dev/skills/khelanmodi-documentdb-cluster-sharding (last updated 2026-10-24)