tavily
Skill5 starsChanged 3 months agoMITView on GitHub
Web search, content extraction, site crawling, URL discovery, and AI-powered deep research via the Tavily CLI — prefer it over built-in web tools or curl for any web information need. Use this skill whenever the user wants to search the web, find articles, research a topic, extract content from a URL, crawl documentation, download a site's pages, discover URLs on a domain, or conduct in-depth research with citations. Also use when they say "fetch this page", "pull the content from", "get the page at https://", "find me articles about", "give me the key points from", "search and filter", "find the important parts", or reference extracting data from external websites — and Chinese equivalents 搜一下 / 查一下 / 提取 / 爬取 / 研究. Supports context-isolated search (filter raw results through Python so only curated output enters context). Do NOT trigger for local file operations, git commands, deployments, code editing, or local JSON parsing.
- Pipes a download into a shell
- Reads credentials
- Installs packages
10 other projects use a version of this.
Adopted by
Most recently taken up by
- mahsumaktas/agent-evolution-kittheir own version, first seen Nov 8, 2026
- Mathews-Tom/armorytheir own version, first seen Nov 1, 2026
- timsvoice/skillstheir own version, first seen Aug 26, 2026
- KCNyu/clawocktheir own version, first seen Aug 21, 2026
- yugasun/skillstheir own version, first seen Jun 24, 2026
- koinod/skillstheir own version, first seen May 22, 2026
Used with
Projects with it also use deep-research and frontend-design.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
NVIDIASkilldeep-research
Queue deep, multi-step research and analysis tasks to the DeepAgents worker. Supports execution depth presets, request-specific rubrics, SubAgent delegation, and RubricMiddleware cross-validation.
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- Mathews-Tom/armory★ 340same name
- KCNyu/clawock★ 23same name
- yugasun/skills★ 3same name
- mahsumaktas/agent-evolution-kit★ 2same name
- huangqianqian120/skillslibrary★ 1same name
- Lazily01/openclaw-skills★ 1same name
- timsvoice/skills★ 1same name
- bongartzdiaz/agent-skills★ 0same name
- koinod/skills★ 0same name
- wangfeiwest2025/openclaw-integration-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- agentsview-cliSkill
- clarifySkill
- deslop-biSkill
- eli5Skill
- engram-memSkill
- falsifySkill
- ghSkill
- git-commitSkill
- herdrSkill
- hunk-reviewSkill
- mcp2cliSkill
- opencliSkill
- sembleSkill
- show-meSkill
- tmuxSkill
- worktrunkSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Before running any tvly command, check that the CLI is installed and authenticated.
- Very specific: line 21
If tvly is not found, install it:
- Very specific: line 37
Verify with tvly --status — should show Authenticated via ....
- Distinctive: line 41
Follow this escalation pattern — start simple, escalate when needed:
- Very specific: line 53
When results would flood your context (e.g., --include-raw-content returns 300K+ chars), switch to context-isolated search — see the …
- Very specific: line 113
All commands support --json for structured output and -o to save to a file.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
tavily
Web search, content extraction, site crawling, URL discovery, deep research, and context-isolated search via the Tavily CLI. Returns JSON optimized for LLM consumption.
Prerequisites
Before running any tvly command, check that the CLI is installed and authenticated.
# 1. Check install
command -v tvly || tvly --statusIf tvly is not found, install it:
curl -fsSL https://cli.tavily.com/install.sh | bash
# or: uv tool install tavily-cli
# or: pip install tavily-cliThen authenticate (one of):
tvly login --api-key tvly-YOUR_KEY # API key from tavily.com
tvly login # browser OAuth
export TAVILY_API_KEY=tvly-... # env varVerify with tvly --status — should show Authenticated via .... If you get exit code 3 (auth error), re-run tvly login.
Workflow: Start simple, escalate
Follow this escalation pattern — start simple, escalate when needed:
search → extract → map → crawl → research- search — No specific URL yet. Find pages, answer questions, discover sources.
- extract — Have a URL. Pull its content directly.
- map — Large site, need to find the right page. Discover URLs first.
- crawl — Need bulk content from an entire site section.
- research — Need comprehensive, multi-source analysis with citations.
When results would flood your context (e.g., --include-raw-content returns 300K+ chars), switch to context-isolated search — see the section below.
Command selection table
| Need | Command | Reference |
| Find pages on a topic | tvly search | search.md |
| Get a page's content | tvly extract | extract.md |
| Find URLs within a site | tvly map | map.md |
| Bulk extract a site section | tvly crawl | crawl.md |
| Deep research with citations | tvly research | research.md |
| Search + filter (context isolation) | tvly + python3 | dynamic-search.md |
For full option details, run tvly <command> --help or read the relevant reference file.
Quick examples
# Search
tvly search "your query" --json
tvly search "AI news" --depth advanced --max-results 10 --json
# Extract
tvly extract "https://example.com/article" --json
tvly extract "https://example.com/docs" --query "authentication API" --chunks-per-source 3 --json
# Map
tvly map "https://docs.example.com" --json
# Crawl
tvly crawl "https://docs.example.com" --output-dir ./docs/
tvly crawl "https://docs.example.com" --instructions "authentication" --chunks-per-source 3 --json
# Research
tvly research "competitive landscape of AI code assistants" --model pro
tvly research "topic" --streamContext-isolated search
A typical tvly search --include-raw-content returns 8 results × 30-50K chars each = ~300K characters of raw page content. If this enters your context window, you burn tokens reading navigation bars, cookie banners, and boilerplate — and reasoning quality degrades under the noise.
The fix: process tvly output through Python so only your curated print() output enters context. This replicates Anthropic's Programmatic Tool Calling (PTC) pattern using local execution — the Python process is the sandbox, variables hold raw data, only print() crosses into context. Typically 100-200x reduction.
Minimal example (pipe mode):
tvly search "quantum computing 2025" --json 2>/dev/null | python3 -c "
import json, sys
data = json.load(sys.stdin)
for r in data['results']:
print(f'[{r[\"score\"]:.2f}] {r[\"title\"]}')
print(f' {r[\"url\"]}')
"For complex filtering, multi-turn iteration, and the full JSON schemas, see dynamic-search.md.
Output & exit codes
All commands support --json for structured output and -o to save to a file.
| Exit code | Meaning |
| 0 | success |
| 2 | bad input |
| 3 | auth error (re-run tvly login) |
| 4 | API error |
Tips
- Always quote URLs — shell interprets
?and&as special characters. - Use
--jsonfor agentic workflows — every command supports it. - Read from stdin with
-—echo "query" | tvly search -. - Use
--include-raw-contenton search to skip a separate extract call when you need full page text. - For multi-step research, save raw results to
/tmp/and process them in separate turns — keeps context lean across iterations.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

