SKILL.md
Tavily 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:
``bash 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>/mcp with bearer auth. - CLI and HTTP-style clients use https://<your-hikari-host>/api/tavily.
- 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