exa-web-search
Exa.ai semantic web search: neural search, crawl, contents extraction, highlights, date filtering
What this skill does
# exa-web-search
## Purpose
This skill enables semantic web searches using Exa.ai's neural engine, allowing for advanced querying, web crawling, content extraction, highlighting key sections, and date-based filtering. It's designed for AI agents to fetch and process web data efficiently in tasks requiring real-time or historical information retrieval.
## When to Use
Use this skill when you need to perform semantic searches beyond keyword matching, such as analyzing trends from recent articles, extracting data from crawled pages, or highlighting relevant content. Apply it in research tasks, content aggregation, or when integrating web data into AI workflows, especially if other search tools fail to capture contextual nuances.
## Key Capabilities
- Semantic search using neural networks for understanding query intent.
- Web crawling to fetch pages dynamically based on queries.
- Content extraction to pull text, images, or metadata from pages.
- Highlighting of key phrases or sections in results.
- Date filtering to limit results to a specific range, e.g., last 7 days.
- Supports pagination and result limits for scalable queries.
## Usage Patterns
Always initialize with authentication via environment variables. For CLI, run searches in a loop for batch processing. In code, use asynchronous API calls to avoid blocking. Structure queries with specific flags for precision, and parse responses to extract highlights or metadata. Test with small limits first to verify results.
## Common Commands/API
Exa.ai uses a CLI tool and REST API. Set your API key in `$EXA_API_KEY` before use.
CLI Commands:
- Basic search: `exa search --query "AI advancements" --limit 5 --date-after "2023-01-01"`
Example snippet:
```
result = subprocess.run(['exa', 'search', '--query', 'climate change'], capture_output=True)
print(result.stdout)
```
- With crawling and extraction: `exa search --query "open source tools" --crawl-depth 2 --extract-content`
Snippet:
```
import subprocess
output = subprocess.check_output(['exa', 'search', '--query', 'web frameworks', '--highlight'])
```
API Endpoints:
- Primary endpoint: `POST https://api.exa.ai/v1/search`
Request body format (JSON):
```
{
"query": "machine learning",
"limit": 10,
"date_after": "2022-01-01",
"crawl_depth": 1
}
```
Snippet:
```
import requests
headers = {'Authorization': f'Bearer {os.environ.get("EXA_API_KEY")}'}
response = requests.post('https://api.exa.ai/v1/search', headers=headers, json={"query": "neural networks"})
data = response.json()
```
- Error checking endpoint: `GET https://api.exa.ai/v1/status` to verify service availability.
Config Formats:
- Use a `.exa-config.json` file for persistent settings:
```
{
"default_limit": 20,
"api_endpoint": "https://api.exa.ai/v1/search"
}
```
Load it in code: `with open('.exa-config.json') as f: config = json.load(f)`
## Integration Notes
Integrate by setting `$EXA_API_KEY` in your environment or passing it via headers. For AI agents, wrap API calls in try-except blocks and use async libraries like `aiohttp` for non-blocking operations. Combine with other skills by piping results, e.g., feed search outputs to a summarization tool. Ensure rate limits (e.g., 100 requests/min) are respected by adding delays. For clustering, reference the 'community' tag to link with related skills.
## Error Handling
Check HTTP status codes in API responses (e.g., 401 for unauthorized, access via `response.status_code`). For CLI, parse stderr for messages like "Query exceeded limits". Common errors include invalid queries (fix by validating input strings) or network issues (retry with exponential backoff). In code, use:
```
if response.status_code != 200:
raise Exception(f"API error: {response.json().get('error')}")
```
Log errors with details like error codes and retry up to 3 times for transient failures.
## Graph Relationships
- Related to: search skills (e.g., general web search tools)
- Depends on: authentication services for API access
- Complements: data extraction skills for post-processing results
- Clusters with: community tools for semantic analysis
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.