clerk-rate-limits
Understand and manage Clerk rate limits and quotas. Use when hitting rate limits, optimizing API usage, or planning for high-traffic scenarios. Trigger with phrases like "clerk rate limit", "clerk quota", "clerk API limits", "clerk throttling".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clerk-pack/skills/clerk-rate-limits/SKILL.mdQuality
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 solid skill description with excellent trigger terms and completeness. Its main weakness is that the capability actions are somewhat vague ('understand and manage') rather than listing specific concrete actions like checking current usage, configuring limits, or troubleshooting throttling errors. Overall it would perform well in skill selection scenarios.
Suggestions
Replace vague verbs like 'understand and manage' with specific concrete actions such as 'check current rate limit status, diagnose throttling errors, configure retry strategies, and plan capacity for high-traffic scenarios'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clerk rate limits and quotas) and some actions ('understand', 'manage', 'optimizing API usage', 'planning for high-traffic scenarios'), but the actions are somewhat vague—'understand and manage' doesn't list concrete specific actions like 'configure rate limit thresholds' or 'monitor quota usage'. | 2 / 3 |
Completeness | Clearly answers both 'what' (understand and manage Clerk rate limits and quotas) and 'when' (hitting rate limits, optimizing API usage, planning for high-traffic scenarios) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger terms: 'clerk rate limit', 'clerk quota', 'clerk API limits', 'clerk throttling'. These are terms users would naturally say when encountering rate limiting issues with Clerk, and the variations provide good coverage. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche—Clerk rate limits and quotas—with distinct trigger terms that include the product name 'Clerk'. Unlikely to conflict with generic rate limiting skills or other Clerk-related skills focused on different features. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%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, actionable skill with excellent executable code examples covering retry logic, batching, caching, and monitoring. Its main weaknesses are verbosity (could trim some sections and split detailed implementations into referenced files) and lack of explicit validation checkpoints within the workflow steps. The rate limit table and error handling table are valuable additions.
Suggestions
Move the Redis caching implementation and monitoring code to a separate referenced file (e.g., CLERK-RATE-LIMIT-ADVANCED.md) to keep the main skill focused on the core retry and batching patterns.
Add explicit validation steps, such as 'Verify retry logic works by temporarily lowering batchSize and confirming 429 responses are handled' or a test snippet that simulates rate limiting.
Remove the Prerequisites and Output sections—they add little value and Claude can infer these from context.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary sections like 'Prerequisites' (understanding traffic patterns, monitoring infrastructure) and the 'Overview' paragraph that restates the title. The 'Output' section is also somewhat redundant as it just summarizes what was already shown. | 2 / 3 |
Actionability | Fully executable TypeScript code examples throughout, including retry logic, batching, caching (both in-memory and Redis), and monitoring. The curl command for quick rate limit checking is a nice copy-paste-ready addition. All code is complete and runnable. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no explicit validation checkpoints or feedback loops. For example, after implementing retry logic there's no step to verify it works, and the batch operations don't include validation that all items were processed successfully. The error handling table is helpful but separate from the workflow. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's quite long with all code inline. The caching section alone has two full implementations (in-memory and Redis) that could be referenced externally. The Resources section provides good external links, but the skill itself could benefit from splitting detailed implementations into separate files. | 2 / 3 |
Total | 9 / 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
3076d78
- 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.