parallel-web/parallel-agent-skills

parallel-web-extract

CLI-backed URL extraction.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/parallel-web/parallel-agent-skills --skill parallel-web-extract

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

URL Extraction

Extract content from: $ARGUMENTS

Command

Choose a short, descriptive filename based on the URL or content (e.g., vespa-docs, react-hooks-api). Use lowercase with hyphens, no spaces. Substitute it into the command inline — $FILENAME is a placeholder, not a shell variable.

Pass each requested URL as a separate quoted positional argument, up to 20 per call. Do not collapse multiple URLs into one quoted $ARGUMENTS string or use eval to split them. Construct arguments directly from the requested URLs. For example:

bash
parallel-cli extract "https://docs.parallel.ai/integrations/cli" "https://docs.parallel.ai/integrations/cursor-marketplace" --json -o "/tmp/parallel-docs.json"

-o saves JSON. Use a .json extension and inspect an existing path before use because Extract overwrites it. Read the saved file as authoritative; stdout may truncate and human-readable output previews only part of the content. Do not treat a stale file as a successful response after a failed call.

Options if needed:

  • --objective "focus area" to focus extraction on a specific goal (also silences the "neither objective nor search_queries" warning that V1 emits when neither is set)
  • -q "keyword" (repeatable) to prioritize keywords in excerpts
  • --full-content to include the complete page body (for long articles, PDFs, or when excerpts may not capture what you need)
  • --full-content-max-chars N to cap full-content size per result
  • --no-excerpts to strip excerpts when you only want full content
  • --session-id "<returned-session-id>" to group related Search/Extract calls. A session ID is not a Task interaction ID or run ID; never use it with research status/poll or --previous-interaction-id

Handling failed extractions

Inspect the exit status, API error, results, per-URL errors and any warnings. errors: [] is normal success. Nonempty errors can coexist with successful results: retain and present successful content, then name each failed URL and its returned reason. Empty results or missing content are not a successful extraction. Do not fabricate content. For affected URLs, suggest:

  • Verifying the URL (the page may have moved)
  • Requesting --full-content if excerpts are empty but the returned metadata supports that the page was fetched
  • Using parallel-cli search to locate the current URL if the page was renamed

Response format

Return content as:

[Page Title](URL)

Use returned full_content for full-page requests; excerpts alone are selected passages and must be labelled as such. Even full content may be capped by --full-content-max-chars or upstream limits; do not promise completeness when capped. Preserve retrieved content verbatim, with these rules:

  • Keep content verbatim - do not paraphrase or summarize
  • Preserve every numbered/bulleted item in the retrieved content; do not claim an excerpt contains the whole page
  • Strip only obvious noise: nav menus, footers, ads
  • Preserve all facts, names, numbers, dates, quotes

After the response, mention the output file path (/tmp/$FILENAME.json) so the user knows it's available for follow-up questions.

For large content, keep the full verbatim text in the saved file and provide a brief labelled preview plus its path. Never silently truncate content while claiming it is the complete extraction.

Setup

If parallel-cli is not found, install and authenticate:

bash
/parallel:parallel-cli-setup

If a documented command or option is missing, check the installed version and upgrade through its installation method: standalone parallel-cli update, pipx pipx upgrade parallel-web-tools, uv uv tool upgrade parallel-web-tools, Homebrew brew upgrade parallel-web/tap/parallel-cli, or npm npm update -g parallel-web-cli. Verify help in the same terminal before retrying.

For authentication errors, inspect parallel-cli auth --json and its authenticated boolean; exit zero alone does not prove authentication. A 403 can indicate permissions, policy or billing. Report the actual error; check balance only for a billing-specific failure and never add funds without explicit confirmation.

Related by task

from this repository

More skills

All skills
parallel-web
Official

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.

1h installs
2
GitHub stars
95
Updated
Nov 17
parallel-web
Official

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

1h installs
2
GitHub stars
95
Updated
Nov 17
parallel-web
Official

parallel-cli-setup

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

1h installs
2
GitHub stars
94
Updated
Nov 16
parallel-web
Official

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.

1h installs
2
GitHub stars
94
Updated
Nov 16