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

64%

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

76%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 executable Java examples across the full Azure Batch surface area, and is reasonably concise and well-organized. Its main gap is the absence of validation/feedback-loop checkpoints for destructive and batch operations, which the rubric caps at workflow_clarity 3.

Suggestions

Add validation checkpoints before destructive/batch operations, e.g. verify a pool exists and confirm intent before beginDeletePool, and check task counts before terminating a job.

Include a brief feedback-loop pattern (validate -> fix -> retry) for long-running operations like pool resize or createTasks to satisfy the rubric's destructive/batch guidance.

Consider extracting the reference-link table and detailed API options into a separate reference file to push progressive disclosure toward a 5, though this is optional given the single-file scope.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient: terse section headers, a compact concepts table, and executable code blocks with almost no padded prose or explanation of concepts Claude already knows; only minor import repetition keeps it from a 5.	4 / 5
Actionability	Nearly every operation (pool, job, task, node, schedule, error handling) ships complete, copy-paste-ready Java code using concrete model classes, covering the common cases comprehensively.	5 / 5
Workflow Clarity	Operations are clearly grouped by entity, but destructive and batch operations (delete pool/job, terminate job, reboot node, createTasks) lack validation checkpoints or confirm-before-proceed steps; per the guidelines this caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist, so the skill is a single well-sectioned document with an external Reference Links table (no nested references); good organization, though the ~380-line monolith could in principle split an advanced/API section.	4 / 5
	Total	16 / 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 distinct niche (Azure Batch SDK for Java) and conveys the core capability, but it lacks an explicit 'when to use' trigger clause and richer natural-language synonyms. Adding a 'Use when...' sentence with common user phrasings would raise completeness and trigger quality.

Suggestions

Append a 'Use when...' clause with concrete triggers, e.g. 'Use when running parallel or HPC batch jobs in Azure, managing Batch pools/jobs/tasks, or working with the azure-compute-batch Java SDK.'

Add natural synonym keywords a user might say, such as 'batch processing', 'compute jobs', or 'parallel workloads', to improve trigger-term coverage.

Enumerate one or two more distinct concrete actions (e.g. 'create and resize compute pools', 'submit and monitor tasks') to lift specificity above anchor 3.

Dimension	Reasoning	Score
Specificity	Names the Azure Batch domain and the action 'Run large-scale parallel and HPC batch jobs', plus the entities (pools, jobs, tasks, compute nodes), but does not enumerate several distinct concrete actions; it falls at the anchor-3 level rather than the more comprehensive anchor-4.	3 / 5
Completeness	It clearly states what the skill does but provides no explicit 'Use when...' trigger clause; per the guidelines a missing when-clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant keywords like 'Azure Batch SDK for Java', 'parallel', and 'HPC batch jobs', but lacks common natural synonyms (e.g. 'batch processing', 'compute') and any file extensions users might say.	3 / 5
Distinctiveness Conflict Risk	The Azure Batch + Java combination is a clear, narrow niche with minimal overlap risk against other skills; not a 5 only because it could marginally overlap with broader Azure SDK skills.	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: sickn33/antigravity-awesome-skills
Path: skills/azure-compute-batch-java/SKILL.md
Commit: 1f67c44

Reviewed: about 14 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.