Implement Exa reference architecture for search pipelines, RAG, and content discovery. Use when designing new Exa integrations, reviewing project structure, or establishing architecture standards for neural search applications. Trigger with phrases like "exa architecture", "exa project structure", "exa RAG pipeline", "exa reference design", "exa search pipeline".
65
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./plugins/saas-packs/exa-pack/skills/exa-reference-architecture/SKILL.mdLow
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The skill’s workflow ingests outsider-authored free text at runtime by calling Exa’s search/content retrieval (e.g., `exa.searchAndContents`, `findSimilarAndContents`) and then injecting returned `r.text`/`r.highlights` into an RAG context string.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The skill calls the Exa API (api.exa.ai) at runtime (via exa.searchAndContents / findSimilarAndContents) to fetch external webpage contents (e.g., "github.com", "arxiv.org", "techcrunch.com", etc.) and then directly injects results.results[].text into the LLM context, so those remote URLs control prompts.
0540a62
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.