CtrlK
BlogDocsLog inGet started
Tessl Logo

exa-rate-limits

Implement Exa rate limiting, exponential backoff, and request queuing. Use when handling 429 errors, implementing retry logic, or optimizing API request throughput for Exa. Trigger with phrases like "exa rate limit", "exa throttling", "exa 429", "exa retry", "exa backoff", "exa QPS".

67

Quality

82%

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

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.

A highly actionable, code-rich skill with concrete executable patterns for Exa rate limiting. It loses points for redundancy between sections and for keeping everything inline rather than splitting advanced patterns into reference files.

Suggestions

Consolidate Step 4 (batch processing) with Step 2 (concurrency queue) or move the simpler Examples retry into Step 1 to remove overlap.

Add an explicit validation checkpoint to the batch workflow (e.g., verify partial results before proceeding to the next batch).

Move the adaptive rate limiter and advanced batching patterns into a reference file, keeping SKILL.md as a lean overview with one primary executable example.

DimensionReasoningScore

Conciseness

Mostly efficient code-first content, but Step 4 (batch processing) overlaps with Step 2 (queue) and the Examples section duplicates Step 1's backoff in a simpler form, so it could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript for backoff, queuing, adaptive limiting, and batching with concrete config values.

3 / 3

Workflow Clarity

Steps are sequenced (1-4) with a retry feedback loop in backoff, but the batch-processing workflow lacks an explicit validation/verification checkpoint, capping clarity at 2.

2 / 3

Progressive Disclosure

Single well-organized file with clear sections, but all implementations are inline with no one-level-deep reference files to offload detail into.

2 / 3

Total

9

/

12

Passed

Description

100%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.

A strong, well-targeted description that names concrete capabilities, gives explicit use-when guidance, and supplies natural trigger phrases scoped to the Exa domain. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'rate limiting, exponential backoff, and request queuing' — rather than vague language.

3 / 3

Completeness

Explicitly states both what it does (implement backoff/queuing) and when to use it ('Use when handling 429 errors, implementing retry logic...').

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would say ('exa rate limit', 'exa throttling', 'exa 429', 'exa retry', 'exa backoff', 'exa QPS').

3 / 3

Distinctiveness Conflict Risk

Exa-specific niche with distinct, brand-scoped triggers unlikely to conflict with other skills.

3 / 3

Total

12

/

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.