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 the lack of specific concrete actions—it says 'understand and manage' but doesn't enumerate what specific operations or guidance it provides. The Clerk-specific focus makes it highly distinctive.
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Check current rate limit usage, implement retry strategies with exponential backoff, configure rate limit headers, and estimate capacity for high-traffic scenarios.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Clerk rate limits and quotas) and mentions some actions like 'manage', 'optimizing API usage', and 'planning for high-traffic scenarios', but doesn't list specific concrete actions like 'check current usage', 'configure rate limit headers', or 'implement retry logic'. | 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 | Explicitly lists natural trigger terms: 'clerk rate limit', 'clerk quota', 'clerk API limits', 'clerk throttling'. These are terms users would naturally say when encountering these issues, and the coverage of variations is good. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining 'Clerk' (a specific service) with 'rate limits/quotas', making it highly unlikely to conflict with other skills. The trigger terms are all Clerk-specific. | 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 for Clerk rate limits. Its main weaknesses are moderate verbosity (particularly the dual caching implementations inline) and lack of explicit validation checkpoints in the workflow. The content would benefit from splitting detailed implementations into supporting bundle files and adding verification steps.
Suggestions
Add validation checkpoints after key steps, e.g., 'Verify retry logic by temporarily lowering batch size and confirming 429 responses are handled gracefully'
Move the detailed Redis caching implementation and monitoring code into separate bundle files (e.g., CACHING.md, MONITORING.md) and reference them from the main skill
Remove the Prerequisites and Output sections — they add little value and Claude can infer these requirements
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary sections like 'Prerequisites' (understanding traffic patterns is obvious), the 'Overview' paragraph that restates the title, and 'Output' section that just summarizes what was already shown. The caching section is quite lengthy with two full implementations (in-memory + Redis) that could be trimmed. | 2 / 3 |
Actionability | Excellent actionability with fully executable TypeScript code examples throughout, a concrete curl command for checking rate limits, specific rate limit numbers per plan, and complete implementations for retry logic, batching, caching, and monitoring. All code is copy-paste ready with proper imports. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, progressing logically from understanding limits to implementing handling, batching, caching, and monitoring. However, there are no explicit validation checkpoints — for instance, no step to verify the retry logic works, no guidance on testing the caching invalidation, and no feedback loop for confirming rate limit monitoring is properly configured. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a table of errors, but it's quite long (~150 lines of code) with no bundle files to offload detailed implementations. The caching section with both in-memory and Redis implementations could be split into a separate reference file. Resources section provides external links but no internal file references for advanced topics. | 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
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.