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.

Quality

72%

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 ./skills/azure-ai-projects-java/SKILL.md
SKILL.md
Quality
Evals
Security

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 a lean, largely executable reference for the Azure AI Projects Java SDK with good structure and mostly copy-paste-ready examples. Its main weaknesses are the lack of an explicitly sequenced workflow with integrated validation checkpoints and the purely cautionary, code-less evaluation section.

Suggestions

Frame setup as an ordered workflow with embedded checkpoints: install -> set PROJECT_ENDPOINT -> build client -> 'compile a minimal test' -> operate, validating explicitly before destructive or costly operations (index creation, dataset upload, evaluations).

Add executable code for the Evaluations integration (or a clearly signaled reference file); the section currently gives only a caution about not assuming an OpenAI EvalService.

Trim the boilerplate 'When to Use' section and tighten the run-on 'Version and data boundary' paragraph to recover token budget.

DimensionReasoningScore

Conciseness

The body is dominated by tight, executable code blocks and a client-purpose table with little padding. Minor over-explanation could be trimmed: the boilerplate 'When to Use' section ('This skill is applicable to execute the workflow or actions described in the overview') and the run-on 'Version and data boundary' paragraph.

4 / 5

Actionability

Mostly executable, copy-paste-ready guidance: Maven dependency XML, PROJECT_ENDPOINT env var, DefaultAzureCredential builder, sub-client construction, and working list/create-or-update examples with try/catch error handling. Not 5 because the Evaluations section provides only a caution with no code and the error-handling snippet references undefined variables (indexName, version).

4 / 5

Workflow Clarity

Sections follow a rough install-configure-authenticate-operate sequence and the boundary section mentions some checkpoints ('compile a minimal test', 'inspect destination, retention and cost before executing'), but no validation steps are integrated into the operational flow. This matches the level-3 anchor (steps listed, checkpoints missing or implicit) rather than 4.

3 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers, a client-purpose table, and an external Reference Links table for deeper navigation; no bundle files exist to reference. Not 5 because navigation relies only on external URLs with no in-skill one-level-deep references.

4 / 5

Total

15

/

20

Passed

Description

65%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 carves out a clear, distinctive niche (Azure AI Projects SDK for Java) with good domain keywords, but its verbs are generic ('project management including...') and it lacks any 'Use when...' trigger clause, capping completeness and specificity at mid-level.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when working with the Azure AI Projects SDK for Java, Azure AI Foundry projects, or when the user mentions connections, datasets, indexes, or evaluations in a Java context.'

Replace the generic 'project management' phrasing with concrete actions: 'Enumerate connections, upload datasets, create and manage search indexes, run model evaluations.'

Include natural trigger variations such as 'Azure AI Foundry', 'AI Studio project', or 'Java AI SDK' to broaden keyword coverage.

DimensionReasoningScore

Specificity

The domain is named ('Azure AI Foundry project management') and four resource areas are enumerated ('connections, datasets, indexes, and evaluations'), but the only action verb is the generic 'management' — no concrete operations like 'enumerate connections' or 'upload datasets'. Fits the level-3 anchor (domain plus limited concrete actions) rather than 4, which expects several explicit actions.

3 / 5

Completeness

The 'what' is clear (SDK for Azure AI Foundry project management covering connections, datasets, indexes, and evaluations), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric says caps completeness at 3.

3 / 5

Trigger Term Quality

Includes strong natural terms users would say ('Azure AI Projects SDK', 'Java', 'Azure AI Foundry', 'connections', 'datasets', 'indexes', 'evaluations'). A few natural variations are missing (e.g., 'AI Studio', 'Foundry SDK'), so it sits at level 4 rather than 5's comprehensive synonym and extension coverage.

4 / 5

Distinctiveness Conflict Risk

A clearly defined niche — the Azure AI Projects SDK explicitly for Java — with distinct product-name triggers and minimal conflict risk against related Azure or Python skills. Not 4 because the language and SDK are explicitly named, leaving little overlap ambiguity.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

sickn33/agentic-awesome-skills

Path

skills/azure-ai-projects-java/SKILL.md

Revision

8aa4123

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill