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.
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.
Manages MongoDB Atlas Stream Processing (ASP) workflows. Handles workspace provisioning, data source/sink connections, processor lifecycle operations, debugging diagnostics, and tier sizing. Supports Kafka, Atlas clusters, S3, HTTPS, and Lambda integrations for streaming data workloads and event processing. NOT for general MongoDB queries or Atlas cluster management. Requires MongoDB MCP Server with Atlas API credentials.
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 asks to "clean gone branches", "remove deleted local branches", "prune branches removed from remote", or explicitly invokes "clean-gone-branches".
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
This skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or explicitly invokes "create-pr".