exa-data-handling
Implement Exa search result processing, content extraction, caching, and RAG context management. Use when handling search results, implementing caching, building citation pipelines, or managing content payloads for LLM context windows. Trigger with phrases like "exa data", "exa results processing", "exa cache", "exa RAG context", "exa content extraction". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill exa-data-handling --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Exa Data Handling ## Overview Manage search result data from Exa's neural search API. Covers content extraction scope control (text vs highlights vs summary), result caching with TTL, citation deduplication, token budget management for LLM context windows, and structured summary extraction. ## Prerequisites - `exa-js` SDK installed and configured - Optional: `lru-cache` for in-memory caching, `i
What does the exa-data-handling skill do?
Implement Exa search result processing, content extraction, caching, and RAG context management. Use when handling search results, implementing caching, building citation pipelines, or managing content payloads for LLM context windows. Trigger with phrases like "exa data", "exa results processing", "exa cache", "exa RAG context", "exa content extraction". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill exa-data-handling --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.