CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. Triggers: "AIProjectClient java", "azure ai projects java", "Foundry project java", "ConnectionsClient", "DatasetsClient", "IndexesClient".

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/plugins/azure-sdk-java/skills/azure-ai-projects-java/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A lean, largely executable SDK reference with a clear install-to-operate sequence and solid error-handling guidance. Its main weakness is discovery: the bundled references/examples.md — which contains the only coverage of datasets, deployments, and async clients — is orphaned, never linked from SKILL.md, and overlaps the body's installation content.

Suggestions

Add an Examples section that links to the bundled reference, e.g., '**More examples** (datasets, deployments, async clients): See [examples.md](references/examples.md)', so the 344-line bundle file is discoverable.

Declare AI_SEARCH_CONNECTION_NAME and AI_SEARCH_INDEX_NAME in the Environment Variables section (or note where they come from), since the createOrUpdate example reads them via System.getenv().

Add the com.azure:azure-identity dependency to the Installation section, since the Authentication code uses DefaultAzureCredentialBuilder, and either make the OpenAI evaluations snippet concrete or drop it.

DimensionReasoningScore

Conciseness

The body is code-first with minimal prose padding and assumes the reader's competence (e.g., the Client Hierarchy table plus brief build snippet). Minor trimmable redundancy: the table and the buildConnectionsClient() block overlap, and the 'Access OpenAI Evaluations' section adds little — anchor 4's 'efficient with minor instances that could be trimmed'.

4 / 5

Actionability

Concrete, mostly executable guidance throughout: Maven dependency, env vars, DefaultAzureCredential builder code, sub-client construction, list/createOrUpdate examples, and try/catch error handling. Minor gaps keep it below anchor 5: the Installation section omits the required com.azure:azure-identity dependency, AI_SEARCH_CONNECTION_NAME/AI_SEARCH_INDEX_NAME are used but never declared in the Environment Variables section, and the OpenAI evaluations snippet ('Use OpenAI evaluation APIs directly') has no usable next step.

4 / 5

Workflow Clarity

The section order forms a coherent sequence — Installation, Environment Variables, Authentication, Client Hierarchy, Core Operations, Error Handling — with the Error Handling section providing a recovery pattern (catch ResourceNotFoundException / HttpResponseException). No explicit validation checkpoints exist, but the operations are not destructive or batch, so the anchor-3 cap does not apply; this lands at anchor 4's 'clear sequence with minor validation gaps'.

4 / 5

Progressive Disclosure

The body itself is well sectioned, but the bundle contains references/examples.md (344 lines covering datasets, deployments, and async clients — none of which the body covers) that is never mentioned or linked anywhere in SKILL.md. Scored against the actual bundle structure, this is anchor 3: structure is present but organization is flawed — a reference exists on disk yet is not signaled at all, and its content (Maven dependency, client creation) duplicates the body.

3 / 5

Total

15

/

20

Passed

Description

73%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.

A solid, domain-specific description with a clear 'what' and an explicit trigger list that avoids the completeness cap. Its weaknesses are the absence of concrete action verbs (topic nouns only) and trigger phrasing that is keyword-based rather than situational.

Suggestions

Replace the topic-only capability list with action verbs, e.g., 'Enumerate connections, upload and manage datasets, create search indexes, and run model evaluations against an Azure AI Foundry project.'

Frame the trigger guidance situationally in addition to the keyword list, e.g., 'Use when developing Java applications against Azure AI Foundry or when the user mentions AIProjectClient or its sub-clients.'

Add missing natural trigger variations such as 'azure ai foundry java', 'azure-ai-projects maven', and 'EvaluationsClient'.

DimensionReasoningScore

Specificity

The description names the domain ("Azure AI Projects SDK for Java") and enumerates four capability areas ("connections, datasets, indexes, and evaluations"), but uses no concrete action verbs — it lists topics rather than actions like "enumerate connections" or "run evaluations". More informative than anchor 2's generic actions, but short of anchor 4's list of several specific actions.

3 / 5

Completeness

The 'what' is clear ("High-level SDK for Azure AI Foundry project management including connections, datasets, indexes, and evaluations") and the explicit 'Triggers:' line provides trigger guidance equivalent to a 'Use when...' clause, so the anchor-3 cap does not apply. However, the triggers are bare quoted keywords without situational framing (no 'Use when the user asks about...' phrasing), placing it at anchor 4 rather than anchor 5's fully explicit what-and-when.

4 / 5

Trigger Term Quality

Triggers like "AIProjectClient java", "azure ai projects java", and "ConnectionsClient" are terms a developer working with this SDK would naturally say. A few natural variations are missing (e.g., "azure ai foundry java", "azure-ai-projects maven", "evaluations java"), matching anchor 4's 'good coverage, a few natural terms missing' rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Azure AI Foundry project management via the Java SDK) with distinct triggers including SDK-specific class names like "ConnectionsClient" and "AIProjectClient" — these would only appear when this skill is wanted, giving minimal conflict risk with other Java or Azure skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

microsoft/skills

Path

.github/plugins/azure-sdk-java/skills/azure-ai-projects-java/SKILL.md

Reviewed

Table of Contents

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.