Skip to content
Agentmart
Submit a tool

parallel-deep-research

ONLY use when user explicitly says 'deep research', 'exhaustive', 'comprehensive report', or 'thorough investigation'.

Skill by parallel

IndexedApache-2.0
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/hack4rva-parallel-deep-research-4dc685

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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 multi-turn: pass --previous-interaction-id from a prior research or enrichment to continue with context.

Use cases: documents, research

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/parallel-deep-research

Tools it pre-approves 1

From allowed-tools in SKILL.md: the agent may use these without asking you each time.

  • Bash(parallel-cli:*)

What's inside

Skill name
parallel-deep-research
Description
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 multi-turn: pass --previous-interaction-id from a prior research or enrichment to continue with context.
License
Apache-2.0
Compatibility
Requires parallel-cli and internet access.
Allowed tools
Bash(parallel-cli:*)
Metadata
author: parallel
Instructions
79 lines in SKILL.md · view on GitHub

Before installing

  • Pre-approves some shell commands
  • Instructions call the network

Files (1)

  • SKILL.md

SKILL.md (first lines)

> **Note:** This research was generated using AI assistance (Claude + Parallel.ai) with human expert review. See [methodology](../../docs/methodology.md) for details.

## Deep Research

Research topic: $ARGUMENTS

### When to use (vs parallel-web-search)

ONLY use this skill when the user explicitly requests deep/exhaustive research. Deep research is 10-100x slower and more expensive than parallel-web-search. For normal "research X" requests, quick lookups, or fact-checking, use **parallel-web-search** instead.

### Step 1: Start the research

```bash
parallel-cli research run "$ARGUMENTS" --processor pro-fast --no-wait --json
```

If this is a **follow-up** to a previous research or enrichment task where you know the `interaction_id`, add context chaining:

```bash
parallel-cli research run "$ARGUMENTS" --processor lite --no-wait --json --previous-interaction-id "$INTERACTION_ID"
```

This returns instantly. Do NOT omit `--no-wait` — without it the command blocks for minutes and will time out.

Processor options:

| Processor | Expected latency | Use when |
|-----------|-----------------|----------|
| `pro-fast` | 30s – 5 min | Default — good balance of depth and speed |
| `ultra-fast` | 1 – 10 min | Deeper analysis, more sources (~2x cost) |
| `ultra` | 5 – 25 min | Maximum depth, only when explicitly requested (~3x cost) |

Parse the JSON output to extract the `run_id`, `interaction_id`, and monitoring URL. Immediately tell the user:
- Deep research has been kicked off
- The expected latency for the processor tier chosen
- The monitoring URL where they can track progress

### Step 2: Poll for results

Choose a descriptive filename based on the topic. Use lowercase with hyphens, no spaces.

```bash
parallel-cli research poll "$RUN_ID" -o "$FILENAME" --timeout 540
```

Important:
- Use `--timeout 540` (9 minutes) to stay within tool execution limits
- Do NOT pass `--json` — the full output is large and will flood context
- The `-o` flag generates two output files:
  - `$FILENAME.json` — metadata and basis
  - `$FILENAME.md` — formatted markdown report
- The poll command prints an **executive summary** to stdout when complete. Share this with the user.

### If the poll times out

Re-run the same `parallel-cli research poll` command to continue waiting.

### Response format

**After step 1:** Share the monitoring URL.

**After step 2:**
1. Share the executive summary printed to stdout
2. Tell the user the two generated file paths
3. Share the `interaction_id` for follow-up chaining

Do NOT re-share the monitoring URL after completion.

### Setup

```bash
curl -fsSL https://parallel.ai/install.sh | bash
# or
pipx install "parallel-web-tools[cli]" && pipx ensurepath
parallel-cli login
# or: export PARALLEL_API_KEY="your-key"
```

From hack4rva/pillar-thriving-built-environment, Apache-2.0.

Signals

Stars
0
Forks
1
Open issues
0
Last commit (this folder)
Mar 28, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

More from parallel

Cite this page

parallel-deep-research skill. Agent Mart. https://agentmart.dev/skills/hack4rva-parallel-deep-research-4dc685 (last updated 2026-10-24)