Azure Database Migration
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure Database Migration Service development including troubleshooting, decision making, limits & quotas, security, integrations & coding patterns, and deployment.
Azure Cosmos DB performance optimization and best practices guidelines for NoSQL, partitioning, queries, and SDK usage.
Install Cosmosdb Best Practices
$ npx skills add microsoft/vscode-cosmosdb --skill cosmosdb-best-practices -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft/vscode-cosmosdb cosmosdb-best-practices --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/microsoft/vscode-cosmosdb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cosmosdb-best-practices .claude/skills/cosmosdb-best-practices && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cosmosdb-best-practices" agent skill from https://github.com/microsoft/vscode-cosmosdb/tree/main/skills/cosmosdb-best-practices into .claude/skills/cosmosdb-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cosmosdb-best-practices", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/microsoft/vscode-cosmosdb/tree/main/skills/cosmosdb-best-practicesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add microsoft/vscode-cosmosdb --skill cosmosdb-best-practices -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft/vscode-cosmosdb cosmosdb-best-practices --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/vscode-cosmosdb.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cosmosdb-best-practices .agents/skills/cosmosdb-best-practices && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cosmosdb-best-practices" agent skill from https://github.com/microsoft/vscode-cosmosdb/tree/main/skills/cosmosdb-best-practices into .agents/skills/cosmosdb-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cosmosdb-best-practices", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft/vscode-cosmosdb --skill cosmosdb-best-practices -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft/vscode-cosmosdb cosmosdb-best-practices --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/vscode-cosmosdb.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cosmosdb-best-practices .cursor/skills/cosmosdb-best-practices && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cosmosdb-best-practices" agent skill from https://github.com/microsoft/vscode-cosmosdb/tree/main/skills/cosmosdb-best-practices into .cursor/skills/cosmosdb-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cosmosdb-best-practices", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/microsoft/vscode-cosmosdb.git --path skills/cosmosdb-best-practices--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add microsoft/vscode-cosmosdb --skill cosmosdb-best-practices -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft/vscode-cosmosdb cosmosdb-best-practices --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/vscode-cosmosdb.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cosmosdb-best-practices .gemini/skills/cosmosdb-best-practices && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cosmosdb-best-practices" agent skill from https://github.com/microsoft/vscode-cosmosdb/tree/main/skills/cosmosdb-best-practices into .gemini/skills/cosmosdb-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cosmosdb-best-practices", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install microsoft/vscode-cosmosdb cosmosdb-best-practicesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add microsoft/vscode-cosmosdb --skill cosmosdb-best-practices -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft/vscode-cosmosdb.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cosmosdb-best-practices .github/skills/cosmosdb-best-practices && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cosmosdb-best-practices" agent skill from https://github.com/microsoft/vscode-cosmosdb/tree/main/skills/cosmosdb-best-practices into .github/skills/cosmosdb-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cosmosdb-best-practices", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft/vscode-cosmosdb --skill cosmosdb-best-practices -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft/vscode-cosmosdb cosmosdb-best-practices --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft/vscode-cosmosdb.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cosmosdb-best-practices .opencode/skills/cosmosdb-best-practices && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cosmosdb-best-practices" agent skill from https://github.com/microsoft/vscode-cosmosdb/tree/main/skills/cosmosdb-best-practices into .opencode/skills/cosmosdb-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cosmosdb-best-practices", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cosmosdb-best-practices- GitHub stars
- 200
- Token cost
- ~4.3k tokens
- SKILL.md length
- 1,194 words
- Files
- 137
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Azure Cosmos DB performance optimization and best practices guidelines for NoSQL, partitioning, queries, and SDK usage.
- Works in 12 steps: Data Modeling (CRITICAL) → Partition Key Design (CRITICAL) → Query Optimization (HIGH) → …
- Refactoring code that interacts with Azure Cosmos DB
- SKILL.md covers When to Apply, Rule Categories by Priority, Quick Reference and How to Use
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Cosmosdb Best Practices is an agent skill from microsoft/vscode-cosmosdb, published by the product's own GitHub organization. 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. USE FOR: Cosmos DB NoSQL, partition key design, RU optimization, point reads, cross-partition queries, SDK singleton, CosmosClient, container modeling, change feed, bulk operations, vector search, full-text search…
Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 137 other files (for example `rules/fts-add-index.md`, `rules/fts-define-policy.md` and `rules/fts-enable-capability.md`).
It sits in Databases, covering NoSQL databases and Search implementation. It works with Azure Cosmos DB, Microsoft Azure, Microsoft SQL Server and MongoDB. The repository describes itself as: Azure Cosmos DB extension for VS Code. The licence is MIT.
When your agent uses it
- Refactoring code that interacts with Azure Cosmos DB
- Designing data models
- Optimizing queries
- Implementing high-performance database operations
Example prompts
- “/cosmosdb-best-practices”
Requirements
- Python 3
Workflow steps
12 steps, taken from the step headings in SKILL.md.
- Data Modeling (CRITICAL)
- Partition Key Design (CRITICAL)
- Query Optimization (HIGH)
- SDK Best Practices (HIGH)
- Indexing Strategies (MEDIUM-HIGH)
- Throughput & Scaling (MEDIUM)
- Global Distribution (MEDIUM)
- Monitoring & Diagnostics (LOW-MEDIUM)
- Design Patterns (HIGH)
- Developer Tooling (MEDIUM)
- Vector Search (HIGH)
- Full-Text Search (HIGH)
What it can do on your machine
Read from SKILL.md and the folder at commit cf3dbf8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Cosmosdb Best Practices loads about 4.3k tokens when it runs. Until then it costs about 211 tokens; SKILL.md has 1,194 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from microsoft/vscode-cosmosdb at commit cf3dbf8, republished under its MIT licence (© microsoft). 1,194 words, ~4,252 tokens.
Download SKILL.mdSave it as
.claude/skills/cosmosdb-best-practices/SKILL.md (or your agent's skills folder). This skill also uses 136 other files; get the full folder from GitHub.- name
- cosmosdb-best-practices
- description
- 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. USE FOR: Cosmos DB NoSQL, partition key design, RU optimization, point reads, cross-partition queries, SDK singleton, CosmosClient, container modeling, change feed, bulk operations, vector search, full-text search, hierarchical partition keys, global distribution, autoscale throughput, indexing policy. DO NOT USE FOR: PostgreSQL, MySQL, MongoDB (non-Azure), DynamoDB, Cassandra, Azure SQL, Cosmos DB for PostgreSQL (vCore), Cosmos DB for MongoDB vCore, Azure DocumentDB, general SQL databases, Redis, Elasticsearch.
- license
- MIT
- metadata.author
- cosmosdb-agent-kit
- metadata.version
- 1.0.0
Azure Cosmos DB Best Practices
Comprehensive performance optimization guide for Azure Cosmos DB applications, containing 100+ rules across 12 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
- Reviewing code for performance issues
- Configuring throughput and scaling
- Building globally distributed applications
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Data Modeling | CRITICAL | model- |
| 2 | Partition Key Design | CRITICAL | partition- |
| 3 | Query Optimization | HIGH | query- |
| 4 | SDK Best Practices | HIGH | sdk- |
| 5 | Indexing Strategies | MEDIUM-HIGH | index- |
| 6 | Throughput & Scaling | MEDIUM | throughput- |
| 7 | Global Distribution | MEDIUM | global- |
| 8 | Monitoring & Diagnostics | LOW-MEDIUM | monitoring- |
| 9 | Design Patterns | HIGH | pattern- |
| 10 | Developer Tooling | MEDIUM | tooling- |
| 11 | Vector Search | HIGH | vector- |
Quick Reference
1. Data Modeling (CRITICAL)
- model-embed-related - Embed related data retrieved together
- model-reference-large - Reference data when items get too large
- model-avoid-2mb-limit - Keep items well under 2MB limit
- model-id-constraints - Follow ID value length and character constraints
- model-nesting-depth - Stay within 128-level nesting depth limit
- model-numeric-precision - Understand IEEE 754 numeric precision limits
- model-denormalize-reads - Denormalize for read-heavy workloads including pre-computed aggregates
- model-schema-versioning - Version your document schemas
- model-type-discriminator - Use type discriminators for polymorphic data
- model-json-serialization - Handle JSON serialization correctly for Cosmos DB documents
- model-relationship-references - Use ID references with transient hydration for document relationships
2. Partition Key Design (CRITICAL)
- partition-high-cardinality - Choose high-cardinality partition keys
- partition-avoid-hotspots - Distribute writes evenly
- partition-hierarchical - Use hierarchical partition keys for flexibility; order levels broad→narrow
- partition-query-patterns - Align partition key with query patterns
- partition-synthetic-keys - Create synthetic keys when needed
- partition-key-length - Respect partition key value length limits
- partition-immutable-key - Choose immutable properties as partition keys
- partition-20gb-limit - Plan for 20GB logical partition limit
- partition-rekey-migration - Re-key a misaligned container with the Change partition key feature
3. Query Optimization (HIGH)
- query-aggregate-single-pass - Compute min/max/avg with one scoped aggregate query
- query-avoid-cross-partition - Minimize cross-partition queries
- query-use-projections - Project only needed fields; prefer dedicated result types for projections
- query-pagination - Use continuation tokens for pagination
- query-avoid-scans - Avoid full container scans
- query-parameterize - Use parameterized queries
- query-order-filters - Order filters by selectivity
- query-top-literal - Use literal integers for TOP, never parameters
- query-latest-by-timestamp - Query "latest" documents with explicit ORDER BY and TOP 1
- query-olap-detection - Detect and redirect analytical queries away from transactional containers
- query-point-reads - Use point reads (ReadItem) instead of queries when id and partition key are known
4. SDK Best Practices (HIGH)
- sdk-singleton-client - Reuse CosmosClient as singleton
- sdk-async-api - Use async APIs for throughput
- sdk-retry-429 - Handle 429s with retry-after
- sdk-connection-mode - Use Direct mode for production
- sdk-preferred-regions - Configure preferred regions
- sdk-excluded-regions - Exclude regions experiencing issues
- sdk-availability-strategy - Configure availability strategy for resilience
- sdk-circuit-breaker - Use circuit breaker for fault tolerance
- sdk-diagnostics - Log diagnostics for troubleshooting
- sdk-serialization-enums - Serialize enums as strings not integers
- sdk-emulator-ssl - Configure SSL and connection mode for Cosmos DB Emulator
- sdk-ifnonematch-create - Use
setIfNoneMatchETag("*")oncreateItemto reject duplicates atomically (409 on conflict) - sdk-no-shared-request-options - Never reuse a
CosmosItemRequestOptionsinstance across multiplecreateItemcalls — SDK mutates it internally, causing wrong partition key on second call - sdk-patch-incr - Use
CosmosPatchOperations.incr()for atomic counter increments — no read RU, no ETag conflict cycle - sdk-bypage-empty-token - Guard against empty-string continuation tokens before calling
byPage()— passnullfor first page, never"" - sdk-etag-concurrency - Use ETags for optimistic concurrency on read-modify-write operations
- sdk-java-content-response - Enable content response on write operations (Java)
- sdk-java-cosmos-config - Configure Cosmos DB initialization correctly in Spring Boot
- sdk-java-spring-boot-versions - Match Java version to Spring Boot requirements
- sdk-local-dev-config - Configure local development to avoid cloud conflicts
- sdk-dotnet-cosmos-package-id - Use
Microsoft.Azure.Cosmos, not the abandonedAzure.Cosmosv4-preview package - sdk-newtonsoft-dependency - Explicitly reference Newtonsoft.Json package
- sdk-python-async-deps - Include aiohttp when using Python async SDK
- sdk-spring-data-annotations - Annotate entities for Spring Data Cosmos
- sdk-spring-data-repository - Use CosmosRepository correctly and handle Iterable return types
- sdk-langchain-cosmosdb-saver - Use CosmosDBSaver for LangGraph checkpointing with async container client
- sdk-langchain-async-checkpointer - Initialize async Cosmos DB container in startup routine, not module level
- sdk-langchain-mcp-persistent-session - Maintain persistent MCP client sessions for application lifetime
- sdk-langchain-mcp-tool-content-format - Handle both string and list formats in MCP ToolMessage content
- sdk-langgraph-mcp-tool-filtering - Filter MCP tools by name prefix for per-agent assignment
- sdk-dotnet-namespace-collision - Avoid
Microsoft.Azure.Cosmosnamespace collisions with domain models (User, Database, Container, etc.) - sdk-ingestion-rate-control - Rate-control high-volume ingestion (concurrency, retry-after, throughput control)
5. Indexing Strategies (MEDIUM-HIGH)
- index-exclude-unused - Exclude paths never queried
- index-path-syntax - Use correct path notation (
/?,/[],/*) - index-composite - Use composite indexes for ORDER BY
- index-composite-direction - Match composite index directions to ORDER BY
- index-spatial - Add spatial indexes for geo queries
- index-range-vs-hash - Choose appropriate index types
- index-lazy-consistent - Understand indexing modes
Show full SKILL.md (459 more words)Show less
6. Throughput & Scaling (MEDIUM)
- throughput-autoscale - Use autoscale for variable workloads
- throughput-right-size - Right-size provisioned throughput
- throughput-serverless - Consider serverless for dev/test
- throughput-burst - Understand burst capacity
- throughput-container-vs-database - Choose allocation level wisely
- throughput-idle-container-review - Review idle containers for lifecycle action
- throughput-ttl-stale-data - Expire stale data with TTL before hitting storage limits
- throughput-serverless-migration - Migrate a low-traffic provisioned account to serverless
7. Global Distribution (MEDIUM)
- global-multi-region - Configure multi-region writes
- global-consistency - Choose appropriate consistency level
- global-conflict-resolution - Implement conflict resolution
- global-failover - Configure automatic failover
- global-read-regions - Add read regions near users
- global-zone-redundancy - Enable zone redundancy for HA
- global-multi-region-write-antipattern - Avoid multi-region writes without an active-active need
8. Monitoring & Diagnostics (LOW-MEDIUM)
- monitoring-ru-consumption - Track RU consumption
- monitoring-latency - Monitor P99 latency
- monitoring-throttling - Alert on throttling
- monitoring-azure-monitor - Integrate Azure Monitor
- monitoring-diagnostic-logs - Enable diagnostic logging
9. Design Patterns (HIGH)
- 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
- pattern-langgraph-multi-agent - Use StateGraph with conditional edges for multi-agent routing
- pattern-langgraph-interrupt-human - Use LangGraph interrupt for human-in-the-loop confirmation flows
- pattern-langgraph-resume-checkpoint - Resume LangGraph from checkpoint after interrupt for multi-turn conversations
- pattern-langgraph-agent-routing-cosmosdb - Persist active agent in Cosmos DB for deterministic routing via point reads
- pattern-langgraph-fastapi-startup - Initialize LangGraph agents in FastAPI startup with retry logic
- pattern-langgraph-chat-history-separate - Store chat history in a dedicated container, not the checkpointer
- pattern-background-task-writes - Use FastAPI background tasks for non-blocking chat history writes
- pattern-langgraph-async-cosmos-routing - Wrap Cosmos DB sync calls in asyncio.to_thread for LangGraph routing functions
- pattern-langgraph-async-cosmos-writes - Use asyncio.to_thread for active agent writes in async node functions
- pattern-langgraph-agent-name-attribution - Tag AI messages with agent name for API response attribution
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
12. Full-Text Search (HIGH)
- fts-enable-capability - Enable
EnableNoSQLFullTextSearchcapability on the account — prerequisite for all FTS functions - fts-full-text-policy - Define
fullTextPolicyon the container with correct language code (en-US, case-sensitive) - fts-index-policy - Add
fullTextIndexesentry in the indexing policy to build the inverted index - fts-contains-query - Use
FullTextContains/FullTextContainsAll/FullTextContainsAnyinstead ofCONTAINS(LOWER(...)) - fts-score-ranking - Use
ORDER BY RANK FullTextScore(path, term)for BM25 relevance ranking - fts-hybrid-query - Combine FTS predicates with range/equality filters; put most selective filter first
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
© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 136 other files in skills/cosmosdb-best-practices of microsoft/vscode-cosmosdb.
- SKILL.md
- rules/fts-add-index.md
- rules/fts-define-policy.md
- rules/fts-enable-capability.md
- rules/fts-hybrid-queries.md
- rules/fts-keyword-matching.md
- rules/fts-relevance-ranking.md
- rules/global-conflict-resolution.md
- rules/global-consistency.md
- rules/global-failover.md
- rules/global-multi-region-write-antipattern.md
- rules/global-multi-region.md
- rules/global-read-regions.md
- rules/global-zone-redundancy.md
- rules/index-composite-direction.md
- rules/index-composite.md
- rules/index-exclude-unused.md
- rules/index-lazy-consistent.md
- rules/index-path-syntax.md
- rules/index-range-vs-hash.md
- … and 117 more
Open the folder on GitHubat commit cf3dbf8
Compare with similar skills
Cosmosdb Best Practices next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cosmosdb Best Practices this skillmicrosoft/vscode-cosmosdb | 200 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Azure Database MigrationMicrosoftDocs/Agent-Skills | 777 | — | ~1.4k | Automated safety check: Pass | CC-BY-4.0 | |
| Whodbxiaoyuge886/aigc | 198 | — | ~894 | Automated safety check: Pass | MIT | |
| Azure Cosmos DB Pymicrosoft/skills | 3.1k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Svc Databases0ld13rr/pentestcode | 828 | — | ~379 | Automated safety check: Pass | MIT | |
| Azure Cosmos Pymicrosoft/skills | 3.1k | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
Whodb
xiaoyuge886/aigc
Database operations including querying, schema exploration, and data analysis.
- Official
Azure Cosmos DB Py
microsoft/skills
Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns.
Svc Database
s0ld13rr/pentestcode
Database RCE paths — UDF, xpcmdshell, COPY TO PROGRAM, Redis key write.
- Official
Azure Cosmos Py
microsoft/skills
Azure Cosmos DB SDK for Python (NoSQL API). An agent skill from microsoft/skills.
- Official
Azure Data Tables Py
microsoft/skills
Azure Tables SDK for Python (Storage and Cosmos DB). An agent skill from microsoft/skills.
More from microsoft/vscode-cosmosdb
- Official
Accessibility Aria Expert
microsoft/vscode-cosmosdb
Detects and fixes accessibility issues in React/Fluent UI webviews.
- Official
Telemetry Best Practices
microsoft/vscode-cosmosdb
Reviews and authors telemetry code in this extension. An agent skill from microsoft/vscode-cosmosdb.
- Official
Backport
microsoft/vscode-cosmosdb
Backport changes (current branch, a PR, a branch, or specific commits/SHAs) onto a target branch (typically a release branch like rel/).
- Official
Cosmosdb Nosql Query Generation
microsoft/vscode-cosmosdb
Generate, explain, edit, and fix Azure Cosmos DB for NoSQL (SQL API) queries.
- Official
Cosmosdb Nosql Query Editor
microsoft/vscode-cosmosdb
Drive the active Azure Cosmos DB for NoSQL Query Editor in VS Code from natural language.
Related
Categories
Questions about Cosmosdb Best Practices
What does Cosmosdb Best Practices do?
Azure Cosmos DB performance optimization and best practices guidelines for NoSQL, partitioning, queries, and SDK usage. Cosmosdb Best Practices is an agent skill from microsoft/vscode-cosmosdb, published by the product's own GitHub organization. Azure Cosmos DB performance optimization and best practices guidelines for NoSQL, partitioning, queries, and SDK usage.
When should I use Cosmosdb Best Practices?
Cosmosdb Best Practices fits situations like: refactoring code that interacts with Azure Cosmos DB; designing data models; optimizing queries; implementing high-performance database operations.
How do I install Cosmosdb Best Practices in Claude Code?
Run `npx skills add microsoft/vscode-cosmosdb --skill cosmosdb-best-practices -a claude-code`. Or copy the skill folder (skills/cosmosdb-best-practices in microsoft/vscode-cosmosdb) into .claude/skills/cosmosdb-best-practices in your project. Claude Code loads it when a task matches its description.
How do I install Cosmosdb Best Practices in Codex?
Run `npx skills add microsoft/vscode-cosmosdb --skill cosmosdb-best-practices -a codex`. Or copy the skill folder (skills/cosmosdb-best-practices in microsoft/vscode-cosmosdb) into .agents/skills/cosmosdb-best-practices in your project. Codex loads it when a task matches its description.
Can I use Cosmosdb Best Practices in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/vscode-cosmosdb --skill cosmosdb-best-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cosmosdb-best-practices, .gemini/skills/cosmosdb-best-practices, .github/skills/cosmosdb-best-practices and .opencode/skills/cosmosdb-best-practices in your project.
What does Cosmosdb Best Practices need to run?
SKILL.md names no scripts, command-line tools or credentials: Cosmosdb Best Practices is instructions for the agent only. Our summary lists: Python 3.
Does Cosmosdb Best Practices access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Cosmosdb Best Practices safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Cosmosdb Best Practices use?
Cosmosdb Best Practices is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cosmosdb Best Practices use?
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Cosmosdb Best Practices?
Skills that share tags, products or a category with Cosmosdb Best Practices: Azure Database Migration (MicrosoftDocs/Agent-Skills, 777 stars), Whodb (xiaoyuge886/aigc, 198 stars), Azure Cosmos DB Py (microsoft/skills, 3.1k stars) and Svc Database (s0ld13rr/pentestcode, 828 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cosmosdb Best Practices?
microsoft (a GitHub organization, an official publisher) maintains it in microsoft/vscode-cosmosdb, which has 200 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.
Source: microsoft/vscode-cosmosdb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.