exa-hello-world

Create a minimal working Exa search example with real results. Use when starting a new Exa integration, testing your setup, or learning basic search, searchAndContents, and findSimilar patterns. Trigger with phrases like "exa hello world", "exa example", "exa quick start", "simple exa search", "first exa query".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

72%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 strong, actionable quickstart with executable code and clean organization, held back slightly by a duplicated runnable example and the absence of inline validation checkpoints. Error handling is well covered via the reference table but not woven into the workflow as explicit checkpoints.

Suggestions

Remove or condense the "Complete Runnable Script" example since it re-covers the same three operations already shown in Steps 1–4, or replace the per-step examples with the single runnable script to eliminate duplication.

Add an inline verification step such as checking that process.env.EXA_API_KEY is set before constructing the client and guarding against an empty results.results array before iterating.

Resolve the findSimilarAndContents (Step 3) vs findSimilar (runnable script) inconsistency so the demonstrated method is consistent across examples.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with useful inline comments and no concept-explaining fluff, but the "Complete Runnable Script" re-demonstrates the same search, searchAndContents, and findSimilar operations already shown in Steps 1–4, adding token-duplicative content that could be tightened.	2 / 3
Actionability	Provides fully executable TypeScript with real imports, API calls, and concrete parameters across all four operations; examples are copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	Steps 1–4 are clearly sequenced, but there are no explicit validation/verification checkpoints (e.g., confirm EXA_API_KEY is set, check for an empty results array) and a minor API inconsistency (Step 3 uses findSimilarAndContents while the runnable script uses findSimilar) could confuse.	2 / 3
Progressive Disclosure	Well-organized sections (Overview, Prerequisites, Instructions, Error Handling, Examples, Resources, Next Steps) with clearly signaled one-level-deep external doc links and no nested references; inline content is appropriate for a quickstart needing no separate files.	3 / 3
	Total	10 / 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.

The description is well-crafted: third-person voice, concrete named actions, explicit Use-when guidance, and natural trigger phrases. It clearly communicates both capability and invocation context without fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions tied to named API methods — "Create a minimal working Exa search example" and "basic search, searchAndContents, and findSimilar patterns" — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ("Create a minimal working Exa search example with real results") and when ("Use when starting a new Exa integration, testing your setup, or learning basic search...") with explicit triggers.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say — "exa hello world", "exa example", "exa quick start", "simple exa search", "first exa query" — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Exa search) with distinct Exa-prefixed triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/exa-pack/skills/exa-hello-world/SKILL.md
Commit: 8585d6d

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.