| Azure Cosmos DB performance optimization and best practices guidelines for NoSQL, partitioning, queries, and SDK usage. Use when writing, reviewing, or refactoring code that interacts with Azure Cosmos DB, designing data models, optimizing queries, or implementing high-performance database operations.
85k tokens
context cost
the whole folder, loaded on every use
80
files
instructions only
0
copies elsewhere
how many repositories repackaged it
198
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repository
Comprehensive performance optimization guide for Azure Cosmos DB applications, containing 75+ rules across 11 categories, prioritized by impact to guide automated refactoring and code generation.
When to Apply
Reference these guidelines when:
Designing data models for Cosmos DB
Choosing partition keys
Writing or optimizing queries
Implementing SDK patterns
Using the Cosmos DB Emulator for local development
Inspecting or managing Cosmos DB data with developer tooling
Implementing vector search or RAG features on Cosmos DB
pattern-change-feed-materialized-views - Use Change Feed for cross-partition query optimization
pattern-efficient-ranking - Use count-based or cached approaches for efficient ranking
pattern-service-layer-relationships - Use a service layer to hydrate document references
10. Developer Tooling (MEDIUM)
tooling-vscode-extension - Use the VS Code extension for routine inspection and management
tooling-emulator-setup - Use the Emulator for local development and testing
11. Vector Search (HIGH)
vector-enable-feature - Enable vector search on the account before using vector features
vector-embedding-policy - Define vector embedding policy for vector properties
vector-index-type - Configure vector indexes in the indexing policy
vector-normalize-embeddings - Normalize embeddings for cosine similarity
vector-distance-query - Use VectorDistance for similarity search
vector-repository-pattern - Implement a repository pattern for vector search
How to Use
Use the linked rule files above for detailed explanations and code examples. The links give the agent direct paths to the relevant guidance instead of relying on folder scanning or inferred filenames.
Each rule file contains:
Brief explanation of why it matters
Incorrect code example with explanation
Correct code example with explanation
Additional context and references
Full Compiled Document
For the complete guide with all rules expanded: AGENTS.md
How to use it
Copy the folder
Take microsoft/cosmosdb-best-practices from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
Check the name does not clash
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.