CtrlK
BlogDocsLog inGet started
Tessl Logo

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

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

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

The content is a lean, actionable overview that delegates executable code to real reference files and covers sync/async batching, concurrency, partial failure, and progress tracking. Its main gap is the absence of an explicit validation feedback loop in the main workflow, which the rubric requires for batch operations.

Suggestions

Add an explicit validation checkpoint with a feedback loop (e.g., 'validate all items -> if errors, return them -> only process valid batches -> retry failed items') to the Instructions sequence.

Inline at least one short executable code snippet in the body (e.g., the batch request/response shape) so the core pattern is copy-paste ready without opening a reference.

Make the validation step a numbered checkpoint that gates processing (step 8 currently describes validation but does not present it as a blocking gate with re-validation on failure).

DimensionReasoningScore

Conciseness

The body is dense and instructive with no padding explaining basic concepts Claude already knows; every line adds specific guidance (thresholds, libraries, response shapes).

3 / 3

Actionability

Provides concrete request/response formats, specific thresholds (1000 max -> 413, <100 sync, >100 async -> 202), named libraries (p-limit, asyncio.Semaphore, Bull/BullMQ, Redis), and points to executable code in references; guidance is highly actionable.

3 / 3

Workflow Clarity

The 9 steps are clearly sequenced and include upfront validation (step 8) and testing (step 9), but for a batch-operation skill there is no explicit validate -> fix -> retry feedback checkpoint, which caps this dimension at 2 per the rubric.

2 / 3

Progressive Disclosure

The body is a well-organized overview with clearly signaled, one-level-deep references (implementation.md, errors.md, examples.md) that are real files, plus cleanly separated sections.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

The description is concise, third-person, and covers what the skill does plus explicit when-to-use triggers with natural phrasing. It is distinguishable from generic API skills and avoids over-claims.

DimensionReasoningScore

Specificity

Names the domain (bulk API requests) and three concrete actions — 'batching, throttling, and parallel execution' — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Optimize bulk API requests with batching, throttling, and parallel execution') and when ('Use when processing bulk API operations efficiently'), with explicit trigger guidance.

3 / 3

Trigger Term Quality

Provides natural trigger phrases users would say — 'process bulk requests', 'batch API calls', 'handle batch operations' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (bulk/batch API processing) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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