azure-cosmosdb-platform-operator

Azure Cosmos DB Platform Operator

Purpose

Review and guide Azure Cosmos DB platform posture without hand-wavy assumptions about partitioning, consistency, throughput, or multi-region behavior.

When to use

Use this skill when the user asks for:

• Azure Cosmos DB account, database, or container operational review,
• partition-key, consistency, throughput, or indexing decisions,
• RU cost, throttling, hot partition, or multi-region tradeoff analysis,
• private endpoint, failover, or platform control-plane posture questions,
• Cosmos DB documentation-grounded discovery or sampled read-only evidence gathering.

Do not use this skill as a substitute for:

• application code implementation details unless they directly affect platform posture,
• generic landing-zone or network architecture when Cosmos DB is incidental,
• RBAC-only analysis when the real problem is identity governance rather than database platform design,
• vector-search-specific Mongo vCore 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, credential boundaries, and current-state caveats.
• 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.