processing-api-batches

Optimize 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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-structured, lean, and clearly sequenced with strong validation and error-recovery feedback loops, plus appropriate one-level-deep references to real bundle files. The main gap is that executable, copy-paste-ready code is deferred to a reference rather than shown inline in the body.

Suggestions

Add one short inline executable snippet in the Instructions (e.g. the synchronous batch handler or the p-limit concurrency loop) so the body reaches copy-paste-ready actionability without requiring a reference hop.

Tighten the single-sentence Overview to remove the slight overlap with the frontmatter description, since that capability summary is already stated above.

Dimension	Reasoning	Score
Conciseness	The body is dense yet lean: numbered steps carry concrete values (1000 items, 413/207/202, concurrency 10), no preamble explaining concepts Claude already knows, and an error table plus compact examples — every token earns its place, matching the level-3 anchor.	3 / 3
Actionability	Highly specific guidance (request/response shapes, thresholds, named libraries, output paths) but no inline executable code — the copy-paste-ready code the level-3 anchor expects lives one reference away in examples.md, leaving it between level 2 and 3.	2 / 3
Workflow Clarity	A clear 9-step sequence with explicit decision points (sync <100 vs async >100), an upfront validation step, a dedicated test step, and error-recovery feedback loops (savepoints, heartbeat + retry from checkpoint), matching the level-3 anchor for batch/destructive operations.	3 / 3
Progressive Disclosure	A concise overview splits details into three clearly signaled, one-level-deep references (implementation.md, errors.md, examples.md), all verified to exist as real files, with easy navigation and no nesting, matching the level-3 anchor.	3 / 3
	Total	11 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly covers what, when, and trigger phrases within a distinct batch-API niche. Its only weakness is that the named capabilities are abstract categories rather than concrete operations, which limits the specificity score.

Suggestions

Replace abstract capability gerunds ("batching, throttling, parallel execution") with one or two concrete operations, e.g. "combine many API calls into one batch request, throttle rate-limited endpoints, and run operations in parallel."

Broaden trigger-phrase coverage with common variations users say, such as "bulk API", "API rate limiting", or "throttle requests".

Dimension	Reasoning	Score
Specificity	Names a domain and several capability categories ("batching, throttling, and parallel execution"), but these are abstract gerunds rather than concrete operations, so it stops short of level 3 while being far from vague level-1 language.	2 / 3
Completeness	Clearly answers both what ("Optimize bulk API requests with batching, throttling, and parallel execution") and when via explicit "Use when…" and "Trigger with phrases like…" clauses, matching the level-3 anchor exactly.	3 / 3
Trigger Term Quality	Explicitly lists natural user-facing trigger phrases ("process bulk requests", "batch API calls", "handle batch operations") giving good coverage of terms a user would actually say, matching the level-3 anchor rather than jargon-only level 1.	3 / 3
Distinctiveness Conflict Risk	The "bulk/batch API" niche plus batch-specific triggers make it clearly distinguishable from general API skills and unlikely to fire for the wrong skill, matching the level-3 clear-niche anchor.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 2cafb23

Reviewed: about 7 hours ago

Table of Contents

Discovery 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.