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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apollo-rate-limits82
Quality
77%
Does it follow best practices?
Impact
93%
2.26xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/apollo-pack/skills/apollo-rate-limits/SKILL.mdDiscovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description with strong trigger terms and completeness. It explicitly provides both 'Use when' guidance and specific trigger phrases, making it easy for Claude to select appropriately. The main weakness is that the capability description could be more specific about the concrete actions performed (e.g., exponential backoff implementation, retry queue management).
Suggestions
Expand the capability statement to list more concrete actions like 'implement exponential backoff', 'handle 429 responses', 'configure retry queues', or 'manage request throttling'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io) and some actions (rate limiting, backoff, retry logic, request throughput), but doesn't list multiple concrete specific actions like 'implement exponential backoff', 'handle 429 responses', or 'configure request queuing'. | 2 / 3 |
Completeness | Clearly 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') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'apollo rate limit', 'apollo 429', 'apollo throttling', 'apollo backoff', 'apollo request limits'. These are specific, natural phrases a developer would use when encountering these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Apollo.io-specific triggers. The combination of 'apollo' with rate limiting terminology creates a clear niche that wouldn't conflict with generic rate limiting skills or other API-specific skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, executable code for Apollo.io rate limiting with good coverage of rate limiter, backoff, and queue patterns. However, it's somewhat verbose with all implementations inline rather than referenced, and lacks explicit workflow guidance for integrating these components or debugging rate limit issues in practice.
Suggestions
Add a quick-start section at the top showing the simplest usage pattern (e.g., just wrapping a call with withBackoff) before diving into full implementations
Include explicit workflow steps for debugging 429 errors: 1) Check headers, 2) Verify rate limiter config, 3) Monitor with RateLimitMonitor, 4) Adjust concurrency
Consider moving full class implementations to referenced files (e.g., 'See rate-limiter.ts for full implementation') and keep only usage examples in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some redundancy (e.g., the Overview section restates what the title already conveys, and some patterns overlap in functionality). The rate limit table and code are valuable, but the document could be tightened. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with complete implementations for rate limiting, backoff, and request queuing. Code is copy-paste ready with proper imports, types, and usage examples. | 3 / 3 |
Workflow Clarity | The skill presents multiple implementation patterns but lacks explicit validation checkpoints or a clear sequence for integrating these components. The error handling table is helpful but doesn't provide a step-by-step workflow for debugging rate limit issues. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the document is quite long (200+ lines) with all implementation details inline. The rate limiter, backoff, and queue implementations could be referenced as separate files rather than fully embedded. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- 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.