parallel-web-search▌
parallel-web/parallel-agent-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Fast web search for current information, research, and fact-finding across the internet.
- ›Executes single objective-based queries or multiple keyword searches in parallel, returning up to 10 results with excerpts and metadata
- ›Supports time-sensitive filtering via --after-date and domain-specific searches with --include-domains
- ›Outputs structured JSON with titles, URLs, publish dates, and excerpts for easy parsing and follow-up queries
- ›Requires inline citations for every claim using
Web Search
Search the web for: $ARGUMENTS
Command
Choose a short, descriptive filename based on the query (e.g., ai-chip-news, react-vs-vue). Use lowercase with hyphens, no spaces.
parallel-cli search "$ARGUMENTS" -q "<keyword1>" -q "<keyword2>" --json --max-results 10 --excerpt-max-chars-total 27000 -o "/tmp/$FILENAME.json"
The first argument is the objective — a natural language description of what you're looking for. It replaces multiple keyword searches with a single call for broad or complex queries. Add -q flags for specific keyword queries to supplement the objective. The -o flag saves the full results to a JSON file for follow-up questions.
Options if needed:
--after-date YYYY-MM-DDfor time-sensitive queries--include-domains domain1.com,domain2.comto limit to specific sources
Parsing results
Do not set max_output_tokens on the command execution — the output is already bounded by --max-results and --excerpt-max-chars-total. Capping output tokens will truncate the JSON and break parsing.
Parse the JSON from stdout. For each result, extract:
- title, url, publish_date
- Useful content from excerpts (skip navigation noise like menus, footers, "Skip to content")
Response format
CRITICAL: Every claim must have an inline citation. Use markdown links like Title pulling only from the JSON output. Never invent or guess URLs.
Synthesize a response that:
- Leads with the key answer/finding
- Includes specific facts, names, numbers, dates
- Cites every fact inline as Source Title — do not leave any claim uncited
- Organizes by theme if multiple topics
End with a Sources section listing every URL referenced:
Sources:
- [Source Title](https://example.com/article) (Feb 2026)
- [Another Source](https://example.com/other) (Jan 2026)
This Sources section is mandatory. Do not omit it.
After the Sources section, 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:
curl -fsSL https://parallel.ai/install.sh | bash
If unable to install that way, install via pipx instead:
pipx install "parallel-web-tools[cli]"
pipx ensurepath
Then authenticate:
parallel-cli login
Or set an API key: export PARALLEL_API_KEY="your-key"
How to use parallel-web-search on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add parallel-web-search
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches parallel-web-search from GitHub repository parallel-web/parallel-agent-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate parallel-web-search. Access the skill through slash commands (e.g., /parallel-web-search) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★66 reviews- ★★★★★Isabella Gill· Dec 28, 2024
Useful defaults in parallel-web-search — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Henry Agarwal· Dec 24, 2024
I recommend parallel-web-search for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Hana Ramirez· Dec 20, 2024
We added parallel-web-search from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Isabella Ghosh· Dec 20, 2024
Solid pick for teams standardizing on skills: parallel-web-search is focused, and the summary matches what you get after install.
- ★★★★★Mia Mensah· Dec 16, 2024
Registry listing for parallel-web-search matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Aarav Johnson· Dec 16, 2024
Keeps context tight: parallel-web-search is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Lucas Flores· Dec 8, 2024
parallel-web-search has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Mia Taylor· Nov 27, 2024
Solid pick for teams standardizing on skills: parallel-web-search is focused, and the summary matches what you get after install.
- ★★★★★William Bhatia· Nov 19, 2024
parallel-web-search is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Mia Gupta· Nov 15, 2024
parallel-web-search fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 66