parallel-cli

Orchestrate vendor-specific search, extraction, and research tasks from the CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Terminal-centric teams need a capable CLI to orchestrate vendor-specific web search, extraction, deep research, enrichment, and monitoring workflows beyond Hermes native tools.

Core Features & Use Cases

  • Parallel CLI provides a unified command-line interface for web search, data extraction, deep research, enrichment, and FindAll-style entity discovery, plus monitoring workflows.
  • It supports JSON output, non-interactive runs, async job control, and context chaining to tie tasks together across sessions.
  • Common use cases include vendor comparison, large-scale monitoring, and automated research pipelines initiated from the terminal.

Quick Start

Use parallel-cli to initiate a non-interactive research workflow and poll for results via JSON output.

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 search and data extraction workflows from the CLI?

Terminal-centric web search and data extraction can be orchestrated via a CLI that supports non-interactive runs, async job control, and JSON outputs. This enables automated research pipelines directly from the terminal without manual intervention.

What is context chaining and how does it tie terminal research tasks together?

Context chaining is a mechanism that ties search, extraction, and research tasks together across terminal sessions. It passes structured JSON results from one async job to another, maintaining state for complex vendor research workflows.

Can I run non-interactive deep research jobs and poll for JSON results?

Yes, you can run non-interactive deep research jobs and poll for JSON results. The CLI supports async execution and structured outputs, allowing you to initiate a workflow and retrieve machine-readable data for automation pipelines.

Does the CLI support authentication flows for vendor-specific extraction?

Yes, the CLI supports authentication flows for vendor-specific extraction tasks. This allows you to securely access protected endpoints and perform structured data retrieval during terminal-centric monitoring workflows.

What is the best way to monitor large-scale entities from the terminal?

The best way to monitor large-scale entities from the terminal is using a CLI that supports FindAll-style entity discovery and async execution. This approach handles monitoring workflows while outputting structured JSON for tracking changes.

When do I need async job control for CLI research workflows?

You need async job control for CLI research workflows when running large-scale monitoring or parallel extraction tasks. It allows non-interactive operations to execute without blocking the terminal, returning structured JSON upon completion.