Name: azure-cosmos-java
Rating: 54.400000000000006 (1 reviews)
Author: administrakt0r

azure-cosmos-java

Azure Cosmos DB SDK for Java. NoSQL database operations with global distribution, multi-model support, and reactive patterns.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/azure-cosmos-java/SKILL.md

The canonical home for this skill is azure-cosmos-java in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is an efficient, actionable Cosmos DB Java reference with concrete code for the common CRUD and query cases. Its main weaknesses are missing validation/feedback loops around destructive operations and a few examples that depend on undefined variables or placeholder versions.

Suggestions

Add an explicit validation checkpoint to destructive flows, e.g. read an item back (or check the response status) before deleteItem, and wrap the CRUD chain in try/catch with retry guidance for 429s.

Make the "With Customizations" example self-contained by defining or stubbing serviceEndpoint, key, directConnectionConfig, and gatewayConnectionConfig, and replace `<version>LATEST</version>` / `{bom_version}` with a concrete pinned version or an instruction to pin one.

Replace the vacuous "When to Use" section with a concrete applicability statement (e.g. Cosmos DB NoSQL API work in Java, partitioning, multi-region consistency) or remove it.

Dimension	Reasoning	Score
Conciseness	The body is a lean, code-heavy reference with no over-explanation of concepts Claude already knows; minor trims remain (the redundant intro line and the empty "This skill is applicable to execute the workflow or actions described in the overview" filler).	4 / 5
Actionability	Most sections provide copy-paste-ready Java code for the common cases, but several examples reference undefined variables (serviceEndpoint, key, directConnectionConfig, gatewayConnectionConfig) and placeholder versions, leaving minor gaps below fully executable.	4 / 5
Workflow Clarity	The Core Workflow sequences database/container/CRUD steps, but the CRUD chain performs a destructive deleteItem with no validation checkpoint or error-recovery feedback loop, which caps workflow clarity at 3 per the batch/destructive guideline.	3 / 5
Progressive Disclosure	A single well-organized SKILL.md with clearly headed sections and no nested references; structure is good, though some inline API reference and reference-link tables could conceivably be split, keeping it just below the ideal one-level-deep anchor.	4 / 5
	Total	15 / 20 Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is reasonably specific and distinct, naming the Azure Cosmos DB Java niche and several capabilities, but it lacks an explicit "Use when..." trigger clause and leans on the generic term "operations" rather than concrete actions. Adding a when-to-use clause and more concrete verbs would lift specificity and completeness.

Suggestions

Append an explicit trigger clause, e.g. "Use when building Java applications that need Cosmos DB NoSQL operations, partitioning, or geo-replicated reactive data access."

Replace the generic "NoSQL database operations" with concrete actions such as "create databases and containers, query items, manage throughput (RUs), and configure multi-region consistency".

Add natural user synonyms ("Cosmos", "partition key", "throughput/RUs", "change feed") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete capabilities ("global distribution, multi-model support, and reactive patterns"), but the lead action "NoSQL database operations" is generic and lacks specific verbs like create/query/insert, so it sits at the anchor listing a few concrete actions without comprehensive coverage.	3 / 5
Completeness	It clearly states what the skill does but contains no explicit "Use when..." trigger clause, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords ("Azure Cosmos DB", "NoSQL database", "reactive patterns") appear but common user phrasings and synonyms (e.g. "Cosmos", partitioning, throughput) are missing, matching the anchor with some relevant keywords lacking common variations.	3 / 5
Distinctiveness Conflict Risk	"Azure Cosmos DB SDK for Java" carves a clear niche with minimal overlap risk; the only mild risk is that "NoSQL database operations" could loosely collide with other database skills, keeping it just below the fully distinct anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/azure-cosmos-java/SKILL.md
Commit: debb2ec

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.