cosmosdb

Azure Cosmos DB multi-model database with global distribution. Use for Azure.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

cosmosdb is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Azure Cosmos DB multi-model database with global distribution. Use for Azure.

Teams using cosmosdb should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/cosmosdb/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/databases/cosmosdb/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/cosmosdb/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How cosmosdb Compares

Feature / Agent	cosmosdb	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Azure Cosmos DB multi-model database with global distribution. Use for Azure.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Azure Cosmos DB

Cosmos DB is Azure's planetary-scale database. It supports multiple APIs: NoSQL (Core/JSON), MongoDB, PostgreSQL, Cassandra, Gremlin (Graph), and Table.

## When to Use

- **Global Distribution**: Replicate data to any Azure region with a click.
- **Multi-Model**: If you need Mongo or Postgres APIs but want "PaaS" management.
- **Low Latency**: Guaranteed <10ms read/write latency at the 99th percentile.

## Quick Start (NoSQL API)

```csharp
Container container = database.GetContainer("Items");

Item item = new Item
{
    Id = "1",
    Category = "Personal",
    Name = "Groceries"
};

await container.CreateItemAsync(item, new PartitionKey(item.Category));
```

## Core Concepts

### Request Units (RUs)

The currency of Cosmos DB. Use RUs to pay for throughput. 1 RU ≈ reading a 1KB doc.

### Partition Key

Crucial. Determines how data is distributed. A bad partition key ("Date") creates "Hot Partitions" (bottlenecks). A good key ("UserId") distributes load evenly.

### Consistency Levels

Offers 5 levels: Strong, Bounded Staleness, Session (Default), Consistent Prefix, Eventual. Trade off consistency for availability/latency.

## Best Practices (2025)

**Do**:

- **Use the NoSQL API**: It is the native API with the most features.
- **Use Hierarchical Partition Keys (2025)**: Supports up to 3 keys for better data distribution (TenantId -> UserId -> DeviceId).
- **Use Analytical Store (Synapse Link)**: Run heavy analytics (BI) on your operational data without impacting performance.

**Don't**:

- **Don't ignore RU consumption**: Monitor it. Queries without a partition key ("Cross-partition queries") are expensive.

## References

- [Azure Cosmos DB Documentation](https://learn.microsoft.com/en-us/azure/cosmos-db/)