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

48%

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

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

Quality

Content

57%Scale 1-3

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

The skill excels at actionability with comprehensive, executable Java code examples covering all major Azure Batch operations. However, it suffers from being a monolithic reference document rather than a well-structured skill — it lacks an end-to-end workflow showing the typical create-pool → create-job → add-tasks → monitor → cleanup sequence, and all content is crammed into a single file instead of being progressively disclosed. Some content like the Key Concepts table and Prerequisites section explain things Claude already knows.

Suggestions

Add an end-to-end workflow section at the top showing the typical sequence: create pool → wait for pool to be ready → create job → add tasks → monitor with getJobTaskCounts → retrieve results → cleanup, with explicit validation checkpoints (e.g., verify pool state before creating job).

Split the detailed API reference (Pool Operations, Job Operations, Task Operations, Node Operations, Job Schedule Operations) into a separate REFERENCE.md file, keeping only a quick-start example and navigation links in SKILL.md.

Remove the Key Concepts table, Prerequisites section, and 'When to Use' boilerplate — Claude already understands these Azure Batch concepts.

Add validation steps for destructive operations: e.g., check job state before termination, verify no running tasks before pool deletion.

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes some unnecessary elements like the 'Key Concepts' table explaining what pools, jobs, tasks, and nodes are — concepts Claude already knows. The 'Prerequisites' section and 'When to Use' boilerplate add no value. The extensive API reference could be trimmed or split into a separate file.	2 / 3
Actionability	The skill provides fully executable Java code examples for every operation — client creation, pool/job/task/node operations, error handling, and scheduling. Code is copy-paste ready with proper imports and realistic parameters.	3 / 3
Workflow Clarity	While individual operations are well-documented, there's no end-to-end workflow showing the typical sequence (create pool → wait for ready → create job → add tasks → monitor → get results → cleanup). For batch operations involving destructive actions like pool deletion and job termination, there are no validation checkpoints or feedback loops.	2 / 3
Progressive Disclosure	This is a monolithic wall of text at ~300+ lines with no content split into separate files. The entire API reference is inline when it should be in a separate reference file, with SKILL.md providing a quick-start overview and links to detailed operation guides.	1 / 3
	Total	8 / 12 Passed

Description

40%Scale 1-3

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 niche (Azure Batch SDK for Java) with some relevant domain terminology, but it lacks an explicit 'Use when...' clause which significantly hurts completeness. The specificity could be improved by listing more concrete actions beyond just 'run batch jobs'. The distinctiveness is strong due to the narrow technology focus.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to create or manage Azure Batch pools, jobs, tasks, or compute nodes using the Java SDK.'

List more specific concrete actions such as 'create and manage pools, submit and monitor jobs, schedule tasks, query compute node status, and handle job outputs.'

Include additional natural trigger terms like 'parallel computing', 'Azure Batch API', 'BatchClient', 'job scheduling', or 'cloud HPC' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Azure Batch SDK for Java) and mentions some actions/concepts (run large-scale parallel and HPC batch jobs) with key entities (pools, jobs, tasks, compute nodes), but doesn't list multiple distinct concrete actions like creating pools, monitoring tasks, or managing compute nodes.	2 / 3
Completeness	Describes what it does (run large-scale parallel and HPC batch jobs) but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent (not even implied beyond the domain name), this scores at 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Azure Batch', 'Java', 'HPC', 'batch jobs', 'pools', 'tasks', 'compute nodes', which are terms a user might use. However, it misses common variations like 'parallel computing', 'job scheduling', 'Azure Batch API', or file format references like 'BatchClient'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Azure Batch SDK' and 'Java' creates a very specific niche that is unlikely to conflict with other skills. The mention of pools, jobs, tasks, and compute nodes further narrows the scope distinctly.	3 / 3
	Total	8 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/azure-compute-batch-java/SKILL.md
Commit: ed71087

Reviewed: ~15 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.