tavily-hikari-best-practices
About tavily-hikari-best-practices
A skill for agents and agent workflows that use Tavily Hikari. It covers CLI configuration, JSON output, safe token handling, and choosing between MCP and HTTP-style endpoints.
Key features
- 01CLI configuration guidance
- 02JSON output for agents
- 03Hikari token handling
- 04MCP and API endpoint distinctions
- 05Search scope and output guidance
Use cases
- 01Configuring `tvly-hikari` for an agent workflow
- 02Choosing an endpoint for an MCP client or CLI
- 03Running a Hikari smoke test
MCP support
It distinguishes the `/mcp` endpoint used by MCP clients from the `/api/tavily` surface used by CLI and HTTP-style clients. MCP clients connect to `/mcp` with bearer authentication.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ ivanli-cn/ tavily-hikari --skill tavily-hikari-best-practicesAfter installing, type/tavily-hikari-best-practicesin Claude Code to confirm it loaded.
Details
From the project READMETavily Hikari Best Practices
Use this skill when deciding how to call Tavily Hikari from an agent workflow.
Rules
-
Use
tvly-hikari ... --jsonfor agent-readable output. -
Use Hikari tokens beginning with
th-; never paste official Tavily API keys into downstream agents or user machines. -
Configure Hikari once:
tvly-hikari configure --base-url https://<your-hikari-host> --token th-<id>-<secret> -
Treat
/mcpand/api/tavily/*as different integration surfaces:- MCP clients use
https://<your-hikari-host>/mcpwith bearer auth. - CLI and HTTP-style clients use
https://<your-hikari-host>/api/tavily.
- MCP clients use
-
Keep searches narrow, save large outputs with
-oor--output-dir, and cite source URLs when answering factual questions. -
Do not test against Tavily production upstream unless the operator explicitly approves it; use local or sandbox Hikari endpoints for smoke tests.
Quick Smoke
tvly-hikari doctor
tvly-hikari search "Tavily Hikari smoke test" --json