azure-compute-batch-java

Azure Batch SDK for Java. Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes.

3.84x

Quality

66%

Does it follow best practices?

Impact

96%

3.84x

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/skills/azure-compute-batch-java/SKILL.md

The canonical home for this skill is azure-compute-batch-java in sickn33/agentic-awesome-skills

Quality

Content

72%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 highly actionable with comprehensive, executable Java examples and clean section organization, but it lacks validation checkpoints for its destructive/batch operations and keeps everything in a single long file rather than practicing progressive disclosure.

Suggestions

Add explicit validation checkpoints before destructive operations, e.g. list/confirm pool has no running jobs before beginDeletePool, and verify task state before terminateTask, to lift workflow_clarity past the batch-operation cap.

Provide an end-to-end sequenced workflow (create pool → create job → add tasks → monitor task counts → clean up) with a validate-after-each-step feedback loop, rather than only isolated per-operation snippets.

Move the bulk API reference into one-level-deep reference files (e.g. references/pool-operations.md, references/task-operations.md) and have SKILL.md overview + link to them, so the main file stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, copy-paste-ready Java with minimal prose and assumes Claude's competence; minor over-explanation (the Key Concepts table defining Pool/Job/Task/Node) and a pinned version ('1.0.0-beta.5') that can go stale keep it just below 5.	4 / 5
Actionability	Fully executable, copy-paste-ready code covers the common cases across pools, jobs, tasks, nodes, and job schedules with concrete method calls and parameters, matching the 'fully executable, specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	Operations are organized by resource lifecycle (create/get/list/resize/delete) giving an implicit sequence, but this is a batch/destructive-operation skill with no validation checkpoints (no 'verify pool empty before delete', no 'confirm task done before terminate'); per the rubric, missing validation in batch/destructive workflows caps this at 3.	3 / 5
Progressive Disclosure	Section headers and a Reference Links table give good in-file structure, but with no references/scripts/assets bundle files the full ~375-line API reference is inlined in SKILL.md rather than split into one-level-deep reference files, fitting the 'content that should be separate is inline' anchor.	3 / 5
	Total	15 / 20 Passed

Description

61%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 is specific and well-targeted to the Azure Batch + Java niche, but it omits an explicit 'Use when...' trigger clause, which caps its completeness. Trigger-term coverage is solid though not exhaustive.

Suggestions

Add an explicit trigger clause, e.g. 'Use when running or scaling parallel/HPC batch workloads on Azure Batch from Java, or when the user mentions Azure Batch, batch jobs, pools, tasks, or compute nodes.'

Broaden trigger synonyms to include 'high-performance computing', 'scheduled jobs', and 'scale-out' so the description matches more natural user phrasings.

List a second distinct action beyond 'run batch jobs' (e.g. 'manage pools, jobs, tasks, and compute nodes') to lift specificity toward 4-5.

Dimension	Reasoning	Score
Specificity	Names the domain clearly ('Azure Batch SDK for Java') and one concrete action ('Run large-scale parallel and HPC batch jobs') plus the resource entities (pools, jobs, tasks, compute nodes), but these are nouns rather than several distinct actions, so it does not reach the 'lists several specific actions' bar of 4.	3 / 5
Completeness	It has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance; per the rubric guideline a missing trigger clause caps completeness at 3, and the body's separate 'When to Use' line does not count toward the description field.	3 / 5
Trigger Term Quality	Natural terms a user would say are present — 'Azure Batch', 'Java', 'parallel', 'HPC', 'batch jobs' — giving good keyword coverage; a few natural synonyms (e.g. 'high-performance computing', 'scale', 'scheduled jobs') are missing, so it stops short of 5.	4 / 5
Distinctiveness Conflict Risk	'Azure Batch SDK for Java' plus 'HPC batch jobs' carves a clear niche with minimal conflict risk, though the generic 'batch jobs' phrase leaves minor overlap risk with broader Azure SDK or general batch-processing skills, keeping it just below 5.	4 / 5
	Total	14 / 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/skills/azure-compute-batch-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.