Parallel Web Extract
CLI-backed URL extraction. Use when the user explicitly invokes this skill, needs CLI-only controls or saved JSON output, or no Parallel web_fetch MCP tool is available. When the bundled Parallel Search MCP is available, prefer its web_fetch tool for ordinary webpages, articles, PDFs, and JavaScript-heavy sites.
- Skill ID
- parallel-web/parallel-agent-skills/parallel-web-extract
- Publisher
- parallel-web
- Repository
- parallel-agent-skills
- Installs
- 0
- Files
- 1
- Requires
- Requires parallel-cli and internet access.
- Synced
- Sep 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
parallel-web/parallel-agent-skills/parallel-web-extractInstalls these files- SKILL.md
What this skill tells the agent
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.
parallel-cli extract "$ARGUMENTS" --json -o "/tmp/$FILENAME.json"Concrete example:
parallel-cli extract "https://docs.parallel.ai" --json -o "/tmp/parallel-docs.json"Note: -o always saves JSON. The extension must be .json.
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-contentto include the complete page body (for long articles, PDFs, or when excerpts may not capture what you need)--full-content-max-chars Nto cap full-content size per result--no-excerptsto strip excerpts when you only want full content
Handling failed extractions
If the response has an errors field, an empty results array, or a 404/timeout for the URL, do NOT fabricate content. Tell the user the extraction failed, surface the upstream status, and suggest:
- Verifying the URL (the page may have moved)
- Retrying with
--full-contentif excerpts came back empty but the page exists - Using
parallel-cli searchto locate the current URL if the page was renamed
Response format
Return content as:
[Page Title](URL)
Then the extracted content verbatim, with these rules:
- Keep content verbatim - do not paraphrase or summarize
- Parse lists exhaustively - extract EVERY numbered/bulleted item
- 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.
Setup
If parallel-cli is not found, install and authenticate:
/parallel:parallel-cli-setupIf parallel-cli extract returns 403, tell the user balance is likely required. Offer to run parallel-cli balance get, and if needed ask for explicit confirmation before running parallel-cli balance add <amount_cents>. Then retry the original extract command.
More from parallel-web
Use this skill in a project
Open any RiverX project, search the Skills panel for parallel-web/parallel-agent-skills/parallel-web-extract, and install it in one click.
