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".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 that excels at completeness and distinctiveness. It clearly defines the domain (Clay rate limits), provides explicit 'Use when' guidance, and includes natural trigger phrases. The main area for improvement is specificity of the concrete actions—the capabilities could be more granular about what strategies or techniques are actually covered.
Suggestions
Add more specific concrete actions such as 'implement exponential backoff, configure batch sizes, calculate optimal records-per-hour pacing' to improve specificity from domain-level to action-level detail.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Clay rate limits) and some actions (handle rate limits, webhook throttling, credit pacing strategies), but the actions are somewhat general rather than listing multiple concrete specific operations like 'implement exponential backoff, configure batch sizes, set up retry queues'. | 2 / 3 |
Completeness | Clearly answers both 'what' (handle rate limits, webhook throttling, credit pacing strategies) and 'when' (hitting 429 errors, managing webhook submission rates, optimizing throughput) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'clay rate limit', 'clay throttling', 'clay 429', 'clay slow', 'clay records per hour', '429 errors', 'webhook submission rates', and 'throughput'. These are terms users would naturally use when encountering these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused specifically on Clay platform rate limiting and throttling. The combination of 'Clay' + rate limiting/429/throttling creates very specific triggers unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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, highly actionable skill with executable TypeScript implementations and clear workflow sequencing. Its main weakness is length — the inline code for three separate classes/utilities makes it a heavy single file that could benefit from splitting into referenced modules. The content is slightly verbose in places (prerequisites, overview) but the core technical content is well-structured and specific.
Suggestions
Split the rate-limiter, backoff, and webhook-manager code into separate referenced files to improve progressive disclosure and reduce the main skill's token footprint.
Remove the Prerequisites and Overview sections — Claude doesn't need to be told what rate limits are or that it needs a Clay account.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with useful tables and code, but includes some unnecessary sections like 'Prerequisites' (Claude doesn't need to be told to have a Clay account) and the 'Overview' paragraph explains obvious concepts. The enrichment provider table and webhook manager code add bulk that could be trimmed or referenced externally. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with concrete implementations for rate limiting, backoff, and webhook management. The code is copy-paste ready with proper imports, types, and error handling. The plan limit tables give specific numbers Claude can act on. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from understanding limits → implementing rate limiting → handling 429s → managing webhook lifecycle → enrichment limits. Each step builds on the previous one, and validation is embedded in the code (checking webhook limits, hourly limits, 429 retry logic with backoff). The error handling table provides clear feedback loops. | 3 / 3 |
Progressive Disclosure | The content is quite long (~200 lines of code) and monolithic — the webhook manager, backoff utility, and enrichment provider details could be split into separate referenced files. Everything is inline in a single document with no bundle files to offload detail, though the error handling table and resources section are well-organized. | 2 / 3 |
Total | 10 / 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
3a2d27d
- 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.