CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/clerk-pack/skills/clerk-rate-limits/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable code throughout, but it is hurt by duplication between the body and the reference file, a monolithic structure that never signals the existing reference, and batch workflows that lack validation checkpoints.

Suggestions

Link to references/implementation-guide.md from the body (e.g. 'See [implementation-guide.md](references/implementation-guide.md) for full patterns') and keep SKILL.md as a lean overview to remove the duplicated Steps 1-5 code.

Add explicit validation checkpoints to the batch and pagination workflows — e.g. verify the returned count matches expectations and back off on 429 before continuing — so the sequence has a validate/retry feedback loop.

Deduplicate the retry/batch/cache/monitor code between SKILL.md and the reference, keeping one canonical copy and pointing to it, to respect the token budget.

DimensionReasoningScore

Conciseness

Mostly code and tables, but the body duplicates Steps 1-5 (retry, batch, cache, monitor) that reappear verbatim in references/implementation-guide.md, and includes some inline restatement, so it is not as lean as the top anchor.

2 / 3

Actionability

Every step ships executable, copy-paste-ready TypeScript with real Clerk SDK calls, plus a runnable curl example — concrete and complete rather than pseudocode.

3 / 3

Workflow Clarity

Steps are clearly sequenced, but the batch operations lack explicit validation/checkpoint steps and there is no validate-then-retry feedback loop, which the guidelines cap at 2 for batch workflows.

2 / 3

Progressive Disclosure

The body is fairly monolithic with full code inline, and the existing reference file (references/implementation-guide.md) is never linked or signaled from the body; content is duplicated rather than split into a clean overview pointing one level deep.

2 / 3

Total

9

/

12

Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-constructed: it states the capability, gives an explicit 'Use when' clause, and lists natural trigger phrases scoped to Clerk. The only mild weakness is that the named actions are broad categories rather than concrete operations.

DimensionReasoningScore

Specificity

Names the Clerk rate-limit domain and several actions ('manage Clerk rate limits and quotas', 'optimizing API usage', 'planning for high-traffic scenarios'), but the actions are general categories rather than the multiple concrete operations the top anchor lists.

2 / 3

Completeness

Explicitly answers both what ('Understand and manage Clerk rate limits and quotas') and when ('Use when hitting rate limits, optimizing API usage...') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Provides natural user phrases — 'clerk rate limit', 'clerk quota', 'clerk API limits', 'clerk throttling' — with good coverage of how a user would actually phrase the request.

3 / 3

Distinctiveness Conflict Risk

Scoped to Clerk with Clerk-specific trigger phrases, making it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.