Perform semantic web searches via the Exa REST API.
npx skills add https://github.com/consuelohq/openengineer --skill exa-search-consuelohq
Please help me install this Agent Skill. Skill: exa-search Source: https://github.com/consuelohq/openengineer/tree/main/skills/exa-search Command: npx skills add https://github.com/consuelohq/openengineer --skill exa-search-consuelohq
Semantic web searches via Exa AI rather than Brave, enabling faster, more accurate results within MCP-enabled workflows.
Set EXA_API_KEY and run the search.sh script with your query.
High-intent search queries and answers about installing and using this skill.
Semantic web searches within MCP-enabled workflows are performed by querying the Exa AI REST API to retrieve fast, structured results across technical and research topics. This Skill uses MCP-ready endpoints to automate the search process.
Yes, you need an EXA_API_KEY to query the Exa REST API. You must set this environment variable before running the search script to authenticate and retrieve normalized search results.
Normalizing Exa AI search results requires curl and jq in your environment. Curl queries the Exa REST API, while jq processes and structures the returned JSON data for use in AI workflows.
Exa AI provides semantic search capabilities that deliver faster and more accurate results than alternatives like Brave. It is specifically useful for AI research and tech discovery workflows requiring structured data.
Yes, the Skill provides a search script that integrates Exa AI search into automated AI research scripts. It uses MCP-compatible endpoints to gather information rapidly and return structured results for downstream processing.
webdevtodayjasonSearch and download GIFs from the Tenor API using curl and jq.
BoraPerusicAutomate plan-driven research and synthesize cited reports.
AllBeingsFutureInvoke named tools on MCP servers with structured arguments.
s-hiraokuExecute Brave Search API queries and output structured JSON results.
