parallel-web/parallel-agent-skills

parallel-cli-setup

Set up and maintain the Parallel CLI (install, auth, balance, skills install)

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/parallel-web/parallel-agent-skills --skill parallel-cli-setup

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Parallel CLI Setup

Set up or maintain parallel-cli with minimal friction. If you are running this prompt, your goal is to follow the instructions below and set up parallel-cli for the user so that they can execute searches, run extracts, deep research, etc.

Step 1: Install or upgrade the CLI

Check whether the CLI exists:

bash
command -v parallel-cli

If missing, install with any of these methods:

  1. macOS only: brew install parallel-web/tap/parallel-cli
  2. Linux/macOS/Windows (uv): uv tool install "parallel-web-tools[cli]"
  3. Linux/macOS/Windows (npm): npm install -g parallel-web-cli
  4. Linux/macOS/Windows (pipx): pipx install "parallel-web-tools[cli]" && pipx ensurepath

When parallel-cli is present, require version >=0.9.2. If older, identify the install method before advising an update. Use command -v parallel-cli, then inspect readlink "$(command -v parallel-cli)" if it is a symlink. Paths under ~/.local/share/uv/ tools/ indicate uv tool install; paths under ~/.local/share/parallel-cli/ indicate the standalone installer.

Upgrade commands (choose based on how it was installed):

  • standalone: parallel-cli update
  • uv: uv tool upgrade parallel-web-tools[cli]
  • pipx: pipx upgrade parallel-web-tools[cli]
  • npm: npm update -g parallel-web-cli
  • homebrew: brew update && brew upgrade parallel-web/tap/parallel-cli

Step 2: Authenticate

Check auth status:

bash
parallel-cli auth --json

You will get a response like:

json
{
  "authenticated": true,
  "method": "oauth",
  "env_var_set": false,
  "has_stored_credentials": true,
  "stored_overridden_by_env": false,
  "token_file": "xxx",
  "version": 1,
  "selected_org_id": "legacy",
  "selected_org_name": null,
  "has_control_api_tokens": false
}

If authenticated is false or selected_org_id is legacy, prompt the user to log in:

bash
parallel-cli login --json

If this is a headless session, append --no-browser.

This triggers device OAuth. The user will be prompted to go to a web browser and input the code the CLI outputs.

When invoking from an agent harness, prefer streaming stdout via a Monitor-style tool over blocking on completion.

The output will look like:

json
{"event": "auth_start"}
{"event": "device_code", "verification_uri": "http://localhost:3000/getServiceKeys/device", "verification_uri_complete": "http://localhost:3000/getServiceKeys/device?user_code=CHQX-NQKP&onboard_variant=agent", "user_code": "CHQX-NQKP", "expires_in": 600, "browser_open_attempted": true, "browser_opened": true}
{"event": "auth_waiting"}
{"event": "auth_success"}

{"event": "auth_success"} is emitted only after the user has successfully authorized the CLI. Otherwise it blocks at {"event": "auth_waiting"}.

Step 3: Check balance

After authentication, check the current balance:

bash
parallel-cli balance get

If zero, prompt the user to add balance:

bash
parallel-cli balance add <AMOUNT_IN_CENTS>

Make it clear that a payment method should have been added to the organization. If not, the user can go to <https://platform.parallel.ai/settings> to add one.

Step 4: Install the Parallel skills

Install the skills for the user:

bash
parallel-cli skills install

The user may need to restart their agent if it doesn't support hot reloading.

Step 5: Suggest a first run

Prompt the user to use the newly installed skills to run a search or extract right away. Suggest one of (use $ instead of / for Codex):

  • /parallel-web-search <query> — fast web search
  • /parallel-web-extract <url> — extract content from a URL
  • /parallel-deep-research <topic> — comprehensive research
  • /parallel-data-enrichment <list> — enrich a list of entities

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli Skills
parallel-web
Ufficiale

parallel-search-evaluation

Use for search evaluation, a POC or bake-off, Parallel vs Exa/Tavily comparisons, SimpleQA/DeepSearchQA benchmarks, or diagnosing search evaluation results. For product selection use parallel-api; for integration migration use migrate-to-parallel.

Installazioni / 1h
2
GitHub Stars
95
Aggiornato
17 nov
parallel-web
Ufficiale

parallel-api

Build apps and agents on the Parallel API: Search, Extract, Responses, Task, Decisions and Monitor, through the parallel-web Python and TypeScript SDKs or REST. Use when writing, reviewing or debugging code that calls Parallel; when choosing a Parallel API, search mode, reasoning effort or Task processor; when adding web search, page extraction, cited answers, research, enrichment, web-grounded decisions or web monitoring to an app; when swapping another search provider for Parallel; when settin

Installazioni / 1h
2
GitHub Stars
95
Aggiornato
17 nov
parallel-web
Ufficiale

parallel-findall

Discover entities (companies, people, products, etc.) matching a natural-language description. Use when the user asks to 'find all X' or 'list every Y that…' — e.g., 'Find AI startups that raised Series A in 2026', 'List roofing companies in Charlotte NC', 'Show me YC W24 dev tools companies'. Different from web-search (which returns webpages) and deep-research (which returns a narrative report). Use this when the user wants a structured list of entities.

Installazioni / 1h
2
GitHub Stars
94
Aggiornato
16 nov
parallel-web
Ufficiale

parallel-deep-research

ONLY use when user explicitly says 'deep research', 'exhaustive', 'comprehensive report', or 'thorough investigation'. Slower and more expensive than parallel-web-search. For normal research/lookup requests, use parallel-web-search instead. Supports follow-ups with a known prior Task interaction ID.

Installazioni / 1h
3
GitHub Stars
93
Aggiornato
11 nov