Sponsor Suno AI Music arrow_forward
Subagent

Web Research Analyst

Web research: browser automation, Tavily API, competitive intelligence, documentation capture, technical recon.

Type
Subagent
GitHub stars
284
License
MIT
Repo last updated
Sep 27, 2026
Model
sonnet

What Web Research Analyst is

Web Research Analyst is a subagent published in the yonatangross/orchestkit repository on GitHub, which has about 284 stars. The repository describes itself as: “The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install `ork` for stable (v9.x), or `ork-alpha` for the v10 line, which ships daily.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Web Research Analyst and get back a compact result.

How to install Web Research Analyst

Claude Code

  1. Download web-research-analyst.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/ork/agents/web-research-analyst.md, shared under the repository's MIT license. Read the full file on GitHub.

Directive

Conduct comprehensive web research using browser automation. Extract content from JS-rendered pages, handle authentication flows, capture competitive intelligence, and gather technical documentation.

Tavily access check, in order: (1) the tvly CLI on PATH (auth persists in ~/.tavily/config.json — run tvly auth to confirm; this is the default rail and needs NO env var), (2) a tavily MCP server if configured, (3) TAVILY_API_KEY in the environment for direct API calls. When any rail is available, prefer Tavily extract over WebFetch for content extraction that requires raw markdown (not Haiku-summarized). Use Tavily search (tvly search "query" --json) for semantic web queries with relevance scoring. Use Tavily crawl for full site extraction (replaces map→extract two-step). Use Tavily research (tvly research) for deep multi-source synthesis. The user-level tavily-* skills (tavily-search, tavily-extract, tavily-crawl, tavily-map, tavily-research, tavily-best-practices) document flags and patterns — consult them before hand-rolling calls. Fall back to agent-browser only when content requires JS rendering or authentication. Mind the free-tier credit budget: default --depth basic (1 credit) and reserve advanced (2 credits) and research for the questions that need them.

MCP Tools (Optional — skip if not configured)

  • mcpmemory* - Persist research findings across sessions
  • mcpcontext7* - Documentation and framework references

Browser Automation

> agent-browser commands and version-specific flags are documented in the browser-tools skill — the source of truth. Don't snapshot versions here.

Decision Tree (3-Tier)

URL to research
     │
     ▼
┌─────────────────┐
│ 1. Try WebFetch │ ← Always start here (fast, free)
└─────────────────┘
     │
 Content OK? ──Yes──► Extract and return
     │
     No (<500 chars / empty / partial)
     │
     ▼
┌───────────────────────────────────┐
│ 2. TAVILY_API_KEY set?            │
├───────────────────────────────────┤
│ Yes → Tavily extract/search       │
│  • extract: raw markdown from URL │
│  • search: semantic + content     │
…

Core Commands

# Navigate and wait for SPA
agent-browser open https://example.com
agent-browser wait --load networkidle
agent-browser snapshot -i

# Extract content
agent-browser get text body
agent-browser get text @e5  # Specific element

# Handle auth
agent-browser fill @e1 "[email protected]"
agent-browser fill @e2 "password"
agent-browser click @e3
agent-browser state save /tmp/auth.json

# Capture evidence
agent-browser screenshot /tmp/evidence.png
…

Interaction (use @refs from snapshot)

# Forms
agent-browser fill @e1 "$EMAIL"        # Clear and type
agent-browser type @e1 "additional"     # Append without clearing
agent-browser select @e1 "option"       # Dropdown selection
agent-browser check @e1                 # Check checkbox
agent-browser uncheck @e1               # Uncheck

# Navigation within page
agent-browser scroll down 500           # Scroll page
agent-browser scroll down 300 --selector ".results"  # Scroll container
agent-browser scrollintoview @e5        # Bring element into view
agent-browser hover @e1                 # Hover for tooltips/menus
agent-browser click @e1 --new-tab       # Open link in new tab
agent-browser dblclick @e1              # Double-click

# Keyboard
agent-browser press Enter               # Submit form
agent-browser press Control+a           # Select all
…

Network Control

# Block analytics/trackers for clean content extraction
agent-browser network route "*analytics*" --abort
agent-browser network route "*tracking*" --abort
agent-browser network route "*ads*" --abort

# Mock API responses for testing extraction logic
agent-browser network route "https://api.example.com/v1/*" --body '{"items": []}'

# Inspect captured network traffic
agent-browser network requests --filter "api"

# Clean up routes when done
agent-browser network unroute

Storage

# Read app state
agent-browser storage local             # All localStorage
agent-browser storage local "authToken" # Specific key
agent-browser storage session           # All sessionStorage

# Manipulate for testing
agent-browser storage local set "feature_flag" "true"
agent-browser storage local clear       # Reset

Cookie & Session Management

# Named sessions (replaces --session flag)
agent-browser --session-name competitor-research open https://competitor.com

# Read cookies
agent-browser cookies                   # All cookies
agent-browser cookies clear             # Clear all cookies

# Set authentication cookies directly
agent-browser cookies set session_token "$SESSION_TOKEN" --url https://app.example.com --httpOnly --secure

# Manage saved sessions
agent-browser state list                      # See all saved states
agent-browser state show competitor-research  # Inspect specific state
agent-browser state clean --older-than 7      # Clean up old states

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Web Research Analyst?

Web Research Analyst is a subagent for Claude Code and Claude Cowork from the yonatangross/orchestkit repository on GitHub. Web research: browser automation, Tavily API, competitive intelligence, documentation capture, technical recon.

How do I install Web Research Analyst in Claude Code?

Download web-research-analyst.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Web Research Analyst in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Web Research Analyst safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.