azure-ai-agents-persistent-java

Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools.

1.63x

Quality

61%

Does it follow best practices?

Impact

100%

1.63x

Average score across 3 eval scenarios

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-ai-agents-persistent-java/SKILL.md

The canonical home for this skill is azure-ai-agents-persistent-java in sickn33/agentic-awesome-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 a well-structured, mostly executable guide with concrete Java examples, but its workflow lacks validation checkpoints before destructive cleanup and the run-poll loop does not handle failure statuses, capping workflow clarity.

Suggestions

Add a validation step before cleanup — e.g. check run.getStatus() for COMPLETED before listing messages and only delete thread/agent after confirming the run succeeded.

Make the polling loop handle terminal failure statuses (FAILED, CANCELLED, REQUIRES_ACTION) so Claude does not proceed to read messages from a failed run.

Declare or comment the modelDeploymentName/modelName variables (tie them to the MODEL_DEPLOYMENT_NAME env var) and wrap Thread.sleep in try/catch to make examples copy-paste runnable.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with tight, copy-pasteable Java code and no padding about basic concepts, but it has minor redundancy — the opening line repeats the frontmatter description and the 'When to Use' line ('applicable to execute the workflow or actions described in the overview') is vague filler — keeping it just below a 5.	4 / 5
Actionability	Concrete, executable Java code is provided for every workflow step (auth, create agent/thread/message, run, list messages, cleanup, error handling), with only minor gaps such as the undeclared modelDeploymentName/modelName variables and Thread.sleep not wrapped in try/catch.	4 / 5
Workflow Clarity	The 6-step Core Workflow is clearly sequenced, but the run-poll loop ignores Failed/Cancelled/RequiresAction statuses and the destructive cleanup (deleteThread/deleteAgent) has no validation checkpoint; per the destructive-operation rule this caps workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist, but the body is well-organized into clearly headed sections and external references are surfaced in a clean 'Reference Links' table rather than buried, fitting the 'good structure, references mostly clear' 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 clearly identifies a specific niche and names concrete SDK entities, but it lacks an explicit 'Use when' trigger clause and relies on generic action verbs, capping completeness and trigger quality at the midpoint.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases, e.g. 'Use when building Java apps that need persistent Azure AI agents with threads, messages, and runs.'

Replace generic verbs ('creating and managing') with specific concrete actions like 'create agents, manage threads, send messages, start and poll runs, and attach tools'.

Include user-natural synonyms such as 'Java AI assistant', 'Azure agent thread', or 'persistent chat agent' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure AI Agents Persistent SDK for Java') and concrete entities ('threads, messages, runs, and tools'), but the actions ('creating and managing') are generic rather than multiple specific actions, fitting the anchor for domain + 1-2 concrete actions.	3 / 5
Completeness	It clearly states what the skill does ('Low-level SDK for creating and managing AI agents...') but provides no 'Use when...' clause or equivalent trigger guidance; per the judging guidelines a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant terms ('AI agents', 'Azure', 'Java', 'threads, messages, runs, and tools') but is dominated by technical jargon ('Persistent SDK', 'runs') and lacks common natural variations users would say, matching the 'some relevant keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'Azure AI Agents Persistent SDK for Java' niche is specific and largely distinct, with only minor overlap risk against closely related Azure or OpenAI agent skills; it is not a clear 5 because the description lacks distinct trigger phrases.	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-claude/skills/azure-ai-agents-persistent-java/SKILL.md
Commit: 731a928

Reviewed: 19 hours 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.