一键导入
tavily
Tavily web search, content extraction, and research tools.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Tavily web search, content extraction, and research tools.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
Use the diffs tool to produce real, shareable diffs (viewer URL, file artifact, or both) instead of manual edit summaries.
Maintain an Obsidian-friendly memory wiki vault with wikilinks, frontmatter, and official Obsidian CLI awareness.
Maintain the Velaclaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
| name | tavily |
| description | Tavily web search, content extraction, and research tools. |
| metadata | {"velaclaw":{"emoji":"🔍","requires":{"config":["plugins.entries.tavily.enabled"]}}} |
| Need | Tool | When |
|---|---|---|
| Quick web search | web_search | Basic queries, no special options needed |
| Search with advanced options | tavily_search | Need depth, topic, domain filters, time ranges, or AI answers |
| Extract content from URLs | tavily_extract | Have specific URLs, need their content |
Tavily powers this automatically when selected as the search provider. Use for straightforward queries where you don't need Tavily-specific options.
| Parameter | Description |
|---|---|
query | Search query string |
count | Number of results (1-20) |
Use when you need fine-grained control over search behavior.
| Parameter | Description |
|---|---|
query | Search query string (keep under 400 characters) |
search_depth | basic (default, balanced) or advanced (highest relevance, slower) |
topic | general (default), news (real-time updates), or finance |
max_results | Number of results, 1-20 (default: 5) |
include_answer | Include an AI-generated answer summary (default: false) |
time_range | Filter by recency: day, week, month, or year |
include_domains | Array of domains to restrict results to |
exclude_domains | Array of domains to exclude from results |
| Depth | Speed | Relevance | Best for |
|---|---|---|---|
basic | Faster | High | General-purpose queries (default) |
advanced | Slower | Highest | Precision, specific facts, detailed research |
include_domains to focus on trusted sources.time_range for recent information (news, current events).include_answer when you need a quick synthesized answer.Use when you have specific URLs and need their content. Handles JavaScript-rendered pages and returns clean markdown. Supports query-focused chunking for targeted extraction.
| Parameter | Description |
|---|---|
urls | Array of URLs to extract (1-20 per request) |
query | Rerank extracted chunks by relevance to this query |
extract_depth | basic (default, fast) or advanced (for JS-heavy pages, tables) |
chunks_per_source | Chunks per URL, 1-5 (requires query) |
include_images | Include image URLs in results (default: false) |
| Depth | When to use |
|---|---|
basic | Simple pages — try this first |
advanced | JS-rendered SPAs, dynamic content, tables, embedded content |
query + chunks_per_source to get only relevant content instead of full pages.basic first, fall back to advanced if content is missing or incomplete.tavily_search results already contain the snippets you need, skip the extract step.Follow this escalation pattern — start simple, escalate only when needed:
web_search — Quick lookup, no special options needed.tavily_search — Need depth control, topic filtering, domain filters, time ranges, or AI answers.tavily_extract — Have specific URLs, need their full content or targeted chunks.Combine search + extract when you need to find pages first, then get their full content.