Web Research With curl
laude-institute/headlong
Looks things up online from the shell with curl: fetching pages, searching DuckDuckGo's HTML endpoint, stripping tags for readable text and pulling JSON APIs.
Deep web research skill using parallel subagents + chromux browser-explorer + Gemini.
$ npx skills add team-attention/hoyeon --skill deep-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install team-attention/hoyeon deep-research --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/deep-research .claude/skills/deep-research && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deep-research" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/deep-research into .claude/skills/deep-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-research", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/team-attention/hoyeon/tree/main/skills/deep-researchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add team-attention/hoyeon --skill deep-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install team-attention/hoyeon deep-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/deep-research .agents/skills/deep-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deep-research" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/deep-research into .agents/skills/deep-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-research", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add team-attention/hoyeon --skill deep-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install team-attention/hoyeon deep-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/deep-research .cursor/skills/deep-research && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deep-research" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/deep-research into .cursor/skills/deep-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-research", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/team-attention/hoyeon.git --path skills/deep-research--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add team-attention/hoyeon --skill deep-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install team-attention/hoyeon deep-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/deep-research .gemini/skills/deep-research && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deep-research" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/deep-research into .gemini/skills/deep-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-research", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install team-attention/hoyeon deep-researchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add team-attention/hoyeon --skill deep-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/deep-research .github/skills/deep-research && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deep-research" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/deep-research into .github/skills/deep-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-research", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add team-attention/hoyeon --skill deep-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install team-attention/hoyeon deep-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/hoyeon.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/deep-research .opencode/skills/deep-research && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deep-research" agent skill from https://github.com/team-attention/hoyeon/tree/main/skills/deep-research into .opencode/skills/deep-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-research", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
deep-researchDeep web research skill using parallel subagents + chromux browser-explorer + Gemini.
Deep Research is an agent skill from team-attention/hoyeon. 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.
Its SKILL.md is about 6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/browser-extract.sh` and `scripts/gemini-research.sh`).
It sits in Research & Science, covering Deep research. It works with Bash. The repository describes itself as: Requirements-first Harness — derive, verify, execute. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 7cff032. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 2 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
opensslnpxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Deep Research loads about 6k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 1,552 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from team-attention/hoyeon at commit 7cff032, republished under its MIT licence (© team-attention). 1,552 words, ~5,964 tokens.
.claude/skills/deep-research/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.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.
Agent(...) with background dispatch, WebSearch, WebFetch, chromux,
and Gemini CLI as described below.hoyeon-external-researcher, hoyeon-docs-researcher, and
hoyeon-browser-explorer.researcher for
external docs/web research and direct chromux Bash calls for browser
extraction.date +%Y%m%d-%H%M%S and store artifacts under
$HOME/.hoyeon/codex-research-$RUN_ID/research/./deep-research <research question or topic>
/deep-research --auto <research question or topic>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.Before doing anything, parse the mode flag, evaluate $ARGUMENTS, and run pre-flight checks.
Run all checks in a single Bash call:
# Session dir init
SESSION_ID="[CLAUDE_SESSION_ID from UserPromptSubmit hook]"
RESEARCH_DIR="$HOME/.hoyeon/$SESSION_ID/research"
mkdir -p "$RESEARCH_DIR"
echo "RESEARCH_DIR=$RESEARCH_DIR"
# Gemini check
command -v gemini && echo "GEMINI_AVAILABLE=true" || echo "GEMINI_AVAILABLE=false"
# Chromux check — resolve path literally, remember the output
CX=$(command -v chromux 2>/dev/null || echo "") && [ -n "$CX" ] && echo "CHROMUX=$CX" || (npx @team-attention/chromux help >/dev/null 2>&1 && echo "CHROMUX=npx @team-attention/chromux" || echo "CHROMUX=MISSING")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:
/path/to/chromux launch default --headless 2>/dev/null || true| 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:
cat > "$RESEARCH_DIR/plan.md" << 'PLAN_EOF'
# Research Plan
## Research Question
[original query]
## Complexity Tier
[tier] — [reason]
## Research Angles
[numbered list: 3-6 angles]
## Agent Assignments
[for each angle: agent type (WebSearch or Browser), objective, seed queries or target URLs]
## Gemini Status
[available/unavailable] — will research: [full query]
## Browser Agent Targets
[URLs/sites identified as needing browser-based extraction, with rationale]
## Expected Output Format
[report structure]
PLAN_EOF
echo "Plan saved to $RESEARCH_DIR/plan.md"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.
Break the topic into distinct, non-overlapping research angles. Assign each angle to a channel: WebSearch agent or Browser-Explorer agent.
| 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.
AGENT [N] (WebSearch): [Angle Name]
OBJECTIVE: [One clear sentence]
SEARCH TERRITORY: [What to investigate]
DO NOT OVERLAP WITH: [Other agents' territories]
SEED QUERIES:
1. [Short, broad query - 2-3 words]
2. [Medium specificity - 3-5 words]
3. [Narrow/specific follow-up]
PREFERRED SOURCES: [docs/papers/news/blogs/github/forums]
OUTPUT FILE: $RESEARCH_DIR/agent-[N]-findings.mdBROWSER AGENT [N]: [Angle Name]
OBJECTIVE: [One clear sentence]
TARGET URLS: [Specific URLs to visit]
EXTRACT: [What specific data/content to extract from each URL]
OUTPUT FILE: $RESEARCH_DIR/browser-[N]-findings.md
RATIONALE: [Why browser is needed — e.g., "Reddit uses infinite scroll / JS-rendered comments"]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.
In the SAME message as all Agent calls, dispatch Gemini as a background Bash:
Bash(run_in_background=true):
/absolute/path/to/script/gemini-research.sh "<full research query>" "$HOME/.hoyeon/SESSION_ID/research" 300Note: 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.
Each WebSearch subagent receives this prompt (customize per agent):
You are Research Agent [N], a focused investigator. ultrathink before each search.
ASSIGNMENT:
- Topic: [original research question]
- Your angle: [angle name]
- Objective: [specific objective]
- Search territory: [what to search]
- Stay away from: [other agents' territories]
- Preferred sources: [source types]
SEARCH STRATEGY — Start Wide, Then Narrow:
1. Begin with SHORT, BROAD queries (2-3 words). Evaluate what's available.
2. Based on initial results, form more specific follow-up queries.
3. Go deeper on the most promising leads.
4. Aim for [N] total search queries (per complexity tier).
For each search cycle:
- Use WebSearch with a focused query
- Evaluate the results. Ask: Is this relevant? Is this from a credible source?
Does this add new information?
- For the best 2-3 results, use WebFetch to extract full content.
Include a focused question about what to extract.
- Take detailed notes with EXACT source URLs for every claim.
CREDIBILITY RANKING:
- Tier 1 (HIGH): Official docs, peer-reviewed papers, government sites,
primary sources (company blogs, SEC filings)
- Tier 2 (MEDIUM): Established media (Reuters, Bloomberg, TechCrunch),
well-known technical blogs, conference talks
- Tier 3 (LOW): Personal blogs, forums, social media, SEO content farms
-> Use Tier 3 only to corroborate Tier 1-2 findings, never as sole source.
WRITE YOUR FINDINGS to the file: [RESEARCH_DIR]/agent-[N]-findings.md
Use this exact structure:
# Agent [N]: [Angle Name]
## Search Queries Used
1. "[query]" -> [number] relevant results
2. ...
## Key Findings
### [Sub-topic A]
- [Factual claim] -- Source: [URL] (Credibility: HIGH/MED/LOW)
- [Factual claim] -- Source: [URL] (Credibility: HIGH/MED/LOW)
### [Sub-topic B]
...
## Source Registry
| # | URL | Title | Type | Credibility | Date |
|---|-----|-------|------|-------------|------|
| 1 | ... | ... | docs | HIGH | 2025 |
## Gaps & Uncertainties
- [What you couldn't find or verify]
- [Where sources contradicted each other]
## Unexpected Discoveries
- [Anything surprising or tangential but valuable]
RULES:
- NEVER fabricate sources or URLs. If you can't find it, say so.
- NEVER search for things outside your assigned territory.
- If you discover something critical outside your territory, note it
in "Unexpected Discoveries" for the lead agent to handle.
- Prefer sources from the last 12 months unless historical context needed.
- For Korea-relevant topics, search in BOTH English and Korean.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:
You are a Browser Research Agent. Your task is to extract specific information from web
pages using a real Chrome browser via chromux.
## Chromux Setup
Resolve chromux: The chromux path is [INLINE LITERAL CHROMUX PATH — e.g., /usr/local/bin/chromux].
Chrome is already running in headless mode.
Generate your session ID:
```bash
openssl rand -hex 2Remember the output literally (e.g., ab12 → your session ID is exp-ab12). Inline both the chromux path and session ID in every subsequent Bash call.
Topic: [original research question] Your angle: [angle name] Objective: [one clear sentence — what information to find]
Visit these URLs in order:
For each URL:
/path/to/chromux open exp-XXXX <url>sleep 2 (or use run with await sleep(2000) if mid-script)/path/to/chromux snapshot exp-XXXX/path/to/chromux close exp-XXXXWrite your findings to: [RESEARCH_DIR]/browser-[N]-findings.md
Structure:
[Extracted data with exact quotes where useful]
| URL | Title | Content Type | Date |
|---|
**Agent tool call:**Agent( subagent_type: "hoyeon:browser-explorer", mode: "dontAsk", prompt: "[browser agent prompt as above, fully customized]" )
For simple single-page extraction, a helper script is also available at
`.claude/skills/deep-research/scripts/browser-extract.sh` — reference it if needed for
basic URL content dumps. For multi-page browsing or dynamic interactions, always use the
browser-explorer agent directly.
---
## Phase 3: Collect & Cross-Validate
After all agents complete, read each findings file from RESEARCH_DIR:$RESEARCH_DIR/agent-1-findings.md $RESEARCH_DIR/agent-2-findings.md ... $RESEARCH_DIR/browser-1-findings.md $RESEARCH_DIR/browser-2-findings.md ... $RESEARCH_DIR/gemini-deep-research.md # if Gemini was available
### Cross-Validation Steps
1. **Deduplicate**: Identify claims found by multiple agents/sources. These are
high-confidence. Note: if agents properly stayed in their lanes, overlap should
be minimal — but where it exists, it's a strong signal.
2. **Cross-Channel Validation**: Compare WebSearch, Browser, and Gemini findings:
- Claims confirmed by WebSearch AND Browser agents = very high confidence (both
channels independently found the same thing)
- Claims found ONLY by browser agents = unique deep extraction, note extraction context
- Claims confirmed by BOTH Claude agents and Gemini = highest confidence (cross-model)
- Claims where Claude and Gemini DISAGREE = flag for resolution
3. **Contradiction Check**: Where agents found conflicting information:
- Note both versions with their sources
- Assess which source is more credible
- If critical, run 1-2 targeted WebSearch queries to break the tie
4. **Gap Analysis**: What's missing?
- Are any angles poorly covered? (agent found <3 sources)
- Are there obvious follow-up questions no agent addressed?
- For critical gaps: run a quick supplementary search (max 3 queries)
5. **Unexpected Discovery Triage**: Review all agents' "Unexpected Discoveries" sections.
If anything is important to the overall question, run a brief follow-up search.
6. **Build Confidence Matrix** and save:
**File: `$RESEARCH_DIR/validation.md`**| Claim | Supporting Agents | Gemini Confirms? | Browser Confirms? | Source Count | Top Source |
|---|
| Claim | Agent | Gemini Confirms? | Source | Why Medium |
|---|
| Claim | Agent | Issue |
|---|
| Topic | Claude Finding | Gemini Finding | Resolution |
|---|
| Topic | WebSearch Finding | Browser Finding | Resolution |
|---|
| Topic | Version A (Source) | Version B (Source) | Resolution |
|---|
---
## Phase 4: Synthesize Report
Now write the final report. ultrathink to plan the narrative structure before writing.
**File: `$RESEARCH_DIR/report-[topic-slug]-[YYYY-MM-DD].md`**
```markdown
# [Research Topic]
> [Date] | [N] sources consulted | [N] WebSearch agents + [N] Browser agents + Gemini |
> [N] search queries | Confidence: [HIGH/MED/LOW] overall
## Executive Summary
[3-5 sentences. Lead with the single most important finding. Include
one surprising insight. End with the practical implication.]
## Table of Contents
[Auto-generate based on sections below]
## Detailed Findings
### [Section 1: Most Important Topic]
[Synthesize across all channels. Don't just list — analyze. Every factual
claim must have an inline citation as [Source Name](URL). Explicitly
note confidence level for non-obvious claims.]
### [Section 2]
...
### [Section N]
...
## Analysis & Implications
[What patterns emerge across all findings? What do they mean for
someone making decisions about this topic? Be specific and actionable.]
## Contrarian Views & Counterarguments
[What credible sources disagree with the mainstream view? Present
the strongest counterarguments fairly.]
## Gaps & Limitations
[What couldn't be determined? Why? What would be needed to fill
these gaps? Be honest — this builds trust.]
## Confidence Assessment
| Finding | Confidence | Sources | Cross-Model | Cross-Channel | Basis |
|---------|-----------|---------|-------------|---------------|-------|
| ... | HIGH | 4 | Confirmed | Confirmed | Official docs + Gemini + Browser |
| ... | MEDIUM | 2 | Unconfirmed | N/A | Two blogs, Gemini silent |
| ... | LOW | 1 | Contradicted| N/A | Single post, Gemini disagrees |
## Sources
### Tier 1: Official & Primary Sources
1. [Title](URL) -- [one-line contribution to this report]
### Tier 2: Established Media & Technical Analysis
2. [Title](URL) -- [one-line contribution]
### Tier 3: Community & Other
3. [Title](URL) -- [one-line contribution]
---
*Generated by deep-research skill | [N] WebSearch agents + [N] Browser agents + Gemini | [date]*The user reads in a terminal — deliver the core value INLINE, then link to files for depth. Do NOT just say "see the report file."
Print the full research results directly in the conversation:
## [Research Topic]
> [Date] | [N] sources | [N] WebSearch agents + [N] Browser agents + Gemini |
> Confidence: [HIGH/MED/LOW]
### Executive Summary
[3-5 sentences]
### Key Findings
**1. [Most important finding]**
[2-3 lines with inline citations]
**2. [Second finding]**
[2-3 lines with inline citations]
**3. [Third finding]**
[2-3 lines with inline citations]
[... continue for all major findings]
### Confidence Assessment
| Finding | Confidence | Cross-Model | Cross-Channel | Basis |
|---------|-----------|-------------|---------------|-------|
| ... | HIGH | Confirmed | Confirmed | ... |
### Gaps & Follow-up
- [Gap 1]
- [Gap 2]
- Suggested follow-up: [direction]This should be comprehensive enough that the user gets full value without opening any file.
After the inline report, add a footer:
---
Full report + raw data:
$RESEARCH_DIR/report-[topic]-[date].md <- Full report
$RESEARCH_DIR/agent-*-findings.md <- WebSearch agent raw data
$RESEARCH_DIR/browser-*-findings.md <- Browser-extracted raw data
$RESEARCH_DIR/gemini-deep-research.md <- Gemini independent research
$RESEARCH_DIR/validation.md <- Cross-validation results/deep-research AI agent frameworks comparison 2025
-> Medium tier, 3 WebSearch agents + 1 Browser agent + Gemini:
WebSearch: frameworks landscape, technical comparison, community adoption
Browser: GitHub discussions/issues on major frameworks (dynamic content)
/deep-research What is the current state of MCP adoption?
-> Medium tier, 3 WebSearch agents + 1 Browser agent + Gemini:
WebSearch: protocol spec & ecosystem, adoption metrics, developer tooling
Browser: Reddit /r/LocalLLaMA threads on MCP (JS-rendered comments)
/deep-research Is Rust replacing C++ in systems programming?
-> Medium tier, 3 WebSearch agents + 1 Browser agent + Gemini:
WebSearch: technical comparison, industry adoption data, official statements
Browser: HN/Reddit discussions on Rust adoption (community sentiment threads)© team-attention, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (scripts) in skills/deep-research of team-attention/hoyeon.
Open the folder on GitHubat commit 7cff032
Deep Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deep Research this skillteam-attention/hoyeon | 173 | — | ~6k | Automated safety check: Pass | MIT | |
| Web Research With curllaude-institute/headlong | 1.2k | — | ~362 | Automated safety check: Pass | Apache-2.0 | |
| Asksd0xdev/sd0x-harness | 192 | — | ~2.1k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Deep Research WorkflowTokenRhythm/opensquilla | 7.1k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Deep Researchsanjay3290/ai-skills | 431 | 9 repos | ~683 | Automated safety check: Notes | Apache-2.0 |
laude-institute/headlong
Looks things up online from the shell with curl: fetching pages, searching DuckDuckGo's HTML endpoint, stripping tags for readable text and pulling JSON APIs.
sd0xdev/sd0x-harness
Context-aware Q&A with auto context gathering. An agent skill from sd0xdev/sd0x-harness.
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
TokenRhythm/opensquilla
Runs multi-round research in three stages with a persisted state file, evidence tracking and a long-form report with per-claim citations.
sanjay3290/ai-skills
Execute autonomous multi-step research using Google Gemini Deep Research Agent.
google-deepmind/science-skills
Query the ChEMBL database for bioactive molecules, drug targets, bioactivity data, approved drugs, and chemical structures.
team-attention/hoyeon
This skill should be used when the user asks to "analyze session", "evaluate skill execution", "check session logs", provides a session ID with a skill path, or wants to verify that a skill executed…
team-attention/hoyeon
Recon-first browser automation. An agent skill from team-attention/hoyeon.
team-attention/hoyeon
This skill should be used when the user wants to verify their changes before pushing, or update the project's rule checklists.
team-attention/hoyeon
This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR.
team-attention/hoyeon
Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen.
team-attention/hoyeon
This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use"…
Works with
Categories
Deep web research skill using parallel subagents + chromux browser-explorer + Gemini. Deep Research is an agent skill from team-attention/hoyeon. Deep web research skill using parallel subagents + chromux browser-explorer + Gemini.
Deep Research fits situations like: tasks that involve Deep research.
Run `npx skills add team-attention/hoyeon --skill deep-research -a claude-code`. Or copy the skill folder (skills/deep-research in team-attention/hoyeon) into .claude/skills/deep-research in your project. Claude Code loads it when a task matches its description.
Run `npx skills add team-attention/hoyeon --skill deep-research -a codex`. Or copy the skill folder (skills/deep-research in team-attention/hoyeon) into .agents/skills/deep-research in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add team-attention/hoyeon --skill deep-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deep-research, .gemini/skills/deep-research, .github/skills/deep-research and .opencode/skills/deep-research in your project.
Going by SKILL.md and its folder, Deep Research needs a shell for the scripts in its folder and the command-line tools its instructions call (openssl and npx). Our summary lists: Node.js; A Bash shell.
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Deep Research is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 6k tokens (SKILL.md is roughly 24k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Deep Research: Web Research With curl (laude-institute/headlong, 1.2k stars), Ask (sd0xdev/sd0x-harness, 192 stars), GitHub Deep Research (bytedance/deer-flow, 84k stars) and Deep Research Workflow (TokenRhythm/opensquilla, 7.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
team-attention (a GitHub organization) maintains it in team-attention/hoyeon, which has 173 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on May 21, 2026.
Source: team-attention/hoyeon on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.