CtrlK
BlogDocsLog inGet started
Tessl Logo

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

72

Quality

90%

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

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 lean and highly actionable with four complete, executable code patterns and a useful error-handling table. Its main gaps are the absence of an explicit validation/retry feedback loop for the batch operation and a lack of progressive disclosure splitting the detailed patterns into reference files.

Suggestions

Add an explicit validation checkpoint to the batch lead-import pattern (e.g., inspect the rejected results and retry only the failed leads before declaring completion) so the workflow has a clear validate-then-proceed feedback loop.

Split the four code patterns into one-level-deep reference files (e.g., references/backoff.md, references/request-queue.md) and keep SKILL.md as a concise overview pointing to them, improving progressive disclosure.

Clarify in the RequestQueue example how callers obtain completion results or handle overflow, since the usage snippet fires-and-forgets without awaiting the queued promises.

DimensionReasoningScore

Conciseness

The body is lean: a brief overview, a compact rate-limit table, and four executable code blocks with minimal prose. It avoids explaining concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

It provides fully executable, copy-paste-ready TypeScript for backoff with jitter, a concurrency queue, a throttled email fetcher, and batched lead creation — specific and complete rather than pseudocode.

3 / 3

Workflow Clarity

Steps 1-4 are clearly sequenced, but the batch lead-import operation only logs success/failure counts without an explicit validation checkpoint or retry-the-failed-batch feedback loop, so per the batch-operations guideline workflow clarity is capped at 2.

2 / 3

Progressive Disclosure

Sections are well organized, but the ~230-line skill is a single monolithic file with all detailed code patterns inline and no bundle references; content that could live in one-level-deep reference files is not split out.

2 / 3

Total

10

/

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.

A strong, specific description that clearly states capabilities, when to use the skill, and natural trigger phrases. It assumes third-person voice throughout and avoids fluff.

DimensionReasoningScore

Specificity

The description names multiple concrete actions — 'rate limiting, backoff, and request throttling patterns' — matching the score-3 anchor that lists several specific capabilities rather than vague language.

3 / 3

Completeness

It states both what it does ('Implement Instantly.ai rate limiting...') and when to use it ('Use when handling 429 errors, implementing retry logic...') with explicit triggers.

3 / 3

Trigger Term Quality

It enumerates natural phrases a user would say — 'instantly rate limit', 'instantly 429', 'instantly throttle', 'instantly backoff', 'instantly retry' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

It is scoped tightly to Instantly.ai with Instantly-prefixed triggers, occupying a clear niche unlikely to conflict with other 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.