azure-cosmos-db

Generate Azure Cosmos DB Bicep and Terraform configurations with partitioning and consistency tuning.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/sitharaj88/claude-skills --skill azure-cosmos-db-sitharaj88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-cosmos-db
Source: https://github.com/sitharaj88/claude-skills/tree/main/skills/azure-cosmos-db
Command: npx skills add https://github.com/sitharaj88/claude-skills --skill azure-cosmos-db-sitharaj88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the complex process of configuring Azure Cosmos DB, ensuring optimal performance, scalability, and cost-efficiency for your multi-model database needs.

Core Features & Use Cases

  • API Selection: Guides you to choose the right API (NoSQL, MongoDB, Cassandra, etc.) based on your use case.
  • Partition Strategy: Designs effective partition keys for high-cardinality and even data distribution.
  • Configuration Generation: Provides production-ready Bicep and Terraform configurations for accounts, databases, and containers.
  • Use Case: You need to set up a new Azure Cosmos DB for a multi-tenant SaaS application. This Skill will help you select the NoSQL API, design a /tenantId partition key, and generate the Bicep code for a globally distributed setup with appropriate indexing and autoscale throughput.

Quick Start

Use the azure-cosmos-db skill to generate a Bicep configuration for a NoSQL API Cosmos DB account named 'mycosmosdb' with a database 'mydatabase' and a container 'orders' partitioned by '/customerId'.

Frequently Asked Questions about azure-cosmos-db

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Azure Cosmos DB for optimal performance and scalability?

You can configure Azure Cosmos DB for optimal performance by generating production-ready settings for multi-model API selection, partitioning strategies, global distribution, and consistency tuning to ensure high scalability.

What is the best way to design a partition key strategy for Azure Cosmos DB?

The best way to design a Cosmos DB partition key strategy is to target high-cardinality properties for even data distribution, such as using a `/tenantId` or `/customerId` path to avoid hot partitions.

Can I generate Bicep and Terraform configurations for a globally distributed Cosmos DB setup?

Yes, you can generate production-ready Bicep and Terraform configurations for globally distributed Cosmos DB accounts, databases, and containers with appropriate indexing policies and autoscale throughput.

How do I choose the right multi-model API for my Azure Cosmos DB use case?

You choose the right Azure Cosmos DB API by evaluating your application needs against supported multi-model options like NoSQL, MongoDB, and Cassandra to align with your specific data access patterns.

Does configuring Azure Cosmos DB throughput provisioning require understanding indexing policies?

Yes, configuring Cosmos DB throughput provisioning requires a detailed understanding of features like indexing policies, autoscale configurations, and change feed mechanisms to properly optimize your database containers.

When should I not use default settings for Azure Cosmos DB container setup?

You should not use default settings for Azure Cosmos DB container setup when building multi-tenant SaaS applications, as custom partition keys, consistency tuning, and indexing policies are required for cost-efficiency.