clay-rate-limits
Implement Clay rate limiting, backoff, and idempotency patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Clay. Trigger with phrases like "clay rate limit", "clay throttling", "clay 429", "clay retry", "clay backoff".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-rate-limits84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 excels across all dimensions. It uses third person voice correctly, provides specific capabilities, includes explicit 'Use when' guidance, and lists natural trigger phrases that are both specific to Clay and cover common user terminology like '429' errors. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'rate limiting', 'backoff', and 'idempotency patterns'. These are distinct, technical capabilities that clearly describe what the skill does. | 3 / 3 |
Completeness | Clearly answers both what ('Implement Clay rate limiting, backoff, and idempotency patterns') and when ('Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput') with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'clay rate limit', 'clay throttling', 'clay 429', 'clay retry', 'clay backoff' - these are terms users would naturally use when encountering these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Clay-specific triggers and the combination of rate limiting + backoff + idempotency creates a clear niche. The explicit 'clay' prefix on all trigger terms prevents conflicts with generic rate limiting skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable code examples for Clay rate limiting with good organization and progressive structure. The main weaknesses are some unnecessary explanatory content (prerequisites, output section) and missing validation checkpoints in the workflow for confirming successful retry behavior or handling edge cases in rate limit recovery.
Suggestions
Remove the 'Prerequisites' and 'Output' sections - Claude already understands async/await and the outcomes are self-evident from the code
Add explicit validation step after retries succeed, e.g., 'Verify response status before processing' or logging successful recovery
Consider moving the rate limit tier table to a separate reference file or adding a note that these values should be verified against current Clay documentation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is mostly efficient with good code examples, but includes some unnecessary elements like the 'Prerequisites' section (Claude knows async/await) and the 'Output' section which states obvious outcomes. The rate limit tier table may be time-sensitive information that could become outdated. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with complete implementations for exponential backoff, idempotency keys, queue-based limiting, and rate limit monitoring. All examples are copy-paste ready with proper imports and type annotations. | 3 / 3 |
Workflow Clarity | Steps are numbered but lack explicit validation checkpoints. For retry logic involving API calls, there's no guidance on verifying successful retries or handling partial failures. The workflow doesn't include a feedback loop for confirming rate limit recovery. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from understanding to implementation to examples. External resources are linked at the end, and cross-references to related skills (clay-security-basics) are appropriately signaled. Content is appropriately sized for a single file. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.