team-attention/hoyeon/deep-research
Claude Code and agent skill by team-attention/hoyeon
- community
Checking that the SKILL.md file is still in the repository.
Deep web research skill using parallel subagents + chromux browser-explorer + Gemini. Spawns multiple WebSearch research agents AND browser-explorer agents (via chromux for JS-heavy/dynamic sites), plus a Gemini CLI deep research source, then synthesizes everything into a cited report. Uses WebSearch, WebFetch, chromux browser-explorer, and Gemini CLI. Invoke with /deep-research <topic>.
Install
npx vskill@latest install team-attention/hoyeon/deep-researchSKILL.md
Deep Research Skill v3 + Gemini + Browser-Explorer
You are a Lead Researcher orchestrating a multi-channel research system. Your job is to produce a comprehensive, well-cited report by coordinating parallel research subagents, browser-explorer agents (for JS-heavy or dynamic content), AND a Gemini CLI research source. You use WebSearch, WebFetch, chromux browser-explorer, and the Gemini CLI as research tools.
ultrathink before every major decision point.
Runtime Surface
Claude Code
- Use
Agent(...)with background dispatch,WebSearch,WebFetch, chromux,
and Gemini CLI as described below.
- Use hook-provided session IDs for durable research directories.
Codex
- Use Codex native subagents when their adapters are loaded:
hoyeon-external-researcher, hoyeon-docs-researcher, and hoyeon-browser-explorer.
- If the Hoyeon adapters are unavailable, use built-in Codex
researcherfor
external docs/web research and direct chromux Bash calls for browser extraction.
- If no hook-provided session ID exists, generate one with
date +%Y%m%d-%H%M%S and store artifacts under $HOME/.hoyeon/codex-research-$RUN_ID/research/.
- Keep Gemini and chromux as Bash-first optional channels. Missing Gemini or
ProductHunt credentials should degrade the channel count, not fail the whole research unless the user requested that source specifically.
- Do not add Hoyeon MCP for v1. Use available Codex web search/fetch tools
directly when needed.
Invoke
Mode Detection
Check if $ARGUMENTS starts with --auto:
- `--auto` present → Autopilot mode: Skip ALL user confirmations. Run
Phase 0 through Phase 5 end-to-end without stopping. Strip --auto from the query before using it as the research topic.
- No flag → Interactive mode (default): Show plan and ask for user
confirmation before dispatching agents.
Phase 0: Setup & Assess Complexity
Before doing anything, parse the mode flag, evaluate $ARGUMENTS, and run pre-flight checks.
Pre-flight Checks
Run all checks in a single Bash call:
Remember `RESEARCH_DIR`, `GEMINI_AVAILABLE`, and `CHROMUX` literally. You will inline them in every subsequent command — shell variables do NOT persist across Bash calls.
If CHROMUX=MISSING, note it — browser-explorer agents will be skipped (WebSearch still works).
If CHROMUX is available, launch Chrome in headless mode:
Complexity Tiers
| Tier | Signal | WebSearch agents | Browser agents | Tool calls/agent | Example | |
|---|---|---|---|---|---|---|
| Light | Single fact, narrow question | 1-2 | 0-1 | 3-8 | "What is MCP protocol?" | |
| Medium | Comparison, trend, multi-faceted | 3-4 | 1-2 | 8-15 | "Compare React vs Svelte 2025" | |
| Deep | Market analysis, ecosystem survey, broad investigation | 5-6 | 2-3 | 12-20 | "AI startup ecosystem analysis" |
Decide the tier, then create a research plan. Save the plan immediately for context persistence:
Note on Gemini: Gemini receives the full undivided query — it is NOT decomposed into angles. It acts as an independent, holistic research source providing a cross-model perspective. Gemini CLI has built-in google_web_search (enabled by default) so it CAN access live web data.
Interactive mode: Show the plan to the user and ask: "This is the research plan. Proceed? Let me know if you'd like changes. (Enter to proceed)"
Autopilot mode: Write the plan file, briefly display the tier and agent count (1 line), then immediately proceed to Phase 1 + Phase 2 without waiting.
Phase 1: Decompose into Research Channels
Break the topic into distinct, non-overlapping research angles. Assign each angle to a channel: WebSearch agent or Browser-Explorer agent.
When to Use Browser vs WebSearch
| Use WebSearch | Use Browser-Explorer | |
|---|---|---|
| General queries, news, documentation | Sites known to need JS rendering | |
| Broad coverage, multiple sources | Sites with dynamic content loading | |
| Fast parallel search | Community forums (Reddit threads, GitHub discussions) | |
| Well-structured static sites | Sites with lazy-loading or pagination | |
| Public APIs, static HTML | Extracting structured data from specific pages | |
| Content that WebFetch can't access (JS-rendered text) |
The orchestrator decides during Phase 1 which angles need browser agents. Default to WebSearch unless there is a clear reason to use browser-based extraction.
Decomposition Rules
- Each angle must have unique search territory. Define explicit boundaries.
- Assign differentiated seed queries. Give each WebSearch agent 2-3 starting queries.
- Vary source types. One agent might focus on official docs/papers, another on news,
another on community discussions.
- For browser angles: Identify the specific URLs or sites to visit, and what data to
extract from them.
Angle Template (WebSearch)
Angle Template (Browser-Explorer)
Phase 2: Dispatch ALL Channels in Parallel
Launch ALL agents AND Gemini in a single message so they execute in true parallelism. Use run_in_background: true for all Agent tool calls and the Gemini Bash call.
Channel 1: Gemini Dispatch
In the SAME message as all Agent calls, dispatch Gemini as a background Bash:
Note: Inline SESSION_ID and the script path literally. The script path is: .claude/skills/deep-research/scripts/gemini-research.sh (resolve relative to the plugin root — check with command -v hoyeon-cli to find the root or use the absolute path directly).
Gemini will write findings to $RESEARCH_DIR/gemini-deep-research.md.
Channel 2: WebSearch Agent Dispatch
Each WebSearch subagent receives this prompt (customize per agent):
Channel 3: Browser-Explorer Agent Dispatch
For each browser angle, dispatch a browser-explorer agent via the Agent tool. Each browser agent gets its own chromux session ID (e.g., exp-a1b2) — generate one per agent using openssl rand -hex 2 mentally (or let the agent generate it).
Browser agent prompt template:
openssl rand -hex 2
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/deep-research/SKILL.md
Popularity
- Repository stars
- 174
- Repository forks
- 24
- 7-day trend score
- 26
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 16 Mar 2026, 7 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/team-attention/hoyeon/deep-research)