batch-request-handler
Batch Request Handler - Auto-activating skill for API Integration. Triggers on: batch request handler, batch request handler Part of the API Integration skill category.
34
0%
Does it follow best practices?
Impact
100%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/16-api-integration/batch-request-handler/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select it. It would be indistinguishable from other API-related skills in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Queues and sends multiple API requests in parallel, handles rate limiting, retries failed requests, and aggregates batch responses.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to send multiple API requests at once, process bulk API calls, handle batch endpoints, or manage parallel HTTP requests.'
Remove the redundant duplicate trigger term and replace with varied natural language keywords users might actually say, such as 'bulk API', 'parallel requests', 'batch processing', 'multiple API calls'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Batch Request Handler' is a name, not a description of capabilities. There are no specific actions like 'processes batch API calls', 'queues requests', or 'handles rate limiting'. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states the skill name, a redundant trigger, and a category label. There is no 'Use when...' clause or equivalent. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'batch request handler' repeated twice, which is the skill's own name rather than natural keywords a user would say. Missing terms like 'batch API', 'bulk requests', 'queue requests', 'parallel API calls', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'API Integration' and 'batch request handler' could overlap with numerous API-related skills. Without specific actions or scope, it would be nearly impossible to distinguish from other API or request-handling skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual instructional content. It repeatedly references 'batch request handler' without ever defining what one is, how to implement one, or providing any code, commands, or concrete guidance. It is entirely meta-description and would provide no value to Claude when activated.
Suggestions
Add concrete, executable code examples showing how to implement batch request handling (e.g., batching HTTP requests with rate limiting, chunking payloads, handling partial failures).
Define a clear multi-step workflow for batch request processing, including validation checkpoints such as verifying response status codes and handling retries on failure.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill itself rather than teaching the actual task.
Include specific patterns for common batch scenarios (e.g., parallel vs sequential batching, pagination, error aggregation) with production-ready code snippets.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague information about 'batch request handler' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no API patterns, no examples of batch request handling. The content only describes itself rather than instructing Claude on how to perform any task. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced operations. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no references to detailed materials, no links to related files, and no meaningful structural organization beyond boilerplate headings that all say the same thing. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.