Name: azure-cosmos-java
Rating: 51.2 (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

56%

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-claude/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

65%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 body is a well-organized, executable Cosmos SDK reference with strong code coverage of auth, CRUD, query, and error handling. Its main gaps are a lack of validation feedback loops in destructive DB workflows and a monolithic structure with no progressive disclosure to bundle files.

Suggestions

Add a validation checkpoint to the CRUD workflow (e.g. verify the item exists before update, confirm delete via read returning 404) with a fix-and-retry loop so destructive operations clear the workflow-clarity cap.

Move the bulk API reference and advanced client-customization material into separate reference files (e.g. REFERENCE.md, ADVANCED.md) and link to them one level deep from SKILL.md.

Define or stub the placeholder variables (serviceEndpoint, directConnectionConfig, gatewayConnectionConfig) in the "With Customizations" example so it is fully copy-paste runnable.

Dimension	Reasoning	Score
Conciseness	The body is dense and code-heavy with minimal padding; "Key Concepts" cover Cosmos-specific notions (partition keys, consistency levels, RUs) rather than basics Claude already knows, fitting anchor 4; not 5 because the reference-link and best-practice sections add some content that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready Java for auth, CRUD, query, and error handling across common cases, matching anchor 4; not 5 because the "With Customizations" example references undefined variables (serviceEndpoint, directConnectionConfig, gatewayConnectionConfig).	4 / 5
Workflow Clarity	The CRUD example sequences create→read→update→delete and an error-handling section exists, but there are no validation checkpoints or validate→fix→retry loops; since database CRUD is destructive, the missing-feedback-loop guidance caps this at 3.	3 / 5
Progressive Disclosure	The single ~252-line file has clear section headers but inlines API-reference and advanced-configuration content that would better live in separate bundle files, matching anchor 3; not 4 because no one-level-deep references split the bulk out.	3 / 5
	Total	14 / 20 Passed

Description

48%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 names a clear, specific niche (Azure Cosmos DB SDK for Java) but stops at feature-listing rather than concrete actions and omits any "Use when..." trigger guidance. It is distinguishable yet under-specified on when Claude should invoke it.

Suggestions

Add an explicit "Use when..." clause naming concrete trigger phrases (e.g. "Use when working with Azure Cosmos DB, NoSQL document databases in Java, or when the user mentions Cosmos DB, partition keys, or RUs").

Replace generic feature nouns with concrete actions, e.g. "Create databases and containers, run CRUD and SQL queries, configure consistency and partitioning for the Azure Cosmos DB Java SDK."

Include natural synonyms a user would actually say ("Cosmos DB", "document database") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"NoSQL database operations" is generic and the description lists SDK features ("global distribution, multi-model support, and reactive patterns") rather than concrete actions, matching anchor 2; it does not reach 3 because no concrete operations like create/query are named.	2 / 5
Completeness	It clearly states what the skill is ("Azure Cosmos DB SDK for Java" doing "NoSQL database operations") but provides no "Use when..." clause, so per the missing-trigger guidance completeness is capped at 3.	3 / 5
Trigger Term Quality	"Azure Cosmos DB SDK for Java" and "NoSQL database" are relevant natural terms but common synonyms and variations (e.g. "Cosmos DB", "document database") are missing, fitting anchor 3 rather than the fuller coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	"Azure Cosmos DB SDK for Java" carves a clear niche with distinct triggers and only minor overlap risk against other Azure or Java SDK skills, matching anchor 4; it is not 5 because no explicit trigger phrase sharpens the boundary.	4 / 5
	Total	12 / 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-claude/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.