Stats
Actions
Tags
From azure-cosmosdb
Provides Azure Cosmos DB partition key design best practices: high cardinality, hotspot avoidance, hierarchical/synthetic keys, query alignment, and logical partition size limits.
How this skill is triggered — by the user, by Claude, or both
Slash command
/azure-cosmosdb:cosmosdb-partition-keyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Best practices for choosing and designing partition keys in Azure Cosmos DB.
AGENTS.mdREADME.mdmetadata.jsonrules/_sections.mdrules/partition-20gb-limit.mdrules/partition-avoid-hotspots.mdrules/partition-hierarchical.mdrules/partition-high-cardinality.mdrules/partition-immutable-key.mdrules/partition-key-length.mdrules/partition-query-patterns.mdrules/partition-synthetic-keys.mdBest practices for choosing and designing partition keys in Azure Cosmos DB.
Reference these guidelines when:
For all rules expanded: AGENTS.md
npx claudepluginhub azurecosmosdb/cosmosdb-agent-kit --plugin azure-cosmosdbAzure Cosmos DB performance optimization and best practices for NoSQL, including partitioning, query optimization, SDK usage, and data modeling.
Guides Azure Cosmos DB application development including NoSQL data modeling, partition key design, point reads, query optimization, SDK usage, transactional batches, change feed, and consistency-aware reads.
Expert guidance on distributed NoSQL databases (Cassandra, DynamoDB), emphasizing query-first modeling, single-table design, partition key strategy, and avoiding hot partitions.