clay-rate-limits

Handle Clay rate limits, webhook throttling, and credit pacing strategies. Use when hitting 429 errors, managing webhook submission rates, or optimizing throughput within Clay's plan limits. Trigger with phrases like "clay rate limit", "clay throttling", "clay 429", "clay slow", "clay records per hour".

Quality

90%

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 body is highly actionable with executable code and concrete tables, and steps are clearly sequenced, but it lacks validation checkpoints for batch webhook operations and keeps reference-like code inline rather than splitting it into bundle files.

Suggestions

Add explicit validation/verification checkpoints between steps for batch webhook operations (e.g., 'Verify webhook registered before submitting', 'Confirm submission count via getStats()').

Move the full rate-limiter, backoff, and webhook-manager modules into reference files under ./scripts/ and link to them, keeping only a concise snippet inline in SKILL.md.

Trim the Overview/Prerequisites prose to only what Claude does not already know about Clay's limit tiers.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete tables and code, but the full ClayRateLimiter class and some prose (Overview, Key insight) carry minor padding that could be tightened.	2 / 3
Actionability	Provides fully executable TypeScript across rate-limiter, backoff, and webhook-manager modules plus concrete plan-limit and provider tables — copy-paste ready.	3 / 3
Workflow Clarity	Five sequenced steps are clear, but batch webhook submission is a batch operation lacking explicit validation/verification checkpoints (e.g., confirm webhook registered, verify counts), which caps clarity at 2.	2 / 3
Progressive Disclosure	Well-organized single-file sections, but content is monolithic with large inline code blocks and no bundle references to split detailed material into one-level-deep files.	2 / 3
	Total	9 / 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.

The description is concise yet complete: it names concrete actions, gives explicit 'Use when' triggers, lists natural keyword phrases, and carves out a clearly distinct Clay-specific niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Handle Clay rate limits, webhook throttling, and credit pacing strategies' — naming specific capabilities rather than vague language.	3 / 3
Completeness	Clearly answers both what (handle rate limits, throttling, pacing) and when ('Use when hitting 429 errors, managing webhook submission rates, or optimizing throughput') with explicit triggers.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases ('clay rate limit', 'clay throttling', 'clay 429', 'clay slow', 'clay records per hour') are terms users would naturally say.	3 / 3
Distinctiveness Conflict Risk	Clay-specific niche with distinct trigger phrases; unlikely to fire 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
Path: plugins/saas-packs/clay-pack/skills/clay-rate-limits/SKILL.md
Commit: 4c47e33

Reviewed: 2 days 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.