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 template placeholder with no substantive content. It repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any 'Use when...' guidance. It would be nearly impossible for Claude to correctly select this skill from a pool of alternatives.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Queues, sends, and monitors batch API requests, handles rate limiting, and aggregates responses from bulk API calls.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to send multiple API requests in bulk, process batch jobs, handle API rate limits, or manage queued HTTP requests.'
Remove the duplicate trigger term and replace with diverse natural language variations users might say, such as 'bulk requests', 'batch API calls', 'mass API processing', 'queue API requests'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Batch Request Handler' and 'API Integration' are labels, not descriptions of what the skill actually does. There are no verbs describing capabilities 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. There is no 'Use when...' clause, and the 'what' is limited to a category label ('API Integration') with no explanation of actual functionality. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('batch request handler, batch request handler'), which is redundant and unlikely to match natural user language. Missing natural terms like 'bulk API calls', 'batch processing', 'queue requests', 'API batching', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Integration' is extremely broad and could conflict with any API-related skill. 'Batch Request Handler' is slightly more specific but without concrete actions or clear scope, it's unclear what distinguishes this 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 template with no substantive content. It contains no actionable guidance, no code examples, no workflow steps, and no specific information about batch request handling or API integration. Every section is generic boilerplate that could apply to any topic by swapping the skill name.
Suggestions
Add concrete, executable code examples showing batch request patterns (e.g., batching HTTP requests with rate limiting, chunking payloads, handling partial failures).
Define a clear multi-step workflow for implementing batch requests, including validation checkpoints such as verifying response status codes and handling retries on failure.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with specific technical content about batch request handler implementation.
Include at least one complete, copy-paste-ready example showing a real batch request scenario (e.g., batching API calls with concurrency limits using asyncio or similar).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content about batch request handling, and pads extensively with generic phrases like 'follows industry best practices' and 'generates production-ready code.' | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no API patterns, no examples of batch request structures, no specific libraries or tools. Every section is vague and abstract, describing what the skill does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The phrase 'step-by-step guidance' is mentioned but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed references, no supporting files, and no meaningful organization beyond boilerplate headings that contain no real content. | 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
3a2d27d
- 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.