From azure-cosmosdb
Guides throughput and scaling decisions for Azure Cosmos DB: autoscale vs provisioned, serverless, burst capacity, RU/s sizing, and container vs database allocation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/azure-cosmosdb:cosmosdb-throughputThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Best practices for provisioning and managing throughput in Azure Cosmos DB.
Best practices for provisioning and managing throughput in Azure Cosmos DB.
Reference these guidelines when:
For all rules expanded: AGENTS.md
npx claudepluginhub azurecosmosdb/cosmosdb-agent-kit --plugin azure-cosmosdbReviews Azure Cosmos DB platform posture including accounts, databases, containers, partition-key design, throughput, consistency, indexing, throttling, multi-region replication, and private connectivity.
Monitors Azure Cosmos DB performance: RU consumption, P99 latency, throttling alerts, Azure Monitor integration, and diagnostic logging.
Optimizes Azure SQL Database performance via service tier comparisons, DTU/vCore guidance, automatic tuning, Hyperscale/serverless options, and monitoring queries.