azure-cosmosdb-application-developer
Use this skill for Azure Cosmos DB application development work, especially NoSQL data modeling, document structure, partition-aware access patterns, point reads, query design, SDK usage, transactional batch scope, consistency-aware reads, change feed integration, and Cosmos DB d
Install
npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/azure/azure-cosmosdb-application-developer
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart
git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Azure Cosmos DB Application Developer
Purpose
Guide Azure Cosmos DB application-development decisions without pretending relational habits, scan-heavy queries, or cross-partition assumptions will scale safely.
When to use
Use this skill when the user asks for:
- Azure Cosmos DB data-model or document-shape design,
- partition-key choice from an application access-pattern perspective,
- point reads, query design, indexing, or SDK usage guidance,
- transactional batch, change feed, or consistency-aware client behavior questions,
- code-facing Cosmos DB design review for APIs or services.
Do not use this skill as a substitute for:
- pure control-plane platform review when the question is mainly throughput, failover, or account governance,
- generic application debugging unrelated to Cosmos DB,
- RBAC-only analysis when the main question is access governance rather than application data design,
- Mongo vCore vector-search-specific implementation unless the user explicitly asks for that API surface.
Lean operating rules
- Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when the active client exposes it, then sanitized user evidence.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad scope, vague partition keys, and RU-blind advice.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
References
Load these only when needed:
- Operations guide — use for service-specific pitfalls, design rules, verification targets, and pushback criteria.
- MCP and evidence path — use when choosing documentation-based evidence, sampled read-only Azure evidence, or sanitized user evidence.
- Safety checklist — use for evidence labels, risk gates, mutation boundaries, approval rules, and credential boundaries.
- Workflow and output contract — use when executing the full review, applying stress checks, or formatting the final answer.
- Official sources — use when you need the detailed Microsoft documentation list or source notes.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main design or operational risks,
- the safest next actions,
- the assumptions or blockers that prevent stronger conclusions.
Files (vanguard-frontier-agentic)
-
references
-
cosmosdb-application-design.md 4.2 KB
Loading… -
mcp-and-evidence.md 1.8 KB
Loading… -
official-sources.md 2.5 KB
Loading… -
safety-checklist.md 2 KB
Loading… -
workflow-and-output.md 1.7 KB
Loading…
-
-
metadata.json 1.8 KB
Loading… -
SKILL.md 3 KB
--- name: azure-cosmosdb-application-developer description: Use this skill for Azure Cosmos DB application development work, especially NoSQL data modeling, document structure, partition-aware access patterns, point reads, query design, SDK usage, transactional batch scope, consistency-aware reads, change feed integration, and Cosmos DB development guidance. allowed-tools: Read Edit Write MultiEdit Grep Glob Bash metadata: author: github: VincentChuWaiChow version: 0.1.3 updated: "2026-06-05" category: data --- # Azure Cosmos DB Application Developer ## Purpose Guide Azure Cosmos DB application-development decisions without pretending relational habits, scan-heavy queries, or cross-partition assumptions will scale safely. ## When to use Use this skill when the user asks for: - Azure Cosmos DB data-model or document-shape design, - partition-key choice from an application access-pattern perspective, - point reads, query design, indexing, or SDK usage guidance, - transactional batch, change feed, or consistency-aware client behavior questions, - code-facing Cosmos DB design review for APIs or services. Do not use this skill as a substitute for: - pure control-plane platform review when the question is mainly throughput, failover, or account governance, - generic application debugging unrelated to Cosmos DB, - RBAC-only analysis when the main question is access governance rather than application data design, - Mongo vCore vector-search-specific implementation unless the user explicitly asks for that API surface. ## Lean operating rules - Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when the active client exposes it, then sanitized user evidence. - Separate confirmed facts from inference. If state was not queried or shown, say so. - Challenge broad scope, vague partition keys, and RU-blind advice. - Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns. ## References Load these only when needed: - [Operations guide](references/cosmosdb-application-design.md) — use for service-specific pitfalls, design rules, verification targets, and pushback criteria. - [MCP and evidence path](references/mcp-and-evidence.md) — use when choosing documentation-based evidence, sampled read-only Azure evidence, or sanitized user evidence. - [Safety checklist](references/safety-checklist.md) — use for evidence labels, risk gates, mutation boundaries, approval rules, and credential boundaries. - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, applying stress checks, or formatting the final answer. - [Official sources](references/official-sources.md) — use when you need the detailed Microsoft documentation list or source notes. ## Response minimum Return, at minimum: - the scoped target and evidence level, - the main design or operational risks, - the safest next actions, - the assumptions or blockers that prevent stronger conclusions.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.