CtrlK
BlogDocsLog inGet started
Tessl Logo

exa-migration-deep-dive

Migrate from other search APIs (Google, Bing, Tavily, Serper) to Exa neural search. Use when switching to Exa from another search provider, migrating search pipelines, or evaluating Exa as a replacement for traditional search APIs. Trigger with phrases like "migrate to exa", "switch to exa", "replace google search with exa", "exa vs tavily", "exa migration", "move to exa".

71

Quality

88%

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

82%Weight 40%Scale 1-5

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

The body is a tight, executable migration playbook with a clear comparison table, complete code for each step, and a troubleshooting table. The main gap is the absence of an explicit rollback/feedback loop for the risky traffic-shift step, which caps workflow clarity at 4.

Suggestions

Add an explicit validation-and-rollback checkpoint after the feature-flag traffic shift (e.g. 'if overlap rate or error rate exceeds threshold, set EXA_TRAFFIC_PERCENTAGE back to the previous value and investigate').

Wire extractDomainFilter into the adapter or query-translation flow, or remove it, so every code example shown is part of a runnable path.

Define the exaAdapter/legacyAdapter references in router.ts (or note where they come from) so the router example is self-contained.

DimensionReasoningScore

Conciseness

The body is efficient: a one-sentence overview, a compact comparison table, and code blocks whose comments carry useful API rationale rather than padding; only minor trims possible (e.g. extractDomainFilter is shown but not wired into the flow).

4 / 5

Actionability

Fully executable, copy-paste-ready TypeScript covers the common cases (install, search adapter, similarity search, traffic-shift router, query translation, result comparison), matching the top anchor.

5 / 5

Workflow Clarity

Five clearly sequenced steps with a gradual rollout (0% -> 10% -> 50% -> 100%) and a Step 5 validation/comparison checkpoint; held at 4 rather than 5 because there is no explicit validate-fix-rollback feedback loop for the risky traffic shift.

4 / 5

Progressive Disclosure

Well-sectioned headers (Overview, API Comparison, Instructions, Error Handling, Resources, Next Steps) with clearly signaled one-level references (external docs URLs and the next skill); no bundle files exist to structure, and the inline code is reasonable for a migration guide.

4 / 5

Total

17

/

20

Passed

Description

95%Weight 40%Scale 1-5

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 strong across the board: it states the concrete capability, names the specific source and target providers, gives an explicit 'Use when' clause, and lists natural trigger phrases with synonyms. Minor specificity gap is the limited action vocabulary (mainly 'migrate'/'evaluate').

DimensionReasoningScore

Specificity

Names the domain and multiple concrete specifics (Google, Bing, Tavily, Serper sources, Exa neural search target, 'evaluating Exa as a replacement') with only minor action-coverage gaps, fitting the 'lists several specific actions' anchor better than the single-action anchor 3.

4 / 5

Completeness

Explicitly answers both 'what' ('Migrate from other search APIs ... to Exa neural search') and 'when' ('Use when switching ... migrating ... evaluating ...') plus concrete trigger phrases, hitting the top anchor.

5 / 5

Trigger Term Quality

Six natural user phrases with synonyms are provided ('migrate to exa', 'switch to exa', 'replace google search with exa', 'exa vs tavily', 'exa migration', 'move to exa'), matching the comprehensive-coverage-with-synonyms anchor; file extensions are not applicable to an API skill.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (Exa migration from named providers) with distinct triggers and minimal overlap risk with unrelated skills.

5 / 5

Total

19

/

20

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.