parallel-cli

Orchestrate async web research workflows with search, extraction, and JSON output.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/overviewlabs/WHOX --skill parallel-cli-overviewlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-cli
Source: https://github.com/overviewlabs/WHOX/tree/main/optional-skills/research/parallel-cli
Command: npx skills add https://github.com/overviewlabs/WHOX --skill parallel-cli-overviewlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables agents to perform scalable, structured web research using Parallel CLI, delivering consistent, machine-readable results.

Core Features & Use Cases

  • JSON-first output for automation and easy integration.
  • Async long-running jobs with status, poll, and --no-wait workflows.
  • Context chaining and enrichment across search, extract, and monitor/findall scenarios.

Quick Start

Run a non-interactive web research workflow with parallel-cli to search, extract, and enrich results and return JSON.

Frequently Asked Questions about parallel-cli

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

FAQPage Schema
How do I automate web research and structured data collection from the command line?

Automate web research by running a CLI that orchestrates parallel search, extraction, and enrichment across multiple sources. It returns consistent JSON output for easy integration into automated workflows and pipelines.

Can I run long-running async research jobs and check their status later?

Yes, long-running async research jobs are supported using status, poll, and --no-wait workflows. You can track jobs via managed run IDs to check progress and retrieve results when ready.

How do I get machine-readable JSON output from web search and extraction tasks?

Web search and extraction tasks return JSON-first output directly from the CLI. This ensures deterministic, machine-readable results that integrate easily into automation scripts and data pipelines.

Do I need an API key to run non-interactive parallel web research workflows?

Yes, authentication via a PARALLEL_API_KEY is required to run deterministic, non-interactive web research workflows. This ensures managed access to search, extraction, and enrichment processes.

What is the best way to enrich and chain context across multiple web research sources?

Enrich and chain context across multiple sources by pipelining search, extract, and monitor or findall scenarios. This enables scalable data enrichment and structured collection across various web sources.

Are there limitations to using async CLI workflows for scalable web research?

This CLI is designed for deterministic, non-interactive workflows, so it does not support interactive or real-time conversational research. It is optimized for repeatable, long-running tasks with structured JSON output.