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.
Install
git clone https://github.com/parallel-web/parallel-cursor-plugin /tmp/parallel-cursor-plugin && ln -s /tmp/parallel-cursor-plugin/skills/parallel-deep-research ~/.claude/skills/parallel-deep-researchFrom README
Deep Research Research topic: $ARGUMENTS Requires parallel-cli ≥ 0.3.0 for text output and context chaining. If a documented command or option is missing, check parallel-cli --version and that command's --help, then follow the -specific upgrade guidance in . API, authentication and input errors are not evidence of an older CLI. When to use (vs parallel-web-search) ONLY use this skill when the user explicitly requests deep/exhaustive research. It can take several minutes and costs more than a quick search, depending on the processor and task. For normal "research X" requests, quick lookups, or fact-checking, use parallel-web-search instead. Step 1: Start the research Choose a descriptive output base in a persistent directory (e.g., reports/ai-chip-market-2026). Include the returned run ID to make it unique, then use this base in step 2 as -o "$FILENAME". Check for existing .json and .md files before saving.