add-tavily-tool

# Add Tavily Tool Install the pinned `mcp-remote` bridge in the agent image and register Tavily's remote MCP server for each selected agent group. The MCP server supplies its tool descriptions and input schemas at runtime. The registered server exposes: - `mcp__tavily__tavily_search` - `mcp__tavily__tavily_extract` The registration is provider-agnostic: any provider with MCP support picks it up (Claude, OpenCode, and Codex all do). Groups on the Claude provider already have the built-in `WebSearch` and `WebFetch` tools (`container/agent-runner/src/providers/claude.ts`), so the skill adds the most for groups on other providers, and for Tavily's structured extraction anywhere. ## Phase 1: Pre-flight Check whether the bridge is already in the image manifest, then list the groups: ```bash grep -n '"mcp-remote"' container/cli-tools.json || true ncl groups list ``` Ask which agent groups should receive Tavily. If `mcp-remote` is already present at a pinned version, reuse the existing entry instead of adding a second one. ## Phase 2: Install the MCP bridge Add this object to the top-level array in `container/cli-tools.json` when an entry named `mcp-remote` is not already present: ```json { "name": "mcp-remote", "version": "0.1.38" } ``` Keep the JSON valid and limit the entry to the two fields shown; this package does not require a native build-script opt-in. Copy the dependency guard into the host test tree: ```bash cp .claude/skills/add-tavily-tool/tavily-manifes...