ivanli-cn/tavily-hikari

tavily-hikari-research

Run multi-step Tavily research through Tavily Hikari with tvly-hikari.

First seen Jul 15, 2026

Installation

$ npx skills add ivanli-cn/tavily-hikari --skill tavily-hikari-research

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from ivanli-cn/tavily-hikari.

npx skills add ivanli-cn/tavily-hikari

Browse all from ivanli-cn/tavily-hikari

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 347
License LICENSE
Default branch main
Open issues 18
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,156 B
  • docs SUMMARY.md 100 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 36 installs

SKILL.md

Tavily Hikari Research

Use this skill when the task needs multi-step Tavily research through Tavily Hikari.

Workflow

  1. Write a concise research question with scope, date, geography, and source constraints.
  2. Run:

``bash tvly-hikari research "Compare Tavily CLI, Agent Skills, and MCP for AI agents" --json ``

  1. Save the response for longer investigations:

``bash tvly-hikari research "Compare Tavily CLI, Agent Skills, and MCP for AI agents" --json -o tavily-research.json ``

  1. If the official CLI returns an async request id, inspect or wait for the result through the

official follow-up commands exposed by the wrapper:

``bash tvly-hikari research status <request-id> --json tvly-hikari research poll <request-id> --json -o tavily-research.json ``

Hikari Notes

  • Requests go to the configured Hikari /api/tavily/research facade.
  • Hikari token quota applies to research calls.
  • Hikari audit logs retain the downstream token context while upstream keys remain private.