agentsclimarketplace

Techtide azure cosmosdb platform operator

Skill TechTideOhio/techtide-harness-kit/skills/azure/techtide-azure-cosmosdb-platform-operator

Use this skill for Azure Cosmos DB platform operations and design review, especially accounts, databases, containers, partition-key design, throughput and RU posture, consistency choices, indexing, throttling, multi-region replication, private connectivity, and Cosmos DB MCP-guided discovery.From its SKILL.md

Install
npx -y skills add TechTideOhio/techtide-harness-kit --skill techtide-azure-cosmosdb-platform-operator

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

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 415 tokens by cl100k_base, as published. Nobody here has run it

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 MCP-backed discovery or 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 live Azure or Microsoft evidence first when the active client exposes it; otherwise fall back to official documentation and 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:

  • MCP and evidence path - use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.
  • 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: 4 files

6.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,790. 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.