From azure-cosmosdb
Guides Cosmos DB document schema design: embedding vs referencing, 2MB item limit, nesting depth, schema versioning, type discriminators, JSON serialization, denormalization, and relationship references.
How this skill is triggered — by the user, by Claude, or both
Slash command
/azure-cosmosdb:cosmosdb-data-modelingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Best practices for designing document schemas in Azure Cosmos DB, prioritized by impact.
AGENTS.mdREADME.mdmetadata.jsonrules/_sections.mdrules/model-avoid-2mb-limit.mdrules/model-denormalize-reads.mdrules/model-embed-related.mdrules/model-id-constraints.mdrules/model-json-serialization.mdrules/model-nesting-depth.mdrules/model-numeric-precision.mdrules/model-reference-large.mdrules/model-relationship-references.mdrules/model-schema-versioning.mdrules/model-type-discriminator.mdBest practices for designing document schemas in Azure Cosmos DB, prioritized by impact.
Reference these guidelines when:
For all rules expanded: AGENTS.md
npx claudepluginhub azurecosmosdb/cosmosdb-agent-kit --plugin azure-cosmosdbProvides Azure Cosmos DB partition key design best practices: high cardinality, hotspot avoidance, hierarchical/synthetic keys, query alignment, and logical partition size limits.
Guides Azure Cosmos DB application development including NoSQL data modeling, partition key design, point reads, query optimization, SDK usage, transactional batches, change feed, and consistency-aware reads.
Designs NoSQL data models for MongoDB, DynamoDB, Redis, and Cassandra using access patterns, embedding/referencing decisions, and denormalization trade-offs.