CtrlK
BlogDocsLog inGet started
Tessl Logo

exa-performance-tuning

Optimize Exa API performance with search type selection, caching, and parallelization. Use when experiencing slow responses, implementing caching strategies, or optimizing request throughput for Exa integrations. Trigger with phrases like "exa performance", "optimize exa", "exa latency", "exa caching", "exa slow", "exa fast".

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

A highly actionable, token-efficient body with executable code and a clear sequenced workflow plus an error-recovery table. The main weakness is monolithic structure — all detail lives inline with no progressive disclosure into reference files.

Suggestions

Move the longer code patterns (e.g. two-phase search, caching setup) into a reference file and summarize each in SKILL.md with a one-level-deep link, improving progressive disclosure.

Add a short "Quick start" section at the top that picks the single highest-impact lever (search type selection) before the detailed step-by-step, so the overview points to the detail rather than embedding all of it.

Consider extracting the latency-by-search-type and performance-comparison tables into a reference file if the skill grows further, keeping SKILL.md as a navigable overview.

DimensionReasoningScore

Conciseness

Lean and dense with executable code and compact comparison tables; no padding or explanation of concepts Claude already knows, and inline comments earn their place (e.g. "Cache hit: 0ms vs 500-2000ms").

3 / 3

Actionability

Every step provides fully executable, copy-paste-ready TypeScript (selectSearchType, cachedSearch, parallelSearch, twoPhaseSearch, normalizeQuery) with concrete parameter values, not pseudocode.

3 / 3

Workflow Clarity

Six steps are clearly sequenced and the Error Handling table gives an issue→cause→solution feedback loop; these are non-destructive optimizations so the destructive-operation validation cap does not apply.

3 / 3

Progressive Disclosure

Well-sectioned, but the ~165-line body is monolithic with all guidance inline and no bundle/reference files to offload detail into; at this length some patterns could be split out rather than kept inline.

2 / 3

Total

11

/

12

Passed

Description

100%

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, concise description that states concrete capabilities, gives explicit "Use when" guidance with natural trigger phrases, and is tightly scoped to the Exa API. It mirrors the best reference examples in the rubric.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "search type selection, caching, and parallelization" — matching the anchor for listing several specific concrete actions; not merely naming a domain.

3 / 3

Completeness

Explicitly answers both what ("Optimize Exa API performance with...") and when ("Use when experiencing slow responses, implementing caching strategies, or optimizing request throughput") with explicit triggers.

3 / 3

Trigger Term Quality

Provides natural phrases users would actually say ("exa performance", "optimize exa", "exa latency", "exa caching", "exa slow", "exa fast"), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Clearly niched to the Exa API with distinct, Exa-scoped triggers; unlikely to fire for unrelated 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.