deep-research

sanjay3290/ai-skills · 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/sanjay3290/ai-skills --skill deep-research
0 commentsdiscussion
summary

Run autonomous research tasks that plan, search, read, and synthesize information into comprehensive reports.

skill.md

Gemini Deep Research Skill

Run autonomous research tasks that plan, search, read, and synthesize information into comprehensive reports.

Requirements

  • Python 3.8+
  • httpx: pip install -r requirements.txt
  • GEMINI_API_KEY environment variable

Setup

  1. Get a Gemini API key from Google AI Studio
  2. Set the environment variable:
    export GEMINI_API_KEY=your-api-key-here
    
    Or create a .env file in the skill directory.

Usage

Start a research task

python3 scripts/research.py --query "Research the history of Kubernetes"

With structured output format

python3 scripts/research.py --query "Compare Python web frameworks" \
  --format "1. Executive Summary\n2. Comparison Table\n3. Recommendations"

Stream progress in real-time

python3 scripts/research.py --query "Analyze EV battery market" --stream

Start without waiting

python3 scripts/research.py --query "Research topic" --no-wait

Check status of running research

python3 scripts/research.py --status <interaction_id>

Wait for completion

python3 scripts/research.py --wait <interaction_id>

Continue from previous research

python3 scripts/research.py --query "Elaborate on point 2" --continue <interaction_id>

List recent research

python3 scripts/research.py --list

Output Formats

  • Default: Human-readable markdown report
  • JSON (--json): Structured data for programmatic use
  • Raw (--raw): Unprocessed API response

Cost & Time

Metric Value
Time 2-10 minutes per task
Cost $2-5 per task (varies by complexity)
Token usage ~250k-900k input, ~60k-80k output

Best Use Cases

  • Market analysis and competitive landscaping
  • Technical literature reviews
  • Due diligence research
  • Historical research and timelines
  • Comparative analysis (frameworks, products, technologies)

Workflow

  1. User requests research → Run --query "..."
  2. Inform user of estimated time (2-10 minutes)
  3. Monitor with --stream or poll with --status
  4. Return formatted results
  5. Use --continue for follow-up questions

Exit Codes

  • 0: Success
  • 1: Error (API error, config issue, timeout)
  • 130: Cancelled by user (Ctrl+C)
how to use deep-research

How to use deep-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 deep-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/sanjay3290/ai-skills --skill deep-research

The skills CLI fetches deep-research from GitHub repository sanjay3290/ai-skills 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/deep-research

Reload or restart Cursor to activate deep-research. Access the skill through slash commands (e.g., /deep-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.855 reviews
  • Henry Yang· Dec 28, 2024

    I recommend deep-research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Mateo Garcia· Dec 24, 2024

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

  • Carlos Johnson· Dec 24, 2024

    deep-research reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Carlos Taylor· Nov 19, 2024

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

  • Emma Sanchez· Nov 15, 2024

    I recommend deep-research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Emma Menon· Nov 15, 2024

    Registry listing for deep-research matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Jin Sethi· Oct 10, 2024

    Registry listing for deep-research matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Kaira Verma· Oct 6, 2024

    deep-research reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Soo Liu· Oct 6, 2024

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

  • Alexander Anderson· Sep 25, 2024

    I recommend deep-research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 55

1 / 6