instantly-rate-limits
Implement Instantly.ai rate limiting, backoff, and request throttling patterns. Use when handling 429 errors, implementing retry logic, or building high-throughput Instantly integrations. Trigger with phrases like "instantly rate limit", "instantly 429", "instantly throttle", "instantly backoff", "instantly retry".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a well-crafted skill description that clearly defines its scope around Instantly.ai rate limiting patterns. It excels in all dimensions by providing specific actions, natural trigger terms, explicit 'Use when' and 'Trigger with' clauses, and a distinctive niche. The description is concise yet comprehensive, following the third-person voice convention correctly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: rate limiting, backoff, request throttling patterns, handling 429 errors, implementing retry logic, and building high-throughput integrations. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement rate limiting, backoff, and request throttling patterns for Instantly.ai) and 'when' (handling 429 errors, implementing retry logic, building high-throughput integrations) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'instantly rate limit', 'instantly 429', 'instantly throttle', 'instantly backoff', 'instantly retry'. These are realistic phrases a developer would use when encountering these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by targeting a specific platform (Instantly.ai) combined with specific technical patterns (rate limiting, 429 errors). The 'instantly' prefix on all trigger terms creates a clear niche unlikely to conflict with generic rate-limiting skills. | 3 / 3 |
Total | 12 / 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 is a solid, actionable skill with executable TypeScript implementations covering the key rate limiting patterns for Instantly.ai. Its main strengths are concrete, copy-paste-ready code and a well-organized error handling reference table. Weaknesses include being somewhat long for a SKILL.md (could split detailed class implementations into separate files) and lacking explicit validation/verification checkpoints within the batch operation workflow.
Suggestions
Split the full class implementations (RequestQueue, ThrottledEmailFetcher) into a referenced file and keep only usage examples and key patterns in SKILL.md to improve progressive disclosure.
Add explicit validation checkpoints to the batch operations pattern, such as verifying lead count after import or checking for partial failures before proceeding.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code, but some sections are slightly verbose — the Prerequisites mentioning 'Understanding of exponential backoff patterns' is unnecessary for Claude, and some inline comments explain obvious things. The code itself is well-structured but could be tighter in places. | 2 / 3 |
Actionability | Fully executable TypeScript code with concrete implementations for backoff, request queuing, throttled fetching, and batch operations. Code is copy-paste ready with realistic usage examples and sensible defaults. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and build on each other logically. However, for batch operations (Step 4) and the queue pattern, there are no explicit validation checkpoints or feedback loops for error recovery beyond logging counts. The error handling table helps but doesn't integrate into the workflow steps themselves. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a table of contents-like flow, but the skill is quite long (~180 lines of code) and could benefit from splitting detailed implementations (e.g., RequestQueue, ThrottledEmailFetcher) into separate reference files while keeping the SKILL.md as an overview with key patterns. | 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 | |
- Commit
c8a915c
- 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.