playbooks

home / skills / fcakyon / claude-codex-settings / setup

setup skill

/plugins/tavily-tools/skills/setup

This skill helps you diagnose Tavily MCP errors and configure Tavily integration to restore API access and project connectivity.

npx playbooks add skill fcakyon/claude-codex-settings --skill setup

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
577 B
---
name: setup
description: 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.
---

# Tavily Tools Setup

Run `/tavily-tools:setup` to configure Tavily MCP.

## Quick Fixes

- **API key invalid** - Get new key from app.tavily.com (format: `tvly-...`)
- **Quota exceeded** - Free tier is 1,000 searches/month
- **Connection failed** - Restart Claude Code after config changes

## Don't Need Tavily?

Disable via `/mcp` command to prevent errors.

Overview

This skill configures and troubleshoots the Tavily integration used by my MCP/agent setup. It provides quick fixes for common Tavily errors, guides API key setup, and offers simple commands to enable, disable, or reset the integration. Use it to restore web search, fix authentication, and keep the agent's Tavily connection healthy.

How this skill works

The setup skill runs the Tavily MCP configuration flow and validates the Tavily API key and connection. It detects common failure modes (invalid key, quota issues, connection errors) and suggests exact remediation steps. It also exposes commands to disable Tavily when you want to avoid related errors or to restart the agent after config changes.

When to use it

  • You see “Tavily MCP error” in logs or UI.
  • You receive “Tavily API key invalid” or authentication failures.
  • Web search or external lookups stop working for the agent.
  • Tavily returns quota or connection/failure messages.
  • You want to disable Tavily to prevent recurring errors while debugging.

Best practices

  • Obtain a valid Tavily API key from app.tavily.com; keys start with tvly- and must be current.
  • Check free-tier quota (1,000 searches/month) before blaming connectivity.
  • After updating keys or settings, restart the agent (Claude Code) to apply changes.
  • If you don’t need Tavily, disable it via the MCP command to avoid errors.
  • Log and save timestamps of failures to correlate with quota or key rotations.

Example use cases

  • Fixing an authentication failure by replacing an expired Tavily API key with a new tvly-... key.
  • Troubleshooting why web search stopped returning results by checking quota and restarting the MCP agent.
  • Temporarily disabling Tavily during diagnostics to confirm whether errors originate from the integration.
  • Running /tavily-tools:setup after a configuration change to revalidate settings and restore connectivity.
  • Responding to a quota exceeded alert by upgrading or limiting automated searches until next billing cycle.

FAQ

How do I get a valid Tavily API key?

Log in to app.tavily.com and create or copy your API key; valid keys use the tvly- prefix.

What if I hit quota limits?

Free tier allows 1,000 searches/month. Reduce automated searches or upgrade your plan to restore full functionality.

Do I need to restart the agent after changing credentials?

Yes. Restart Claude Code (or the MCP server) after updating keys or config to ensure changes take effect.