azure-compute-batch-java

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

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

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 body is highly actionable, with complete executable Java examples across all resource types, and mostly lean. Its weaknesses are structural: the entire API reference is monolithically inlined with no progressive disclosure, and destructive/batch operations lack the validation checkpoints the rubric requires, capping workflow clarity at 3.

Suggestions

Move the bulk per-operation API reference into one-level-deep reference files (e.g. references/pools.md, references/jobs.md, references/tasks.md) and keep only installation, client creation, and a quick-start example in SKILL.md.

Add validation checkpoints around risky operations, e.g. verify pool state after resize via getPool, check task counts with getJobTaskCounts after createTasks, and confirm job/pool state before terminate/delete.

Remove the generic boilerplate "When to Use" and "Limitations" sections (they restate the description without skill-specific content) and either drop the pinned beta version or note it in a clearly marked version/compatibility section.

Dimension	Reasoning	Score
Conciseness	The body is dense, executable code with terse headers, but contains boilerplate filler ("This skill is applicable to execute the workflow or actions described in the overview", generic Limitations disclaimers) and an inline pinned version "1.0.0-beta.5". This matches anchor 4 (efficient with minor instances that could be trimmed), not 5, because the filler sections add no skill-specific value.	4 / 5
Actionability	Every section provides copy-paste-ready Java covering the common cases, from "batchClient.createPool(new BatchPoolCreateParameters(...))" through polling ("poller.waitForCompletion()") to error handling with BatchErrorException. This matches anchor 5 (fully executable, specific examples covering common cases).	5 / 5
Workflow Clarity	Content is organized as a per-resource API catalog rather than a sequenced workflow, and destructive and batch operations ("beginDeletePool", "beginTerminateJob", "createTasks" with 1000 tasks) lack any validation or verification steps. The rubric explicitly caps workflow clarity at 3 for batch/destructive skills without validation, so scores of 4-5 are unavailable despite the LRO polling shown.	3 / 5
Progressive Disclosure	Roughly 300 lines of API reference are inlined directly in SKILL.md with no bundle files at all, matching anchor 3's example of inline content that should be separate. It scores above 2 because section headers (Pool/Job/Task/Node/Job Schedule Operations) provide real structure, but below 4 because the bulk reference belongs in separate one-level-deep files.	3 / 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 names a distinct, well-scoped niche and includes natural trigger keywords, but it lists only one concrete action and completely lacks a "Use when..." clause, capping completeness and specificity at mid-scale.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about Azure Batch, running HPC or parallel workloads on Azure, or managing Batch pools, jobs, tasks, or compute nodes from Java."

Expand the capability list beyond a single action to cover the concrete operations the skill supports, e.g. "Create and resize pools, submit jobs and task collections, retrieve task output, and manage compute nodes."

Include common user synonyms such as "parallel processing", "compute nodes", or "Azure Batch account" to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	"Run large-scale parallel and HPC batch jobs" is a single concrete action, and "pools, jobs, tasks, and compute nodes" names domain objects rather than actions. It matches anchor 3 (domain plus 1-2 concrete actions) rather than 4, which requires several specific actions.	3 / 5
Completeness	The "what" is clear ("Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes") but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. It cannot be 2 because the "what" is concrete, and cannot be 4 because the "when" is entirely absent rather than just imprecise.	3 / 5
Trigger Term Quality	"Azure Batch", "Java", "HPC", "batch jobs", "pools", and "compute nodes" are natural phrases users would say, giving good keyword coverage. It falls short of anchor 5 because synonyms like "parallel processing" or "Batch account" are missing.	4 / 5
Distinctiveness Conflict Risk	"Azure Batch SDK for Java" carves out a clear niche with distinct triggers (Azure Batch, HPC, batch jobs) and minimal overlap with other skills. This matches anchor 5 directly; no neighboring anchor fits better.	5 / 5
	Total	15 / 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: sickn33/agentic-awesome-skills
Path: skills/azure-compute-batch-java/SKILL.md
Commit: 7b534bc

Reviewed: 6 days 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.