apollo-rate-limits

Implement Apollo.io rate limiting and backoff. Use when handling rate limits, implementing retry logic, or optimizing API request throughput. Trigger with phrases like "apollo rate limit", "apollo 429", "apollo throttling", "apollo backoff", "apollo request limits".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with executable, copy-paste-ready code and a clear step sequence, but it inlines all implementations rather than leveraging the existing reference file and lacks explicit validation feedback loops for the batch API operations it covers.

Suggestions

Signal the existing references/implementation-guide.md from the body and move the full TypeScript module implementations there, keeping SKILL.md as a concise overview with one representative example.

Add an explicit validation checkpoint in the workflow (e.g., verify x-rate-limit-remaining after a batch run and halt/retry when usage exceeds 80%) to create a validate→fix→retry feedback loop for the batch operations.

Tighten the rate-limit table and header list in SKILL.md to the essential per-endpoint limits, offloading the full reference table to the implementation guide.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but inlines five complete TypeScript modules (~140 lines of code) plus a rate-limit table and header list directly in SKILL.md, so it could be tightened by moving full implementations to the reference.	2 / 3
Actionability	Provides fully executable TypeScript — SlidingWindowLimiter, withBackoff, queuedRequest, attachRateMonitor, and a complete bulk-search example — with specific library configs and header names, copy-paste ready.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1–5) with an error-handling table, but there are no explicit validation checkpoints or validate→fix→retry feedback loops; per the batch-operations guideline this caps the score at 2.	2 / 3
Progressive Disclosure	A references/implementation-guide.md bundle exists but the body never signals or links to it, while all code modules are inlined in SKILL.md — content that should be split into the reference is inline.	2 / 3
	Total	9 / 12 Passed

Description

100%

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, specific, and complete — it states concrete capabilities, gives an explicit 'Use when' trigger, and lists natural keyword phrases. It is well-distinguished from generic rate-limiting or API skills.

Dimension	Reasoning	Score
Specificity	Names the Apollo.io domain plus multiple concrete actions — 'Implement Apollo.io rate limiting and backoff', 'implementing retry logic', 'optimizing API request throughput' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what ('Implement Apollo.io rate limiting and backoff') and when ('Use when handling rate limits, implementing retry logic, or optimizing API request throughput'), matching the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say — 'apollo rate limit', 'apollo 429', 'apollo throttling', 'apollo backoff', 'apollo request limits' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Apollo.io-specific niche with distinct, prefixed triggers ('apollo 429', 'apollo backoff'), making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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: 02d6341

Reviewed: 5 days 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.