Azure Cosmos DB Data Modeling Skill (awesome-copilot) for Claude Code: What It Does and How to Install It
Makes your agent interview you about your workload, then write a justified Azure Cosmos DB NoSQL data model.
- Installs
- 8.7K
- on skills.sh
- Stars
- 40.7K
- on GitHub
- Updated
- Oct 2026
- last repo commit
The agent works as a pair programmer in a long conversation. It asks one question at a time, at most three related ones, and records what it learns in cosmosdb_requirements.md after every message. When you confirm all access patterns are captured and a validation checklist is complete, it writes the final design to cosmosdb_data_model.md.
It bundles no scripts. SKILL.md carries the design rules inline: aggregate-oriented design, rules for consolidating containers, cost constants and 14 design patterns, from data binning to write sharding and TTL. It says never to invent request-per-second numbers and to work them out with you.
Good for
- Developers designing containers and partition keys for Cosmos DB for NoSQL
- Architects who need access patterns and RU costs on paper
- Teams planning high-write or global workloads
Install cosmosdb-datamodeling
Claude Code
- 1
Copy this prompt.
Install the cosmosdb-datamodeling skill in Claude Code. Run this command: npx skills add https://github.com/github/awesome-copilot --skill cosmosdb-datamodeling Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js.
The awesome-copilot README is written for GitHub Copilot and does not name Claude Code, so the Claude Code and Codex routes are the standard skill-folder routes. It is one SKILL.md file and is not part of any awesome-copilot plugin listed in the repo.
Built from the package data we hold. Not yet tested by us. Source.
What's in the skill
When it loads
Step-by-step guide for capturing key application requirements for NoSQL use-case and produce Azure Cosmos DB Data NoSQL Model design using best practices and common patterns, artifacts_produced: "cosmosdb_requirements.md" file and "cosmosdb_data_model.md" file
Sections in SKILL.md
- Role and Objectives
- Documentation Workflow
- Primary Working File: cosmosdb_requirements.md
- Application Overview
- Access Patterns Analysis
- Entity Relationships Deep Dive
- Enhanced Aggregate Analysis
- [Entity1 + Entity2] Container Item Analysis
- Identifying Relationship Check
- User + Orders Container Item Analysis
- Container Consolidation Analysis
- Consolidation Decision Framework
- Consolidation Candidates Review
- Consolidation Rules
- Design Considerations (Subject to Change)
- Validation Checklist
Key facts
- Installs on skills.sh
- 8,688 (Nov 2, 2026)
- Last repo commit
- Oct 30, 2026
- What it includes
- 1 file: SKILL.md (1,045 lines). No scripts
- Audits on skills.sh
- Gen Agent Trust Hub: pass, Socket: pass, Snyk: pass (Nov 2, 2026)
- Version in SKILL.md
- 1.0, last updated 2025-09-17
What it includes
Gathers access patterns, volumes, latency and concurrency, one question at a time
At most three related questions per turn.
Write ·
Requirements interviewWorking file updated after every message that adds information
Holds access patterns, entity relationships, aggregate analysis and design ideas.
Write ·
cosmosdb_requirements.mdDecides which related entities share a container, using access overlap rules
Consolidate above 50% overlap; keep separate below 30%.
Container consolidation analysisA decision framework for entities with 30 to 70% access correlation
Multi-document vs separate containersTen checks before the final model, such as RPS, latency and hot partitions
Validation checklistFinal deliverable with containers, indexes, access pattern mapping and trade-offs
Created only after you confirm all patterns are captured.
Write ·
cosmosdb_data_model.mdWorks in RUs from realistic document sizes, with cross-partition overhead and monthly cost
Uses constants in SKILL.md; check current Azure pricing.
Cost calculation rulesAbove 10k writes per second, asks about binning, write reduction and partitions
Massive scale warning14 patterns, including binning, sparse indexes, hierarchical partition keys and TTL
Applied only after the core design, not as defaults.
Design patterns
From the official docs
Questions
What does cosmosdb-datamodeling do?
It makes your agent guide you through Cosmos DB NoSQL data modeling. It captures your access patterns and volumes, then produces a data model with container designs, indexing, partition keys and cost estimates.
How do I install it?
Use the install box at the top of this page. It is one SKILL.md file, so there is nothing else to set up.
Which files does it create?
cosmosdb_requirements.md as a working notebook, and cosmosdb_data_model.md as the final design. The second is only created after you confirm the access patterns are complete.
Does it need an Azure account or key?
SKILL.md names no account or tool. It is a conversation that writes two Markdown files from the answers you give.
Can I trust its cost numbers?
SKILL.md bakes in Cosmos DB constants such as $0.25 per GB-month storage and $0.008 per RU per hour, dated 2025-09-17 in the file. Our advice: check them against current Azure pricing before you rely on them.
Does it cover global distribution and hot partitions?
Yes. The final model template has a global distribution section and a hot partition analysis, and the validation results list both as checks.
Is it safe?
It bundles no scripts and writes two Markdown files in your working folder. It works from what you tell it, so the main risk is acting on an unreviewed design. Review the model before you build on it.
Information
updated Nov 2, 2026
- Repository
- github/awesome-copilot
- Folder
skills/cosmosdb-datamodeling
Sources
Docs, issue trackers and discussions this page is built from.
Show all 2Hide
- awesome-copilot README · github.com
- cosmosdb-datamodeling SKILL.md · github.com