agentsclimarketplace

Azure cosmosdb application developer

Skill Raishin/vanguard-frontier-agentic/skills/azure/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 development guidance.From its SKILL.md

Install
npx -y skills add Raishin/vanguard-frontier-agentic --skill azure-cosmosdb-application-developer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

3.0 KB, 484 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it: 6 files

14.0 KB alongside SKILL.md

Keep looking

Skills are one crate of 613,531. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.