Azure Cosmosdb

This one covers the essentials of working with Azure Cosmos DB's NoSQL API: partition key design, CRUD patterns with the TypeScript SDK, and consistency tradeoffs. The partition key guidance is solid, showing good patterns like userId or tenantId and warning against low cardinality or timestamp keys that create hot partitions. Includes practical code for point reads, cross-partition queries, pagination, and patch operations. If you're building on Cosmos DB and need to avoid the common mistakes around data distribution and query efficiency, this captures the patterns that actually matter in production. Focuses on the Core API, so if you're using MongoDB or Cassandra wire protocols, you'll need different resources.

skills.sh installs: 170
GitHub stars: 685
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add alinaqi/claude-bootstrap --skill azure-cosmosdb --agent claude-code

Installs into .claude/skills of the current project.

Files

Core Principle

Choose partition key wisely, design for your access patterns, understand consistency tradeoffs.

Cosmos DB distributes data across partitions. Your partition key choice determines scalability, performance, and cost. Design for even distribution and query efficiency.

Cosmos DB APIs

API	Use Case
NoSQL (Core)	Document database, most flexible
MongoDB	MongoDB wire protocol compatible
PostgreSQL	Distributed PostgreSQL (Citus)
Apache Cassandra	Wide-column store
Apache Gremlin	Graph database
Table	Key-value (Azure Table Storage compatible)

This skill focuses on NoSQL (Core) API - the most common choice.

Key Concepts

Concept	Description
Container	Collection of items (like a table)
Item	Single document/record (JSON)
Partition Key	Determines data distribution
Logical Partition	Items with same partition key
Physical Partition	Storage unit (max 50GB, 10K RU/s)
RU (Request Unit)	Throughput currency