processing-api-batches
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill processing-api-batchesOptimize bulk API requests with batching, throttling, and parallel execution. Use when processing bulk API operations efficiently. Trigger with phrases like "process bulk requests", "batch API calls", or "handle batch operations".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill fails to deliver on its stated purpose of optimizing bulk API requests with batching, throttling, and parallel execution. The content is generic API development boilerplate that could apply to any API project, with no specific guidance on batch processing patterns, rate limiting strategies, or concurrent request handling. The skill needs to be completely rewritten to focus on its actual domain.
Suggestions
Add concrete code examples showing batch request patterns (e.g., chunking arrays, Promise.all with concurrency limits, queue-based processing)
Include specific throttling implementations with rate limiting logic and backoff strategies
Add validation checkpoints for batch operations: how to handle partial failures, retry logic, and progress tracking
Remove generic API development content and focus exclusively on bulk/batch processing concerns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains significant padding and generic content that doesn't relate to the stated purpose (bulk API batching). The overview repeats itself, prerequisites are generic boilerplate, and the instructions describe general API development rather than batch processing, throttling, or parallel execution. | 1 / 3 |
Actionability | No concrete code examples for batching, throttling, or parallel execution. Instructions are vague directives like 'Generate boilerplate code' and 'Implement endpoint handlers' without any executable guidance. The Bash command reference 'Bash(api:batch-*)' is unexplained. | 1 / 3 |
Workflow Clarity | Steps are poorly organized with duplicate numbering (two separate lists both starting at 1). No validation checkpoints for batch operations, no error recovery flows, and no guidance on handling partial failures in bulk requests—critical for batch processing. | 1 / 3 |
Progressive Disclosure | References external files for implementation details, errors, and examples which is appropriate structure. However, the main content provides almost no useful overview—it's mostly generic placeholders, making the references feel like deflection rather than progressive disclosure. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
82%This is a solid skill description that clearly communicates its purpose and provides explicit trigger guidance. The main weakness is that the capabilities listed (batching, throttling, parallel execution) are somewhat abstract rather than concrete actions, and there's moderate risk of overlap with other API-related skills.
Suggestions
Add more concrete actions like 'retry failed requests', 'manage rate limits', or 'aggregate responses' to improve specificity
Include additional distinguishing trigger terms like 'rate limiting', 'concurrent requests', or 'API queue' to reduce conflict risk with general API skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (bulk API requests) and lists some actions (batching, throttling, parallel execution), but these are somewhat abstract concepts rather than concrete actions like 'retry failed requests' or 'split large payloads'. | 2 / 3 |
Completeness | Clearly answers both what (optimize bulk API requests with batching, throttling, parallel execution) and when (explicit 'Use when' clause and 'Trigger with phrases' providing clear guidance on when to select this skill). | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms: 'process bulk requests', 'batch API calls', 'handle batch operations'. These are phrases users would naturally say when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to bulk/batch API operations, but could potentially overlap with general API skills or rate-limiting skills. The 'bulk' and 'batch' focus helps distinguish it, but 'API requests' is fairly broad. | 2 / 3 |
Total | 10 / 12 Passed |
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.