CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

exa-search

AI-powered web search via Exa with content extraction. Use when user says "exa search", "web search with content", "find similar pages", or needs broad web results beyond academic databases (arXiv, Semantic Scholar).

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/skills-codex/exa-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, largely executable skill with a clear six-step workflow and explicit error paths for its fragile steps. Main weaknesses are duplicated script-resolution logic, verbose repo-policy prose, and a pseudocode Step 6 that keeps it from fully lean/executable.

Suggestions

Collapse the wiki-script resolution chain in Step 6 by referencing the Step 2 resolution pattern once, removing the duplicated bash block.

Replace the Step 6 pseudocode with a concrete executable example for a single arXiv and a single non-arXiv hit.

Trim the Constants section to the two facts (script name, MAX_RESULTS) and move the Policy D1 / install-chain prose to the referenced integration-contract.md.

DimensionReasoningScore

Conciseness

The body is dense and mostly earns its tokens, but the script-resolution chain appears twice (Step 2 and Step 6), the not-found user message duplicates the error already emitted in the bash, and the Policy D1 prose in Constants explains repo plumbing Claude doesn't need — several spots could be tightened.

3 / 5

Actionability

Steps 2-3 give copy-paste-ready bash (pip install, key export, search/find-similar/get-contents invocations with flags) and Step 4 defines a concrete output table, but Step 6's wiki-ingest block is pseudocode ("for each research-paper hit") rather than executable code — a minor gap.

4 / 5

Workflow Clarity

Six clearly sequenced steps with explicit error handling on script resolution (error message plus fix instructions) and per-hit fallback logic in Step 6 (skip ingest and log when metadata is missing); not a 5 because there is no feedback loop for search failures (API errors, empty results).

4 / 5

Progressive Disclosure

No bundle files exist, and the two external references to shared-references/integration-contract.md are clearly signaled one-level-deep markdown links; sections are well organized, though the 15-flag argument reference and the duplicated resolution logic are inlined where a small reference file would fit — good structure with minor gaps.

4 / 5

Total

15

/

20

Passed

Description

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

A strong description that clearly and explicitly states both capability and usage triggers with concrete quoted phrases, and distinguishes itself from academic-database skills. It could list a couple more concrete actions (find-similar, filtered search) to lift specificity.

Suggestions

Add 1-2 more concrete actions (e.g., 'find pages similar to a URL', 'filter results by domain, date, or category') to raise specificity coverage.

Include one or two everyday synonyms such as 'search the web' or 'general web lookup' so users who don't name Exa still trigger it naturally.

DimensionReasoningScore

Specificity

"AI-powered web search via Exa with content extraction" names the domain and exactly two concrete actions (web search, content extraction), omitting other capabilities like find-similar and filtering — matches the anchor for domain plus 1-2 actions, not comprehensive enough for 4.

3 / 5

Completeness

Explicitly answers both: what ("AI-powered web search via Exa with content extraction") and when ("Use when user says 'exa search', 'web search with content', 'find similar pages', or needs broad web results beyond academic databases") with concrete quoted trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say — "exa search", "web search with content", "find similar pages" — plus contrast terms (arXiv, Semantic Scholar), but misses common synonyms like "search the web" or "look this up online".

4 / 5

Distinctiveness Conflict Risk

Exa-specific triggers and the explicit contrast with arXiv/Semantic Scholar carve a clear niche from sibling academic-search skills, but generic phrases like "web search" and "broad web results" carry minor overlap risk with any general web-search skill — mostly distinct, not minimal-conflict.

4 / 5

Total

16

/

20

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 — 13 / 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

relative_links

Relative link issues: 2 suspicious

Warning

Total

13

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex/exa-search/SKILL.md

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.