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".
64
77%
Does it follow best practices?
Impact
—
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 the skill enables. The explicit trigger phrase list and clear 'Use when' clause make it effective for skill selection.
Suggestions
Replace vague verbs like 'understand and manage' with specific concrete actions such as 'diagnose rate limit errors, implement retry strategies, check quota usage, configure backoff policies'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Clerk rate limits and quotas) and mentions some actions ('understand', 'manage', 'optimizing API usage', 'planning for high-traffic scenarios'), but these are fairly general and don't list concrete specific actions like 'check current usage', 'configure rate limit headers', or 'implement retry logic'. | 2 / 3 |
Completeness | The description 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 | The description explicitly lists natural trigger terms: 'clerk rate limit', 'clerk quota', 'clerk API limits', 'clerk throttling'. These are terms users would naturally use when encountering rate limiting issues with Clerk, and the coverage of variations is good. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Clerk rate limits and quotas, which is a narrow niche unlikely to conflict with other skills. The Clerk-specific trigger terms further reduce conflict risk. | 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 (could trim prerequisites, overview, and output sections) and a workflow that presents independent techniques rather than a validated end-to-end process. The content would benefit from being split across bundle files to keep the main SKILL.md leaner.
Suggestions
Trim the Overview, Prerequisites, and Output sections — they add little value for Claude and consume tokens unnecessarily.
Add a validation/verification step after implementing retry logic (e.g., 'Test by temporarily lowering batchSize to trigger 429 and confirm backoff works').
Split the caching strategy (Step 4) and monitoring (Step 5) into separate bundle files referenced from the main SKILL.md to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient 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. The code examples themselves are well-sized but the overall document could be tightened. | 2 / 3 |
Actionability | Excellent actionability with fully executable TypeScript code examples for retry logic, batching, caching (both in-memory and Redis), and monitoring. The curl command for quick rate limit checking is a nice practical addition. All code is copy-paste ready with proper imports and realistic patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but they read more as independent techniques than a cohesive workflow. There's no explicit validation checkpoint — for instance, after implementing retry logic, there's no step to verify it works. The batch operations lack guidance on what to do if a batch partially fails. The monitoring step doesn't feed back into the retry/caching steps. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a logical progression, but it's quite long for a single SKILL.md with no bundle files. The caching strategy (in-memory + Redis) and monitoring sections could reasonably be split into separate reference files. The 'Resources' section provides external links which is good, but the inline content is heavy for an overview document. | 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
0c3a6ad
- 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.