CtrlK

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.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill batch-request-handler

What are skills?

Overall
score

17%

Review — 0%

Does it follow best practices?

Validation — 11 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Activation

This description is severely lacking across all dimensions. It provides no concrete actions, no natural trigger terms, no explicit 'when to use' guidance, and is too generic to distinguish from other API-related skills. The redundant trigger term ('batch request handler' repeated twice) suggests auto-generated content without meaningful curation.

Suggestions

Add specific concrete actions the skill performs (e.g., 'Queues multiple API requests, manages rate limiting, aggregates batch responses, handles retry logic for failed requests').

Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when processing multiple API calls at once, handling bulk data transfers, managing request queues, or when the user mentions batch processing, bulk requests, or API throttling').

Specify the types of APIs or batch scenarios this handles to distinguish it from other API skills (e.g., 'REST API batch endpoints', 'async job processing', 'paginated data retrieval').

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' (no actions described) and 'when should Claude use it' (no explicit use cases or triggers beyond the redundant skill name). Both components are missing.	1 / 3
Trigger Term Quality	The trigger terms are just the skill name repeated twice ('batch request handler, batch request handler'). These are not natural keywords users would say when needing this functionality - users would more likely say 'process multiple API calls', 'bulk requests', or 'queue API requests'.	1 / 3
Distinctiveness Conflict Risk	'API Integration' is extremely generic and could conflict with many other API-related skills. Without specific actions or use cases, there's no clear niche to distinguish this from other integration or request-handling skills.	1 / 3
	Total	4 / 12 Passed

Implementation

This skill is a placeholder 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 could be replaced with a single sentence: 'This skill helps with batch requests' and convey the same information.

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 content ('This skill provides...', 'Capabilities include...') and replace with actual technical guidance

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 provided. 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 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 empty section headers. No references to detailed documentation, no examples, no navigation to related resources. The 'Related Skills' section mentions a category but provides no actual links.	1 / 3
	Total	4 / 12 Passed

Validation

69%

Warnings & errors only

Validation — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
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
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow	Warning

	Total	11 / 16 Passed

Reviewed: 23 days ago

Table of Contents

Activation Implementation Validation

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.