Tavily Metered Search

v1.0.1

Web search via Tavily API with built-in monthly usage tracking and quota management. Use when the user asks to search the web / look up sources / find links....

0· 100·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description claim web search + quota management; the bundled script implements Tavily API calls, monthly counting, warning/limit enforcement, and configuration exactly as described. Required env var (TAVILY_API_KEY) matches the claimed purpose.
Instruction Scope
Runtime instructions and the script operate within the skill's scope: they call https://api.tavily.com/search, read config/config.json, update data/tavily-usage.json, and optionally read ~/.openclaw/.env for TAVILY_API_KEY. Reading that .env file and writing the local usage file are expected for quota tracking, but users should be aware the script will read ~/.openclaw/.env if present.
Install Mechanism
No install spec; the skill is instruction/script-only and does not download or install external packages. This is low-risk from an installation perspective.
Credentials
Only TAVILY_API_KEY is required (declared). The script looks for it in the environment or in ~/.openclaw/.env. This is proportionate to the functionality, but users should ensure ~/.openclaw/.env does not contain other sensitive secrets they don't want read by skill code.
Persistence & Privilege
Skill does not request elevated privileges or set always:true. It writes/maintains only its own usage file under its skill data directory and does not modify other skills or global agent configuration.
Assessment
This skill appears to do what it says: it needs only a Tavily API key, will POST search requests to api.tavily.com, and will create/update data/tavily-usage.json in the skill folder to track counts. Before installing, (1) confirm you intend to give the skill a Tavily API key and that the vendor/site (tavily.com) is trustworthy; (2) prefer supplying the key via environment variable rather than placing it in ~/.openclaw/.env if that file contains other secrets; (3) note that --no-count skips local increment but still consumes Tavily quota; and (4) review network policies if you have constraints on outbound requests to third-party APIs.

Like a lobster shell, security has layers — review code before you run it.

latestvk97aew3qw8mxv9xy1jd5f8s289834jcc

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

EnvTAVILY_API_KEY

Comments