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
Quality
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 fails to explain what the skill does, when to use it, or provide meaningful trigger terms. The repeated trigger term and generic category name provide almost no value for skill selection.
Suggestions
Add specific actions the skill performs (e.g., 'Queues multiple API calls, manages rate limiting, processes bulk data requests, handles async batch operations').
Add a 'Use when...' clause with natural trigger terms like 'bulk API calls', 'multiple requests', 'batch processing', 'rate limiting', 'async operations'.
Differentiate from other API skills by specifying the type of batch requests handled (e.g., specific APIs, data formats, or use cases like 'processing large datasets' or 'parallel API calls').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Batch Request Handler') and category ('API Integration') without describing any concrete actions. There are no verbs indicating what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger conditions. | 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. No variations or related terms are provided. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'API Integration' is extremely generic and could conflict with many other API-related skills. 'Batch Request Handler' provides some specificity but without explaining what kind of batch requests or what actions are performed. | 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 actual content. It describes what a batch request handler skill should do without providing any implementation details, code examples, API patterns, or actionable guidance. The entire content is meta-description rather than instruction.
Suggestions
Add concrete code examples showing how to implement batch request handling (e.g., request queuing, rate limiting, response aggregation)
Define a clear workflow for batch processing: request collection → validation → execution → error handling → response assembly
Include specific patterns for common batch scenarios: parallel vs sequential execution, retry logic, partial failure handling
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no actual technical substance. It explains what the skill does in abstract terms without providing any concrete information Claude doesn't already know. Every section is padded boilerplate. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance whatsoever. The content only describes what the skill claims to do ('provides step-by-step guidance', 'generates production-ready code') without actually providing any of it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for handling batch requests. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no examples, no links to related materials. The 'Related Skills' section mentions a category but provides no navigation. | 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
0c08951
- 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.