/deep-research

name: deep-research
description: Deep research and analysis tool. Generates comprehensive HTML reports on any topic, domain, paper, or technology. Use when user asks to research, analyze, investigate, deep-dive, or generate a report on any subject. Supports academic papers (arXiv), technologies, trends, comparisons, and general topics.

Deep Research

Analyze any topic, domain, or paper and generate a beautiful HTML report using Actionbook browser automation and json-ui rendering.

Usage

/deep-research:analyze <topic>
/deep-research:analyze <topic> --lang zh
/deep-research:analyze <topic> --output ./reports/my-report.json

Or simply tell Claude: "帮我深度研究 XXX 并生成报告" / "Research XXX and generate a report"

Parameters

| Parameter | Required | Default | Description | |-----------|----------|---------|-------------| | `topic` | Yes | - | The subject to research (any text) | | `--lang` | No | `both` | Language: `en`, `zh`, or `both` (bilingual) | | `--output` | No | `./output/<topic-slug>.json` | Output path for JSON report |

Topic Detection

| Pattern | Type | Strategy | |---------|------|----------| | `arxiv:XXXX.XXXXX` | Paper | **arXiv Advanced Search** (Step 2b) + ar5iv deep read | | `doi:10.XXX/...` | Paper | Resolve DOI, then **arXiv Advanced Search** for related work | | Academic keywords (paper, research, model, algorithm) | Academic topic | **arXiv Advanced Search** (Step 2b) + Google for non-academic sources | | URL | Specific page | Fetch and analyze the page | | General text | Topic research | Google search + arXiv Advanced Search if relevant |

Architecture

┌──────────┐     ┌──────────────┐     ┌──────────────┐     ┌──────────┐
│  Claude   │────▶│  Actionbook  │────▶│  Web Pages   │────▶│ Extract  │
│  Code     │     │  Browser CLI │     │  (multiple)  │     │ Content  │
└──────────┘     └──────────────┘     └──────────────┘     └─────┬────┘
      │                                                           │
      │          ┌──────────────┐     ┌──────────────┐           │
      ├─────────▶│  Actionbook  │     │ arXiv Adv.   │           │
      │          │  search/get  │────▶│ Search Form  │──────────▶│
      │          │  (selectors) │     │ (40+ fields) │           │
      │          └──────────────┘     └──────────────┘           │
      │                                                           │
      │    Actionbook indexes arXiv form selectors,               │
      │    enabling field-specific, filtered academic              │
      │    searches that WebFetch/WebSearch CANNOT do.             │
      │                                                           │
┌──────────┐     ┌──────────────┐     ┌──────────────┐           │
│  Open in │◀────│   json-ui    │◀────│  Write JSON  │◀──────────┘
│  Browser │     │   render     │     │  Report      │  Synthesize
└──────────┘     └──────────────┘     └──────────────┘

Why Actionbook, Not WebFetch/WebSearch?

| Capability | Actionbook | WebFetch/WebSearch | |------------|-----------|-------------------| | Operate complex web forms (dropdowns, checkboxes, date pickers) | Yes — uses indexed selectors | No | | arXiv: search by Author, Title, Abstract separately | Yes — `#terms-0-field` select | No — keyword only | | arXiv: filter by subject (CS, Physics, Math, ...) | Yes — category checkboxes | No | | arXiv: filter by date range or specific year | Yes — date inputs | No | | Read pages with verified selectors (no guessing) | Yes — `actionbook get` | No — raw HTML parse | | Interact with any indexed site's UI | Yes — click, type, select | No — read-only |

**This is the core value of Actionbook for research: it turns web forms into structured, programmable interfaces for AI agents.**

MUST USE Actionbook CLI

**Always use `actionbook browser` commands for web browsing. Never use WebFetch or WebSearch.**

actionbook browser open <url>          # Navigate to page
actionbook browser snapshot            # Get accessibility tree
actionbook browser text [selector]     # Extract text content
actionbook browser screenshot [path]   # Capture visual
actionbook browser click <selector>    # Click element
actionbook browser close               # Close browser (ALWAYS do this at end)

Complete Workflow

Step 1: Plan Search Strategy

Based on the topic, generate 5-8 search queries from different angles:

• Core definition / overview
• Latest developments / news
• Technical details / implementation
• Comparisons / alternatives
• Expert opinions / analysis
• Use cases / applications

**Search order — ALWAYS query Actionbook API first, then search:**

| Step | Action | Why | |------|--------|-----| | **Step 2 (FIRST)** | **Query Actionbook API** | Get verified selectors for arXiv Advanced Search form, ar5iv papers, and any other known sites BEFORE browsing. This is the foundation for all subsequent steps. | | **Step 3 (SECOND)** | **arXiv Advanced Search** | Use Actionbook selectors from Step 2 to perform multi-field, filtered academic search. Even non-academic topics often have relevant papers. | | **Step 4 (THIRD)** | Google / Bing search | Supplement with blogs, news, code, discussions, non-academic sources. |

**IMPORTANT:** Always query Actionbook API first (Step 2) to get selectors, then use them in arXiv Advanced Search (Step 3). This is what makes Actionbook-powered research fundamentally different from WebFetch/WebSearch — the agent knows the exact selectors for every form field before it even opens the browser.

Step 2: Query Actionbook API for Selectors (ALWAYS DO THIS FIRST)

**BEFORE browsing any URL, query Actionbook's indexed selectors.** This gives you verified CSS/XPath selectors instead of guessing.

# Search for indexed actions by domain
actionbook search "<keywords>" -d "<domain>"

# Get detailed selectors for a specific page
actionbook get "<domain>:/<path>:<area>"

**Pre-indexed sites useful for research:**

| Site | area_id | Key Selectors |