Skills azure-cosmos-java
📦
azure-cosmos-java
Content revision r2 Safe ⚙️ External commands🌐 Network access🔑 Env variables
Build Azure Cosmos DB Apps with Java
Azure Cosmos DB integrations require careful client, partition, query, and throughput choices. This skill provides focused Java SDK patterns for synchronous and reactive workflows.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "azure-cosmos-java" from https://skillstore.io/skills/sickn33-azure-cosmos-java.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-cosmos-java/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "azure-cosmos-java". Set up a synchronous client for a development service.
Expected outcome:
- Dependency guidance using the Azure SDK bill of materials.
- A client setup outline using endpoint and key environment variables.
- A reminder to reuse one client throughout the application.
Using "azure-cosmos-java". Design CRUD operations for customer records partitioned by tenant.
Expected outcome:
- A container plan using the tenant identifier as the partition path.
- Create, read, replace, and delete steps that include the tenant partition value.
- Conflict and throttling cases to handle during testing.
Using "azure-cosmos-java". Review a slow reactive Cosmos DB service.
Expected outcome:
- Check whether the asynchronous client is reused instead of created per request.
- Inspect partition distribution, request-unit charges, preferred regions, and connection mode.
- Measure throttling and retry behavior before changing provisioned throughput.
Security Audit
Safev6 • 7/23/2026 Open versioned report
All 40 static findings are false positives caused by Markdown formatting, SDK configuration examples, or documentation links. No executable scripts, credential files, obfuscated payloads, prompt injection, or malicious network behavior were found.
1
Files scanned
267
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (26)
SKILL.md:15-21 SKILL.md:21-25 SKILL.md:25-44 SKILL.md:44-48 SKILL.md:48-51 SKILL.md:51-57 SKILL.md:57-65 SKILL.md:65-69 SKILL.md:69-76 SKILL.md:76-80 SKILL.md:80-94 SKILL.md:94-100 SKILL.md:100 SKILL.md:101 SKILL.md:102 SKILL.md:108-117 SKILL.md:117-121 SKILL.md:121-131 SKILL.md:131-135 SKILL.md:135-169 SKILL.md:169-173 SKILL.md:173-189 SKILL.md:189-214 SKILL.md:214-217 SKILL.md:217-231 SKILL.md:231-247
🌐 Network access (7)
🔑 Env variables (2)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-azure-cosmos-java/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-azure-cosmos-java?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-azure-cosmos-java?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-cosmos-java/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-azure-cosmos-java.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). azure-cosmos-java security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-cosmos-java/audits/6BibTeX citation
@techreport{sickn33-sickn33-azure-cosmos-java-2026,
author = {sickn33},
title = {azure-cosmos-java security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/sickn33-azure-cosmos-java/audits/6},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "azure-cosmos-java security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-azure-cosmos-java/audits/6"
identifiers:
- type: other
value: "skillstore:sickn33-azure-cosmos-java:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
68
Community
83
Spec Compliance
What You Can Build
Create a Java data service
Design client setup, container access, CRUD operations, and queries for a Java backend.
Plan a scalable data model
Compare partition, consistency, region, and connection choices before implementing a Cosmos DB workload.
Diagnose throughput behavior
Review request charges, client reuse, direct mode, and rate-limit handling for an existing service.
Try These Prompts
Set up a basic client
Show the Maven dependency and a minimal synchronous Cosmos DB Java client using named environment variables.
Build a CRUD workflow
Design Java CRUD operations for [entity] using database [database], container [container], and partition key [path].
Create a reactive pipeline
Create an asynchronous workflow that initializes resources, processes [operation], handles conflicts and throttling, and reports request charges.
Review production architecture
Review my Cosmos DB Java design for client reuse, partitioning, consistency, regions, direct mode, request units, and failure handling.
Best Practices
- Reuse a single Cosmos client and select the asynchronous client for high-throughput workloads.
- Choose a high-cardinality partition key that distributes storage and request traffic evenly.
- Measure request-unit charges and test throttling, retries, consistency, and regional behavior.
Avoid
- Do not create a new Cosmos client for every request or operation.
- Do not select a low-cardinality partition key without workload measurements.
- Do not place account keys in source code, logs, prompts, or generated examples.
Frequently Asked Questions
Which Cosmos DB API does this skill cover?
It covers the Azure Cosmos DB NoSQL API through the Java SDK.
Does it support synchronous and asynchronous clients?
Yes. It explains both client types and includes reactive operation patterns.
Can it choose a partition key for my application?
It can assess candidates, but the final choice requires real data distribution and query measurements.
Does it provision Azure Cosmos DB resources?
No. It provides SDK guidance for applications and does not run infrastructure provisioning.
Does it support managed identity authentication?
The source material covers account-key authentication only. Managed identity requires additional Azure Identity guidance.
Can it guarantee production performance?
No. Production performance requires workload testing, request-unit analysis, partition validation, and regional measurements.