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 verbs ('understand', 'manage') are somewhat vague and could be replaced with more concrete actions like 'diagnose rate limit errors', 'configure retry strategies', or 'monitor quota usage'. Overall it performs well for skill selection purposes.
Suggestions
Replace vague verbs like 'understand' and 'manage' with more concrete actions such as 'diagnose rate limit errors', 'configure retry logic', or 'monitor quota consumption' to improve specificity.
| 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' are not concrete actions like 'configure', 'monitor', or 'troubleshoot'. | 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. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Clerk rate limits and quotas—the combination of 'Clerk' as a product name with 'rate limits', 'quota', and 'throttling' creates a clear niche that is unlikely to conflict with other skills. | 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 that it's somewhat verbose for a SKILL.md (could split detailed implementations into separate files) and lacks explicit validation/verification checkpoints in the workflow despite dealing with error-prone operations. The rate limit table and error handling table are valuable quick-reference additions.
Suggestions
Split detailed implementations (caching with Redis, monitoring) into separate referenced files to keep SKILL.md as a concise overview with quick-start code
Add explicit validation checkpoints, e.g., 'Test retry logic by temporarily lowering batchSize to trigger rate limits' or 'Verify cache invalidation by checking webhook delivery'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary sections like 'Prerequisites' (Claude knows what it needs), the 'Output' summary section that just restates what was already shown, and some light padding like 'Understand Clerk's rate limiting system and implement strategies to avoid hitting limits' which is redundant with the title. | 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 copy-paste ready. All code is concrete and complete. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no explicit validation checkpoints or feedback loops. For rate limit handling (which involves retry/recovery patterns), the code itself contains retry logic, but the workflow doesn't include verification steps like 'confirm your retry logic works by testing with a burst of requests' or validation that caching is functioning correctly. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a logical progression, but it's quite long (~150 lines of code) and could benefit from splitting detailed implementations (caching strategies, monitoring) into separate reference files. The Resources section provides good external links, but the inline content is heavy for a SKILL.md overview. | 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
3e83543
- 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.