azure-compute-batch-java
Azure Batch SDK for Java. Run large-scale parallel and HPC batch jobs with pools, jobs, tasks, and compute nodes.
56
46%
Does it follow best practices?
Impact
Pending
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 and distinct domain (Azure Batch SDK for Java) and mentions key concepts, giving it strong distinctiveness. However, it lacks an explicit 'Use when...' clause, which significantly hurts completeness, and the actions described are somewhat general rather than listing specific concrete operations. Adding trigger guidance and more specific actions would substantially improve this description.
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, handle auto-scaling configurations.'
Include additional natural trigger terms like 'batch processing', 'parallel computing', 'Azure Batch API', 'job scheduling in Azure' 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 the skill does (run large-scale parallel and HPC batch jobs) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric should cap completeness at 2, and the 'when' is entirely missing, placing this at a 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, but misses common variations like 'Azure Batch API', 'batch processing', 'job scheduling', or 'parallel computing'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: Azure Batch SDK specifically for Java. The combination of Azure Batch, Java SDK, and HPC/parallel computing concepts makes it highly unlikely to conflict with other skills. | 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 providing concrete, executable Java code examples for Azure Batch SDK operations, covering a wide range of API surface area. However, it reads more like an API reference catalog than a skill guide — it lacks a clear end-to-end workflow showing how to orchestrate a batch job from pool creation through task completion and result retrieval. The content is also somewhat verbose for a skill file, with boilerplate sections and concept explanations that don't add value for Claude.
Suggestions
Add a 'Quick Start Workflow' section at the top showing the complete sequence: create pool → wait for steady state → create job → add tasks → monitor with getJobTaskCounts → retrieve output → cleanup, with explicit validation checkpoints between steps.
Remove the 'Key Concepts' table, 'Prerequisites' section, and generic 'When to Use'/'Limitations' boilerplate — Claude already understands these concepts and the boilerplate adds no actionable value.
Consider splitting the detailed API operations (pool, job, task, node, schedule) into a separate REFERENCE.md file, keeping SKILL.md focused on the workflow and most common operations.
| 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 (Claude already knows this), the generic 'When to Use' and 'Limitations' boilerplate sections, and the 'Prerequisites' section is somewhat obvious. However, the code examples themselves are lean and well-structured. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready Java code examples for every major operation: client creation, pool/job/task/node operations, error handling, and scheduling. Import statements are included where needed, and examples cover both simple and advanced use cases like exit conditions and autoscale formulas. | 3 / 3 |
Workflow Clarity | There is no clear end-to-end workflow showing the sequence of operations (create pool → wait for pool ready → create job → create tasks → monitor → retrieve results). The skill is organized as an API reference with isolated operations but lacks sequencing, validation checkpoints, or feedback loops for operations that are inherently multi-step and involve long-running operations. | 1 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a reference links table pointing to external resources. However, the file is quite long (~300 lines of content) and could benefit from splitting detailed API operations into separate reference files while keeping SKILL.md as a concise overview with a quick-start workflow. | 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
76cbde3
- 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.