use-tavily

Wrap Tavily searches, URL extractions, and site mappings with preset defaults.

1|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/fdshg693/ZENN --skill use-tavily
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-tavily
Source: https://github.com/fdshg693/ZENN/tree/main/.claude/skills/use-tavily
Command: npx skills add https://github.com/fdshg693/ZENN --skill use-tavily

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tavily is powerful but can lead to inconsistent results without project-specific defaults. This skill wraps Tavily calls in a stable, opinionated layer that fixes prompts, scopes, and outputs to help teams reproduce research outcomes.

Core Features & Use Cases

  • Preset-driven research: Locks common Tavily parameters into lightweight presets for searches, extractions, and mappings.
  • Composable pipelines: Supports keyword search, URL extraction, site mapping, and multi-step pipelines from query to summarized results.
  • Safe, auditable outputs: Writes structured logs and yields outputs suitable for reproducible analysis and debugging.

Quick Start

Use this skill to run Tavily-powered research or extraction with fixed presets for reproducible results.

Frequently Asked Questions about use-tavily

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stabilize Tavily search results for reproducible research?

Stabilize Tavily search results by wrapping API interactions with project-specific presets that lock parameters, scopes, and outputs. This ensures reproducible research outcomes by enforcing a constrained interface with safe defaults.

How do I build a multi-step pipeline for keyword searches and URL extractions?

Build multi-step pipelines by chaining keyword searches, URL extractions, and site mappings into a composable workflow. This approach takes queries from initial search through to summarized results with structured outputs.

What is a preset-driven approach for Tavily API automation?

Preset-driven automation locks common Tavily parameters into lightweight configurations for searches, extractions, and mappings. This fixes prompts and scopes to prevent inconsistent results and ensure predictable behavior.

Does this approach limit Tavily API scope and cost for typical use cases?

Yes, embedding preset details and environment handling limits Tavily API scope and cost for typical use cases. Safe defaults constrain the interface to ensure predictable behavior while gathering information.

Why are my Tavily extractions yielding inconsistent outputs across different runs?

Inconsistent Tavily extractions occur without project-specific defaults. Wrapping calls in a stable, opinionated layer fixes prompts and scopes, yielding structured logs and structured outputs for reproducible analysis.