azure-compute-batch-java
Azure Batch SDK for Java. Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes.
44
46%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/azure-compute-batch-java/SKILL.mdQuality
Discovery
40%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, narrow domain (Azure Batch SDK for Java) with some relevant terminology, making it distinctive. However, it lacks explicit trigger guidance ('Use when...') and could be more specific about the concrete actions it supports beyond just 'run batch jobs'. The description reads more like a tagline than a selection guide.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Azure Batch in Java, batch processing, managing compute pools, scheduling HPC jobs, or working with the com.microsoft.azure.batch SDK.'
List more specific concrete actions such as 'create and manage compute pools, submit and monitor batch jobs, configure task dependencies, scale compute nodes, and retrieve job outputs.'
Include common user phrasing variations like 'batch processing', 'Azure Batch API', 'BatchClient', or 'cloud HPC' to improve trigger term 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 the skill does (run large-scale parallel and HPC batch jobs) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also only moderately detailed, placing this at 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Azure Batch', 'Java', 'HPC', 'parallel', 'pools', 'jobs', 'tasks', 'compute nodes' which are natural terms, but misses common variations like 'batch processing', 'Azure Batch API', 'batch compute', 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 domain is narrow and well-defined with distinct terminology like pools, compute nodes, and HPC. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at actionability with comprehensive, executable Java code examples covering all major Azure Batch SDK operations. However, it reads as a flat API reference rather than a workflow-oriented skill — there's no end-to-end sequence showing how to orchestrate a batch job from pool creation through result retrieval, and no validation checkpoints for destructive operations. The content is also too long for a single SKILL.md without supporting bundle files to offload detailed API examples.
Suggestions
Add a 'Quick Start Workflow' section at the top showing the end-to-end sequence: create pool → wait for pool ready → create job → add tasks → monitor with getJobTaskCounts → retrieve output → cleanup, with explicit validation checkpoints between steps.
Split detailed API examples (pool operations, job operations, task operations, node operations, job schedules) into separate bundle files and reference them from SKILL.md with one-level-deep links.
Remove the 'Key Concepts' table, 'Prerequisites' section, and boilerplate 'When to Use'/'Limitations' sections — Claude already knows these concepts and the boilerplate adds no value.
Add validation/verification steps for destructive operations (e.g., check pool state before deletion, verify task completion before job termination) to prevent errors in batch workflows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary content like the 'Key Concepts' table (Claude knows what pools/jobs/tasks are), the 'Prerequisites' section stating obvious requirements, the boilerplate 'When to Use' and 'Limitations' sections, and the 'Best Practices' section which is somewhat generic. The sheer length (~300 lines) for what is essentially an API reference could be tightened. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready Java code for every operation — client creation, pool/job/task/node/schedule CRUD, error handling, and bulk task creation. Import statements are included where needed, and examples use concrete values. | 3 / 3 |
Workflow Clarity | There is no sequenced workflow showing how to go from pool creation → job creation → task submission → monitoring → result retrieval. The content is organized as an API reference catalog rather than a workflow. For batch operations involving destructive actions (delete pool, terminate job), there are no validation checkpoints or confirmation steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of API examples with no bundle files to offload detailed references to. The reference links table at the end provides external navigation, but the inline content (~300 lines of code examples) would benefit from being split into separate files for pool operations, job operations, task operations, etc., with the SKILL.md serving as a concise overview. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%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
- sickn33/antigravity-awesome-skills
- Commit
9e5d4dd
- Reviewed
Table of Contents
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.