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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

A well-organized, highly actionable skill body with complete executable code patterns and a useful error-handling table. Its weaknesses are the absence of explicit validation/feedback loops for batch operations and the monolithic inline structure with no progressive file separation.

Suggestions

Add an explicit validation/verification step after batch operations (e.g., reconcile failed counts, optionally retry rejected leads, and confirm totals before proceeding) so Step 4 has a feedback loop.

Split the larger code patterns (e.g., RequestQueue and ThrottledEmailFetcher) into a referenced file under scripts/ or references/ and keep SKILL.md as an overview pointing to them, improving progressive disclosure.

Resolve the inline '// Parse Retry-After header if available' comment in withBackoff — the code does not actually parse Retry-After — either implement it or remove the misleading comment.

Dimension	Reasoning	Score
Conciseness	Lean and code-first; it does not explain concepts Claude already knows (delegating backoff understanding to a prerequisite) and jumps straight to executable patterns, so each token earns its place.	3 / 3
Actionability	Provides complete, copy-paste-ready TypeScript implementations (withBackoff, RequestQueue, ThrottledEmailFetcher, addLeadsBatched) with concrete parameters and usage examples.	3 / 3
Workflow Clarity	Steps are clearly numbered (Step 1–4), but the batch operation in Step 4 and lead-import flow lack an explicit validation/verification checkpoint or feedback loop, capping clarity at 2 per the batch-operations guideline.	2 / 3
Progressive Disclosure	Well-organized sections and clearly signaled external/sibling references, but everything is inline in a ~200-line SKILL.md with no content split into reference files, so it is monolithic rather than appropriately partitioned.	2 / 3
	Total	10 / 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.

A strong, third-person description that clearly states the capability, the triggering situations, and concrete trigger phrases. It avoids vague fluff and over-claims while remaining concise.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'rate limiting, backoff, and request throttling patterns' — rather than vague language, matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers both what ('Implement Instantly.ai rate limiting, backoff, and request throttling patterns') and when ('Use when handling 429 errors...'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Natural trigger phrases a user would actually say ('instantly rate limit', 'instantly 429', 'instantly throttle', 'instantly backoff', 'instantly retry') give broad coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Instantly.ai-specific niche and distinctive triggers make it unlikely to activate 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: 1628598

Reviewed: about 8 hours 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.