tavily-usage
The tavily-usage skill enables web search and content extraction through Tavily MCP tools. Use tavily_search for keyword-based discovery across multiple sources and tavily_extract for retrieving detailed content from specific URLs. This skill applies when users request web searches, URL content fetching, website scraping, or information retrieval from links, following a discovery-then-extraction workflow to optimize API costs.
git clone --depth 1 https://github.com/fcakyon/claude-codex-settings /tmp/tavily-usage && cp -r /tmp/tavily-usage/plugins/tavily-tools/skills/tavily-usage ~/.claude/skills/tavily-usageSKILL.md
# Tavily Search and Extract Use Tavily MCP tools for web search and content retrieval operations. ## Tool Selection ### Tavily Search (`mcp__tavily__tavily_search`) Use for: - Keyword-based searches across the web - Finding relevant pages and content - Quick answer gathering - Multiple result discovery **Best for**: Initial research, finding sources, broad queries ### Tavily Extract (`mcp__tavily__tavily-extract`) Use for: - Getting detailed content from specific URLs - Deep analysis of page content - Structured data extraction - Following up on search results **Best for**: In-depth analysis, specific URL content, detailed information ## Hook Behavior `tavily_extract_to_advanced.py` hook automatically upgrades extract calls to advanced mode for better accuracy when needed. ## Integration Pattern 1. Use `mcp__tavily__tavily_search` for discovery phase 2. Analyze results to find relevant URLs 3. Use `mcp__tavily__tavily-extract` for detailed content on specific URLs 4. Process extracted content for user needs ## Environment Variables Tavily MCP requires: - `TAVILY_API_KEY` - API key from Tavily (tvly-...) Configure in shell before using the plugin. ## Cost Considerations - Search is cheaper than extract - Use search to filter relevant URLs first - Only extract URLs that are likely relevant - Cache results when possible
Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
This skill should be used when user asks to "query Azure resources", "list storage accounts", "manage Key Vault secrets", "work with Cosmos DB", "check AKS clusters", "use Azure MCP", or interact with any Azure service.
This skill should be used when user encounters "Tavily MCP error", "Tavily API key invalid", "web search not working", "Tavily failed", or needs help configuring Tavily integration.