Tavily Proxy Search

Search the web through a self-hosted TavilyProxyManager instance using Bearer master-key authentication while preserving the familiar tavily-search parameter...

Security Scan

The skill's code and instructions match its stated purpose (sending authenticated search requests to a self‑hosted TavilyProxyManager); no signs of hidden exfiltration or unrelated capabilities were found, though the registry metadata omits the required env var the skill actually needs.

Purpose & Capability

Name/description align with the included script: it POSTs a search payload to a TavilyProxyManager /search endpoint using a Bearer master key. However, the registry metadata lists no required environment variables or primary credential while SKILL.md and the script require TAVILY_PROXY_MASTER_KEY (and optionally TAVILY_PROXY_URL). This metadata omission is inconsistent but the requested secret itself is appropriate for the described purpose.

Instruction Scope

SKILL.md and the script are narrowly scoped: they read TAVILY_PROXY_MASTER_KEY and optionally TAVILY_PROXY_URL from the environment or ~/.openclaw/.env, build a JSON payload and POST it to the configured proxy URL, then return parsed results. The instructions and code do not access unrelated files, scan system state beyond the .env file, or contact any endpoints other than the configured proxy.

Install Mechanism

No install spec; this is instruction-only with a small bundled Python script. No external downloads, package installs, or archive extraction are performed by the skill.

Credentials

The skill requests a single master key (TAVILY_PROXY_MASTER_KEY), which is proportionate for authenticating to a self‑hosted proxy. The script reads ~/.openclaw/.env to find that variable (it only searches for the named variable). The inconsistency is that registry metadata did not declare this required env var; users should be aware the skill will read that environment variable and send it to the configured URL.

Persistence & Privilege

The skill does not request persistent 'always' inclusion, does not modify other skills or global agent settings, and uses normal autonomous-invocation defaults.

Assessment

This skill appears to be what it claims: a small script that forwards search requests to a TavilyProxyManager instance using a Bearer master key. Before installing, verify you trust the target proxy URL (set TAVILY_PROXY_URL explicitly to the intended host, ideally a local or otherwise controlled instance) because the skill will send your TAVILY_PROXY_MASTER_KEY to that endpoint. Note the registry metadata omitted the required environment variable—you must set TAVILY_PROXY_MASTER_KEY (via env or ~/.openclaw/.env). If you have concerns, review the included scripts (they are short and readable) and avoid using a high‑privilege/production master key unless necessary.

Use the bundled script to search the web through an existing TavilyProxyManager /search endpoint.

This skill does not deploy TavilyProxyManager. It only sends authenticated search requests to a TavilyProxyManager instance that is already running. Project: https://github.com/xuncv/TavilyProxyManager

Requirements

Provide credentials via either:

• environment variable: TAVILY_PROXY_MASTER_KEY
• ~/.openclaw/.env line: TAVILY_PROXY_MASTER_KEY=...

Optional:

• environment variable: TAVILY_PROXY_URL
• ~/.openclaw/.env line: TAVILY_PROXY_URL=...
• default URL: http://127.0.0.1:8080/search

Minimal example:

export TAVILY_PROXY_URL="http://127.0.0.1:8080/search"
export TAVILY_PROXY_MASTER_KEY="your-master-key"

Commands

Run from the OpenClaw workspace:

# raw JSON (default)
python3 {baseDir}/scripts/tavily_proxy_search.py --query "..." --max-results 5

# include short answer (if available)
python3 {baseDir}/scripts/tavily_proxy_search.py --query "..." --max-results 5 --include-answer

# stable schema (closer to web_search): {query, results:[{title,url,snippet}], answer?}
python3 {baseDir}/scripts/tavily_proxy_search.py --query "..." --max-results 5 --format brave

# human-readable Markdown list
python3 {baseDir}/scripts/tavily_proxy_search.py --query "..." --max-results 5 --format md

Output

raw (default)

• JSON: query, optional answer, results: [{title,url,content}]

brave

• JSON: query, optional answer, results: [{title,url,snippet}]

md

• A compact Markdown list with title/url/snippet.

Common failures

• Missing TAVILY_PROXY_MASTER_KEY

  • Cause: the proxy master key is not configured.
  • Fix: set TAVILY_PROXY_MASTER_KEY in the environment or ~/.openclaw/.env.

• Tavily proxy returned HTTP 401

  • Cause: the Bearer master key is wrong, expired, or the endpoint expects a different auth setup.
  • Fix: verify the master key and confirm the target really is a TavilyProxyManager /search endpoint.

• Tavily proxy request failed

  • Cause: the proxy URL is unreachable, refused, timed out, or DNS failed.
  • Fix: verify TAVILY_PROXY_URL, container status, reverse proxy, and network reachability.

• Tavily proxy returned non-JSON

  • Cause: the configured URL is not the correct /search API endpoint, or an upstream proxy returned HTML/error text.
  • Fix: point TAVILY_PROXY_URL to the real TavilyProxyManager /search endpoint.

Notes

• Keep max-results small by default (3–5) to reduce token and reading load.
• Authentication is handled with Authorization: Bearer <TAVILY_PROXY_MASTER_KEY>.
• Do not send TAVILY_API_KEY in the JSON body for this skill.
• Preserve the familiar parameter style: --query, --max-results, --include-answer, --search-depth, --format.
• advanced search depth depends on the capabilities of the deployed TavilyProxyManager instance and its upstream search configuration.