Optional vendor skill for Parallel CLI — agent-native web search, extraction, deep research, enrichment, FindAll, and monitoring. Prefer JSON output and non-interactive flows.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Optional vendor skill for Parallel CLI — agent-native web search, extraction, deep research, enrichment, FindAll, and monitoring. Prefer JSON output and non-interactive flows.
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
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
Try the least invasive install path available for the environment.
Homebrew
brew install parallel-web/tap/parallel-cli
npm
npm install -g parallel-web-cli
Python package
pip install "parallel-web-tools[cli]"
Standalone installer
curl -fsSL https://parallel.ai/install.sh | bash
If you want an isolated Python install, pipx can also work:
Use --objective when the page is broad and you only need one slice of information.
Deep research
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
parallel-cli research run \
"Compare the leading AI coding agents by pricing, model support, and enterprise controls" \
--processor core \
--json
Async launch + poll
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
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
Use when the user has CSV/JSON/tabular inputs and wants additional columns inferred from web research.
Suggest columns
parallel-cli enrich suggest "Find the CEO and annual revenue" --json
Plan a config
parallel-cli enrich plan -o config.yaml
Inline data
parallel-cli enrich run \
--data '[{"company": "Anthropic"}, {"company": "Mistral"}]' \
--intent "Find headquarters and employee count" \
--json
Non-interactive file run
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
parallel-cli enrich run config.yaml
Status / polling
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
Use for web-scale entity discovery when the user wants a discovered dataset rather than a short answer.
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
Use for ongoing change detection over time.
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:
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
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
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
Check current auth / install state:
parallel-cli auth
parallel-cli --help
Update commands:
parallel-cli update
pip install --upgrade parallel-web-tools
parallel-cli config auto-update-check off
Pitfalls
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.
