SKILLoptionalHermes Optional Skills

Parallel Cli

Name: Parallel Cli
Author: Hermes Agent

Agent-native web search, deep research, and enrichment

ResearchWebSearchDeep-ResearchEnrichmentCLIOptionalHermes skill

Last registry verification2026-08-18v1.1.0Hermes Agent

Open original source ↗اقرأ بالعربية

Plain meaning

What does it add to Hermes?

Agent-native web search, deep research, and enrichment

Parallel Cli is a skill related to research and sources. It gives the agent a way to find external information and sources instead of relying only on model memory.

This plain-language explanation is based on the publisher description. The original text remains visible for verification.

Use it when

Use it when your goal in research and sources is clear and you can limit it to the data and actions it actually needs.

Skip it when

Do not add it merely to experiment when Hermes already has a simpler path, or when you cannot review its source and permissions.

Who is it for?

Best for users who want a repeatable way of working inside Hermes.

Safe first test

Ask for one recent fact with two sources, then open both links and verify dates and evidence.

Original publisher description

Agent-native web search, deep research, and enrichment

✓

Data source

This entry was indexed from Hermes Optional Skills. Our explanation interprets the type and domain without inventing a capability not present upstream.

Security review

The source is official or editorially reviewed, but you still need to review permissions and version compatibility.

Safe setup path

Inspect, install, then test.

01
Open the source
Match the publisher, license, and description to your need. Check the real update history.
02
Review permissions and secrets
Never paste a secret value into this site. Use environment-variable names and grant the smallest scope.
03
Copy setup only after review
The controls below copy text. They do not execute commands on your device.
04
Test with a non-sensitive task
Inspect the visible tools, then exclude write or delete tools you do not need.

Install command

Review the command, then copy it.

hermes skills install parallel-cli

Hermes Belarabi does not execute this command. Installation happens on your device and remains subject to Hermes scanning and your review.

The full skill definition

Exactly what Hermes loads when this skill runs.

Reproduced from the official documentation. Read it before enabling the skill: this text becomes the agent's instructions.

Agent-native web search, deep research, and enrichment.

Skill metadata

A lookup table. Do not read it all; find the row that applies to you.

Source	Optional — install with `hermes skills install official/research/parallel-cli`
Path	`optional-skills/research/parallel-cli`
Version	`1.1.0`
Author	Hermes Agent
License	MIT
Platforms	linux, macos, windows
Tags	`Research`, `Web`, `Search`, `Deep-Research`, `Enrichment`, `CLI`
Related skills	`duckduckgo-search`, `mcporter`

Reference: full SKILL.md

Explains the idea itself. Read it slowly; the later sections build on it.

Use parallel-cli when the user explicitly wants Parallel, or when a terminal-native workflow would benefit from Parallel's vendor-specific stack for web search, extraction, deep research, enrichment, entity discovery, or monitoring.

This is an optional third-party workflow, not a Hermes core capability.

Important expectations:

Parallel is a paid service with a free tier, not a fully free local tool.
It overlaps with Hermes native web_search / web_extract, so do not prefer it by default for ordinary lookups.
Prefer this skill when the user mentions Parallel specifically or needs capabilities like Parallel's enrichment, FindAll, or monitor workflows.

parallel-cli is designed for agents:

JSON output via --json
Non-interactive command execution
Async long-running jobs with --no-wait, status, and poll
Context chaining with --previous-interaction-id
Search, extract, research, enrichment, entity discovery, and monitoring in one CLI

When to use it

Explains the idea itself. Read it slowly; the later sections build on it.

Prefer this skill when:

The user explicitly mentions Parallel or parallel-cli
The task needs richer workflows than a simple one-shot search/extract pass
You need async deep research jobs that can be launched and polled later
You need structured enrichment, FindAll entity discovery, or monitoring

Prefer Hermes native web_search / web_extract for quick one-off lookups when Parallel is not specifically requested.

Installation

Ordered, practical steps. Run one and confirm it worked before moving on.

Try the least invasive install path available for the environment.

Homebrew

Shell1 line

brew install parallel-web/tap/parallel-cli

npm

Shell1 line

npm install -g parallel-web-cli

Python package

Shell1 line

pip install "parallel-web-tools[cli]"

Standalone installer

Shell1 line

curl -fsSL https://parallel.ai/install.sh | bash

If you want an isolated Python install, pipx can also work:

Shell2 lines

pipx install "parallel-web-tools[cli]"
pipx ensurepath

Authentication

Settings you configure once. Change one at a time so you can see what each does. Set PARALLEL_API_KEY in your environment, not in the chat.

Interactive login:

Shell1 line

parallel-cli login

Headless / SSH / CI:

Shell1 line

parallel-cli login --device

API key environment variable:

Shell1 line

export PARALLEL_API_KEY="***"

Verify current auth status:

Shell1 line

parallel-cli auth

If auth requires browser interaction, run with pty=true.

Core rule set

Explains the idea itself. Read it slowly; the later sections build on it.

Always prefer --json when you need machine-readable output.
Prefer explicit arguments and non-interactive flows.
For long-running jobs, use --no-wait and then status / poll.
Cite only URLs returned by the CLI output.
Save large JSON outputs to a temp file when follow-up questions are likely.
Use background processes only for genuinely long-running workflows; otherwise run in foreground.
Prefer Hermes native tools unless the user wants Parallel specifically or needs Parallel-only workflows.

Quick reference

Explains the idea itself. Read it slowly; the later sections build on it.

Text10 lines

parallel-cli
├── auth
├── login
├── logout
├── search
├── extract / fetch
├── research run|status|poll|processors
├── enrich run|status|poll|plan|suggest|deploy
├── findall run|ingest|status|poll|result|enrich|extend|schema|cancel
└── monitor create|list|get|update|delete|events|event-group|simulate

Common flags and patterns

Explains the idea itself. Read it slowly; the later sections build on it.

Commonly useful flags:

--json for structured output
--no-wait for async jobs
--previous-interaction-id <id> for follow-up tasks that reuse earlier context
--max-results <n> for search result count
--mode one-shot|agentic for search behavior
--include-domains domain1.com,domain2.com
--exclude-domains domain1.com,domain2.com
--after-date YYYY-MM-DD

Read from stdin when convenient:

Shell2 lines

echo "What is the latest funding for Anthropic?" | parallel-cli search - --json
echo "Research question" | parallel-cli research run - --json

Search

Explains the idea itself. Read it slowly; the later sections build on it.

Use for current web lookups with structured results.

Shell5 lines

parallel-cli search "What is Anthropic's latest AI model?" --json
parallel-cli search "SEC filings for Apple" --include-domains sec.gov --json
parallel-cli search "bitcoin price" --after-date 2026-01-01 --max-results 10 --json
parallel-cli search "latest browser benchmarks" --mode one-shot --json
parallel-cli search "AI coding agent enterprise reviews" --mode agentic --json

Useful constraints:

--include-domains to narrow trusted sources
--exclude-domains to strip noisy domains
--after-date for recency filtering
--max-results when you need broader coverage

If you expect follow-up questions, save output:

Shell1 line

parallel-cli search "latest React 19 changes" --json -o /tmp/react-19-search.json

When summarizing results:

lead with the answer
include dates, names, and concrete facts
cite only returned sources
avoid inventing URLs or source titles

Extraction

Explains the idea itself. Read it slowly; the later sections build on it.

Use to pull clean content or markdown from a URL.

Shell4 lines

parallel-cli extract https://example.com --json
parallel-cli extract https://company.com --objective "Find pricing info" --json
parallel-cli extract https://example.com --full-content --json
parallel-cli fetch https://example.com --json

Use --objective when the page is broad and you only need one slice of information.

Deep research

Explains the idea itself. Read it slowly; the later sections build on it.

Use for deeper multi-step research tasks that may take time.

Common processor tiers:

lite / base for faster, cheaper passes
core / pro for more thorough synthesis
ultra for the heaviest research jobs

Synchronous

Shell4 lines

parallel-cli research run \
  "Compare the leading AI coding agents by pricing, model support, and enterprise controls" \
  --processor core \
  --json

Async launch + poll

Shell9 lines

parallel-cli research run \
  "Compare the leading AI coding agents by pricing, model support, and enterprise controls" \
  --processor ultra \
  --no-wait \
  --json

parallel-cli research status trun_xxx --json
parallel-cli research poll trun_xxx --json
parallel-cli research processors --json

Context chaining / follow-up

Shell5 lines

parallel-cli research run "What are the top AI coding agents?" --json
parallel-cli research run \
  "What enterprise controls does the top-ranked one offer?" \
  --previous-interaction-id trun_xxx \
  --json

Recommended Hermes workflow:

launch with --no-wait --json
capture the returned run/task ID
if the user wants to continue other work, keep moving
later call status or poll
summarize the final report with citations from the returned sources

Enrichment

Explains the idea itself. Read it slowly; the later sections build on it.

Use when the user has CSV/JSON/tabular inputs and wants additional columns inferred from web research.

Suggest columns

Shell1 line

parallel-cli enrich suggest "Find the CEO and annual revenue" --json

Plan a config

Shell1 line

parallel-cli enrich plan -o config.yaml

Inline data

Shell4 lines

parallel-cli enrich run \
  --data '[{"company": "Anthropic"}, {"company": "Mistral"}]' \
  --intent "Find headquarters and employee count" \
  --json

Non-interactive file run

Shell6 lines

parallel-cli enrich run \
  --source-type csv \
  --source companies.csv \
  --target enriched.csv \
  --source-columns '[{"name": "company", "description": "Company name"}]' \
  --intent "Find the CEO and annual revenue"

YAML config run

Shell1 line

parallel-cli enrich run config.yaml

Status / polling

Shell2 lines

parallel-cli enrich status <task_group_id> --json
parallel-cli enrich poll <task_group_id> --json

Use explicit JSON arrays for column definitions when operating non-interactively. Validate the output file before reporting success.

FindAll

Explains the idea itself. Read it slowly; the later sections build on it.

Use for web-scale entity discovery when the user wants a discovered dataset rather than a short answer.

Shell6 lines

parallel-cli findall run "Find AI coding agent startups with enterprise offerings" --json
parallel-cli findall run "AI startups in healthcare" -n 25 --json
parallel-cli findall status <run_id> --json
parallel-cli findall poll <run_id> --json
parallel-cli findall result <run_id> --json
parallel-cli findall schema <run_id> --json

This is a better fit than ordinary search when the user wants a discovered set of entities that can be reviewed, filtered, or enriched later.

Monitor

Explains the idea itself. Read it slowly; the later sections build on it.

Use for ongoing change detection over time.

Shell4 lines

parallel-cli monitor list --json
parallel-cli monitor get <monitor_id> --json
parallel-cli monitor events <monitor_id> --json
parallel-cli monitor delete <monitor_id> --json

Creation is usually the sensitive part because cadence and delivery matter:

Shell1 line

parallel-cli monitor create --help

Use this when the user wants recurring tracking of a page or source rather than a one-time fetch.

Recommended Hermes usage patterns

Explains the idea itself. Read it slowly; the later sections build on it.

Fast answer with citations

Run parallel-cli search ... --json
Parse titles, URLs, dates, excerpts
Summarize with inline citations from the returned URLs only

URL investigation

Run parallel-cli extract URL --json
If needed, rerun with --objective or --full-content
Quote or summarize the extracted markdown

Long research workflow

Run parallel-cli research run ... --no-wait --json
Store the returned ID
Continue other work or periodically poll
Summarize the final report with citations

Structured enrichment workflow

Inspect the input file and columns
Use enrich suggest or provide explicit enriched columns
Run enrich run
Poll for completion if needed
Validate the output file before reporting success

Error handling and exit codes

A troubleshooting section. Find the symptom that matches yours rather than reading it end to end.

The CLI documents these exit codes:

0 success
2 bad input
3 auth error
4 API error
5 timeout

If you hit auth errors:

check parallel-cli auth
confirm PARALLEL_API_KEY or run parallel-cli login / parallel-cli login --device
verify parallel-cli is on PATH

Maintenance

Explains the idea itself. Read it slowly; the later sections build on it.

Check current auth / install state:

Shell2 lines

parallel-cli auth
parallel-cli --help

Update commands:

Shell3 lines

parallel-cli update
pip install --upgrade parallel-web-tools
parallel-cli config auto-update-check off

Pitfalls

Explains the idea itself. Read it slowly; the later sections build on it.

Do not omit --json unless the user explicitly wants human-formatted output.
Do not cite sources not present in the CLI output.
login may require PTY/browser interaction.
Prefer foreground execution for short tasks; do not overuse background processes.
For large result sets, save JSON to /tmp/*.json instead of stuffing everything into context.
Do not silently choose Parallel when Hermes native tools are already sufficient.
Remember this is a vendor workflow that usually requires account auth and paid usage beyond the free tier.