azure-ai-projects-java

Azure AI Projects SDK for Java. High-level SDK for Azure AI Foundry project management including connections, datasets, indexes, and evaluations.

1.59x

Quality

52%

Does it follow best practices?

Impact

97%

1.59x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-azure-ai-projects-java/SKILL.md

Quality

Discovery

40%

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 identifies a clear and distinct domain (Azure AI Projects SDK for Java) but lacks actionable trigger guidance and uses noun-list style rather than concrete action verbs. The absence of a 'Use when...' clause significantly weakens its utility for skill selection, and the listed capabilities are categories rather than specific operations.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to work with Azure AI Foundry projects in Java, manage AI project connections, create or query datasets/indexes, or run evaluations using the azure-ai-projects SDK.'

Replace the noun list with concrete action verbs, e.g., 'Create and manage Azure AI Foundry project connections, upload and query datasets, build search indexes, and run model evaluations using the Azure AI Projects SDK for Java.'

Include natural trigger terms users might say, such as 'azure-ai-projects dependency', 'AI Foundry Java client', or 'Azure AI project setup'.

Dimension	Reasoning	Score
Specificity	Names the domain (Azure AI Projects SDK for Java) and lists some capabilities (connections, datasets, indexes, evaluations), but these are high-level categories rather than concrete actions like 'create connections', 'manage datasets', or 'run evaluations'.	2 / 3
Completeness	Describes what the skill covers (Azure AI Projects SDK capabilities) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately detailed, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Azure AI', 'Java', 'SDK', 'Azure AI Foundry', 'connections', 'datasets', 'indexes', 'evaluations', but misses common user variations like 'Maven', 'azure-ai-projects', specific class names, or phrases users might naturally say like 'set up an Azure AI project'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Azure AI Projects SDK' and 'Java' creates a very specific niche that is unlikely to conflict with other skills. The mention of 'Azure AI Foundry' further narrows the scope distinctly.	3 / 3
	Total	8 / 12 Passed

Implementation

64%

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

This is a solid SDK reference skill with good executable code examples and clear structure. Its main weaknesses are some unnecessary content (best practices that are common knowledge, vacuous 'When to Use' section) and a lack of workflow sequencing that would help Claude understand how to chain operations together. The reference links table is a nice touch for discoverability.

Suggestions

Remove the 'Best Practices' section or reduce it to only non-obvious tips specific to this SDK; items like 'use environment variables' and 'handle pagination' are general knowledge.

Remove or rewrite the 'When to Use' section — it currently says nothing meaningful and wastes tokens.

Add a brief workflow sequence showing a typical end-to-end flow (authenticate → list connections → create dataset → create index → run evaluation) with validation checkpoints between steps.

Dimension	Reasoning	Score
Conciseness	Generally efficient with good code examples, but includes some unnecessary content like the 'Best Practices' section with tips Claude already knows (use env vars, handle pagination), and the 'When to Use' section is a meaningless tautology. The best practices list is mostly common sense for any Azure SDK.	2 / 3
Actionability	Provides fully executable Java code examples for authentication, listing connections, listing indexes, creating indexes, and error handling. Code is copy-paste ready with proper imports and realistic usage patterns.	3 / 3
Workflow Clarity	The skill presents individual operations clearly but lacks a cohesive workflow sequence. For an SDK reference skill this is somewhat acceptable, but there's no guidance on the order of operations (e.g., authenticate → get connections → create index → evaluate) and no validation checkpoints for operations that could fail.	2 / 3
Progressive Disclosure	The content is well-structured with clear sections and a reference links table pointing to external resources. However, the inline content is moderately long and some sections (like the full client hierarchy table + code, or the complete index creation example) could be split into separate reference files for a cleaner overview.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: boisenoise/skills-collections
Commit: f1697b6

Reviewed: 3 days 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.