Optional guide for web_researcher sub-agent. Use only when the user explicitly asks to delegate web research (e.g. /subagent-spawn web_researcher, "запусти web_researcher").
Scanned 9/3/2026
Install to Claude Code
npx -y skills add javded-itres/Holix --skill web-researcher --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Web Researcher?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/javded-itres-web-researcher)More formats (shields.io, HTML) on the badges page.
---
name: web-researcher
description: >
Optional guide for web_researcher sub-agent. Use only when the user explicitly
asks to delegate web research (e.g. /subagent-spawn web_researcher, "запусти
web_researcher").
tags:
- research
- web
- search
- subagent
- delegate
user-invocable: true
---
## When to use
Only when the user **explicitly** requests the `web_researcher` sub-agent
(`/subagent-spawn web_researcher …`, "делегируй web_researcher", etc.).
Do not auto-spawn for ordinary search questions.
## How to delegate
1. `delegate_to_subagent(agent_type="web_researcher", task="<full user request>")`
2. `wait_subagent_result(job_id="<returned job_id>")` if the user wants the answer in this reply
3. Summarize the sub-agent response for the user
## Task text
Include in `task`: what to find, geography/route, date (today), preferred sources, output format.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...