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".
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 well-structured skill description with strong trigger terms and clear 'when' guidance. Its main weakness is that the 'what' portion is somewhat thin — it says 'migrate' but doesn't enumerate the specific actions involved in migration (e.g., mapping parameters, converting query formats, updating endpoints). The explicit trigger phrase list is a notable strength for skill selection.
Suggestions
Add 2-3 more specific concrete actions beyond 'migrate', such as 'map query parameters', 'convert search syntax', or 'update API endpoints and authentication' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (search API migration) and the action (migrate), but doesn't list multiple concrete actions beyond 'migrate'. It doesn't describe specific steps like 'convert query syntax', 'map API parameters', 'update authentication', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (migrate from other search APIs to Exa neural search) and 'when' (switching providers, migrating pipelines, evaluating Exa as replacement) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including competitor names (Google, Bing, Tavily, Serper), action phrases ('migrate to exa', 'switch to exa', 'replace google search with exa'), and comparison terms ('exa vs tavily'). These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — specifically about migrating TO Exa FROM other search providers. The named competitors and migration-specific language make it unlikely to conflict with general Exa usage skills or general search skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong migration skill with excellent actionability — every step has executable code, and the workflow includes validation and gradual rollout. The main weakness is that the content is somewhat long for a single SKILL.md with no supporting bundle files; the adapter code and query translation logic could be split out. The error handling table and comparison function are particularly valuable additions.
Suggestions
Split the adapter layer code (Step 2) and query translation (Step 4) into separate referenced files to improve progressive disclosure and reduce SKILL.md length.
Clarify the 'Next Steps' reference — 'exa-advanced-troubleshooting' should be a concrete file path or removed if no bundle file exists.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary elements. The API comparison table is useful, but the adapter pattern code is quite lengthy. The overview paragraph is concise. The feature flag / traffic shift pattern adds value but could be tighter. Some comments in code are slightly over-explanatory. | 2 / 3 |
Actionability | Fully executable TypeScript code throughout — the adapter layer, query translation, feature flag router, and comparison function are all copy-paste ready. The error handling table maps specific issues to concrete solutions. The install step includes actual shell commands. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence from installation through validation. Step 5 provides an explicit comparison/validation function to verify migration correctness. The gradual traffic shift (0% → 10% → 50% → 100%) with a feature flag is a proper feedback loop for a migration workflow. The error handling table serves as a troubleshooting checkpoint. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a logical flow, but it's fairly long for a single file with no bundle files to offload detail into. The adapter code and query translation could be in separate referenced files. The 'Next Steps' reference to 'exa-advanced-troubleshooting' is vague and not a clear file path. | 2 / 3 |
Total | 10 / 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
a04d1a2
- 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.