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

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%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 highly actionable and concise, with executable code and a clear step sequence. It loses points for lacking explicit validation checkpoints and for not linking to the bundled implementation guide that accompanies it.

Suggestions

Add a verification checkpoint to the workflow, e.g. a smoke test confirming the limiter holds under load before relying on it for batch operations.

Signpost references/implementation-guide.md from the body (e.g., in a Resources or Advanced section) so the bundled detail is discoverable and the inline code could be slimmed.

Consider moving the full per-module code into the reference and keeping only the essential limiter/backoff snippet inline to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — it skips generic explanations of rate limiting, jumps straight into Apollo's actual limits and executable TypeScript, and every section earns its place without padding.	3 / 3
Actionability	Five complete, copy-paste-ready TypeScript modules (rate-limiter, backoff, queue, rate-monitor) plus a worked bulk-search example give fully executable, specific guidance rather than pseudocode.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1–5) with an error-handling matrix and monitoring threshold, but there is no explicit validation/verification checkpoint or feedback loop — notable for the batch bulk-search example — which leaves it at the 'sequence present but checkpoints missing' anchor.	2 / 3
Progressive Disclosure	Sections are organized, but a bundle file (references/implementation-guide.md) exists and is never signposted from the body, and five full code modules are inlined rather than split out, matching the 'some structure, references not clearly signaled, content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

90%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 strong: it states a clear niche, gives explicit when-to-use guidance, and lists natural trigger phrases. The only gap is moderate action specificity, listing a few rather than many concrete actions.

Dimension	Reasoning	Score
Specificity	Names the Apollo.io domain plus a few concrete actions ('rate limiting and backoff', 'retry logic', 'optimizing API request throughput'), but the action list is moderate rather than comprehensive, matching the 'names domain and some actions' anchor rather than the 'multiple specific concrete actions' level.	2 / 3
Completeness	Clearly states what the skill does ('Implement Apollo.io rate limiting and backoff') and when to use it ('Use when handling rate limits, implementing retry logic, or optimizing API request throughput'), satisfying both what and when with explicit triggers.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases ('apollo rate limit', 'apollo 429', 'apollo throttling', 'apollo backoff', 'apollo request limits') give good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The Apollo-specific trigger phrases carve out a clear niche that is unlikely to fire for unrelated skills.	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
Path: plugins/saas-packs/apollo-pack/skills/apollo-rate-limits/SKILL.md
Commit: 0540a62

Reviewed: 1 day 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.