parallel-deep-research

Orchestrate parallel-cli deep-research tasks with multi-turn context and progress tracking.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Ocean326/Agents --skill parallel-deep-research-ocean326
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: parallel-deep-research
Source: https://github.com/Ocean326/Agents/tree/main/skills/global/parallel-deep-research
Command: npx skills add https://github.com/Ocean326/Agents --skill parallel-deep-research-ocean326

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates exhaustive research sessions by orchestrating parallel tooling when a user explicitly requests thorough analysis.

Core Features & Use Cases

  • Orchestrated Deep Research: Launches deep-research tasks via parallel-cli with appropriate processor options and multi-turn context.
  • On-Demand, Context-Aware: Supports follow-ups through --previous-interaction-id for continued analysis.
  • Progress & Output: Provides a monitoring URL and final reports.

Quick Start

Tell the agent to start a deep research task on the given topic.

Frequently Asked Questions about parallel-deep-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate deep research tasks that require long-running analysis?▼

This Skill automates multi-turn context and iterative enrichment for exhaustive deep research sessions by orchestrating parallel-cli tasks, handling long-running analysis on demand. You receive a run_id and a monitoring URL to track progress.

Can I continue an analysis using previous interaction context?▼

Yes, you can continue an analysis using previous interaction context by applying the --previous-interaction-id flag when launching your deep research session. This supports multi-turn context chaining and iterative enrichment for follow-up analysis.

Do I need internet access and parallel-cli to run long-running research sessions?▼

Yes, you need internet access and parallel-cli installed to run long-running research sessions. These dependencies are required to orchestrate deep-research tasks, support processor selection, and return the run_id, interaction_id, and monitoring URL.

What's the best way to monitor progress of an exhaustive research task?▼

The best way to monitor progress of an exhaustive research task is using the monitoring URL provided after launch. The session returns this URL along with a run_id and interaction_id to track your parallel-cli deep-research execution.

Does the --no-wait flag affect processor selection during deep research?▼

Yes, the --no-wait flag works with processor selection to prevent blocking during deep research task execution. This allows the parallel-cli session to launch and return the run_id immediately without waiting for the processor to finish.