parallel-research

casper-studios/casper-marketplace · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/casper-studios/casper-marketplace --skill parallel-research
0 commentsdiscussion
summary

Deep web research, competitive intelligence, entity discovery, and data enrichment using Parallel AI's specialized APIs.

skill.md

Parallel Research

Overview

Deep web research, competitive intelligence, entity discovery, and data enrichment using Parallel AI's specialized APIs.

Quick Decision Tree

What do you need?
├── Quick factual answer (3-5 seconds)
│   └── Chat API ($0.005/request)
│   └── Script: scripts/parallel_research.py chat "question"
├── Comprehensive research report (5min-2hr)
│   └── Deep Research API ($0.30/report for ultra)
│   └── Script: scripts/parallel_research.py research "topic"
├── Find entities matching criteria (companies, people)
│   └── FindAll API ($0.03 + $0.10/match)
│   └── Script: scripts/parallel_research.py findall "query"
└── Enrich existing data (add fields to records)
    └── Task API with schema ($0.025/record for core)
    └── Script: scripts/parallel_research.py enrich data.csv

Environment Setup

# Required in .env
PARALLEL_API_KEY=your_api_key_here

Get your API key: https://platform.parallel.ai/settings/api-keys

Common Usage

Quick Q&A

python scripts/parallel_research.py chat "What is Anthropic's latest funding round?"

Deep Research Report

python scripts/parallel_research.py research "Competitive landscape of AI code editors in 2025" --processor ultra

Find Companies

python scripts/parallel_research.py findall "AI code editor companies that raised funding in 2024-2025" --limit 50

Basic Research (Simplified)

python scripts/basic_research.py "Company Name"

Vendor Selection

python scripts/vendor_selection.py "CRM software" --requirements "enterprise,API,automation"

Processor Tiers

Processor Cost/1K Latency Best For
lite $5 10-60s Basic metadata
base $10 15-100s Simple research
core $25 1-5min Cross-referenced research
pro $100 2-10min Exploratory research
ultra $300 5-25min Deep research (recommended)
ultra-fast $300 2-10min Speed + quality

Cost Estimates

Task API Cost
100 quick questions Chat $0.50
Market research report Deep Research (ultra) $0.30
Find 50 competitors FindAll (core) ~$5.00
Enrich 100 leads Task (core) $2.50

Free Tier

20,000 requests free (combined across all APIs).

Security Notes

Credential Handling

Data Privacy

  • Research queries are sent to Parallel AI servers
  • Research outputs may contain third-party company information
  • Results are stored locally in .tmp/ directory
  • Parallel AI may log queries for service improvement
  • Avoid including sensitive internal data in research queries

Access Scopes

  • API key provides full access to all research endpoints
  • No granular permission scopes available
  • Monitor usage and costs via Parallel AI dashboard

Compliance Considerations

  • Data Sources: Research pulls from public web sources
  • Citation: Always cite sources in research outputs
  • Accuracy: AI-generated research should be verified
  • Competitive Intel: Ensure competitive research complies with policies
  • Third-Party Data: Respect intellectual property of sources
  • PII in Results: Research results may contain company/individual PII
  • Data Freshness: Verify currency of time-sensitive information

Troubleshooting

Common Issues

Issue: Processor timeout

Symptoms: Request times out or returns partial results Cause: Complex query requiring more processing time than allowed Solution:

  • Use a faster processor tier (lite or base instead of ultra)
  • Simplify the research query
  • Break complex queries into multiple smaller requests
  • Increase timeout in script if configurable

Issue: Credits exhausted

Symptoms: "Insufficient credits" or quota error Cause: Account credits depleted Solution:

  • Check balance at https://platform.parallel.ai/dashboard
  • Upgrade plan or purchase additional credits
  • Use lower-cost processor tiers for less critical queries
  • Monitor usage to avoid unexpected depletion

Issue: Invalid response format

Symptoms: JSON parsing error or unexpected response structure Cause: API returned error or malformed response Solution:

  • Check query format matches API requirements
  • Retry the request (may be transient issue)
  • Verify API key is valid and active
  • Review API documentation for expected response format

Issue: Empty or irrelevant results

Symptoms: Research returns no results or off-topic content Cause: Query too narrow, ambiguous, or poorly structured Solution:

  • Broaden the search query
  • Add context to clarify query intent
  • Try different phrasing or keywords
  • Use Chat API first to validate query understanding

Issue: API authentication failed

Symptoms: "Invalid API key" or 401 error Cause: API key expired, invalid, or not set Solution:

Issue: Rate limited

Symptoms: 429 error or "rate limit exceeded" Cause: Too many concurrent requests Solution:

  • Add delays between requests
  • Reduce parallel request count
  • Implement exponential backoff
  • Contact support for higher rate limits if needed

Resources

  • references/api-guide.md - Complete API documentation
  • references/basic-research.md - Simple company research
  • references/vendor-selection.md - Vendor comparison workflow

Integration Patterns

Research to Report

Skills: parallel-research → content-generation Use case: Create polished reports from research findings Flow:

  1. Run deep research on topic/company
  2. Generate structured research output
  3. Format into branded document via content-generation

FindAll to CRM

Skills: parallel-research → attio-crm Use case: Populate CRM with discovered companies Flow:

  1. Use FindAll to discover companies matching criteria
  2. Enrich each company with additional data
  3. Create/update company records in Attio CRM

Research to Sheets

Skills: parallel-research → google-workspace Use case: Build research database in Google Sheets Flow:

  1. Run FindAll or batch research on multiple entities
  2. Structure results as tabular data
  3. Upload to Google Sheets for team collaboration
how to use parallel-research

How to use parallel-research on Cursor

AI-first code editor with Composer

1

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-research
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/casper-studios/casper-marketplace --skill parallel-research

The skills CLI fetches parallel-research from GitHub repository casper-studios/casper-marketplace and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/parallel-research

Reload or restart Cursor to activate parallel-research. Access the skill through slash commands (e.g., /parallel-research) 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

GET_STARTED →

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. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.539 reviews
  • Dev Kapoor· Dec 28, 2024

    Solid pick for teams standardizing on skills: parallel-research is focused, and the summary matches what you get after install.

  • Henry Brown· Dec 20, 2024

    We added parallel-research from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ganesh Mohane· Dec 8, 2024

    Useful defaults in parallel-research — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Sakshi Patil· Nov 27, 2024

    parallel-research is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Liam Gill· Nov 19, 2024

    We added parallel-research from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Charlotte Patel· Nov 11, 2024

    Solid pick for teams standardizing on skills: parallel-research is focused, and the summary matches what you get after install.

  • Chaitanya Patil· Oct 18, 2024

    Keeps context tight: parallel-research is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Liam Mensah· Oct 10, 2024

    parallel-research fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Diego Ghosh· Oct 2, 2024

    parallel-research has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Diego Iyer· Sep 21, 2024

    Useful defaults in parallel-research — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 39

1 / 4