deep-research
Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.
Best use case
deep-research is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.
Teams using deep-research should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/deep-research/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How deep-research Compares
| Feature / Agent | deep-research | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Deep Research > **Drift-prone skill.** Firecrawl/Exa MCP tool names, quotas, and result > shapes change. Verify the configured MCP tools and current API docs before > promising coverage or quoting live source counts. Produce thorough, cited research reports from multiple web sources using firecrawl and exa MCP tools. ## When to Use - User asks to research any topic in depth - Competitive analysis, technology evaluation, or market sizing - Due diligence on companies, investors, or technologies - Any question requiring synthesis from multiple sources - User says "research", "deep dive", "investigate", or "what's the current state of" ## MCP Requirements At least one of: - **firecrawl** — `firecrawl_search`, `firecrawl_scrape`, `firecrawl_crawl` - **exa** — `web_search_exa`, `web_search_advanced_exa`, `crawling_exa` Both together give the best coverage. Configure in `~/.gemini.json` or `~/.codex/config.toml`. ## Workflow ### Step 1: Understand the Goal Ask 1-2 quick clarifying questions: - "What's your goal — learning, making a decision, or writing something?" - "Any specific angle or depth you want?" If the user says "just research it" — skip ahead with reasonable defaults. ### Step 2: Plan the Research Break the topic into 3-5 research sub-questions. Example: - Topic: "Impact of AI on healthcare" - What are the main AI applications in healthcare today? - What clinical outcomes have been measured? - What are the regulatory challenges? - What companies are leading this space? - What's the market size and growth trajectory? ### Step 3: Execute Multi-Source Search For EACH sub-question, search using available MCP tools: **With firecrawl:** ``` firecrawl_search(query: "<sub-question keywords>", limit: 8) ``` **With exa:** ``` web_search_exa(query: "<sub-question keywords>", numResults: 8) web_search_advanced_exa(query: "<keywords>", numResults: 5, startPublishedDate: "2025-01-01") ``` **Search strategy:** - Use 2-3 different keyword variations per sub-question - Mix general and news-focused queries - Aim for 15-30 unique sources total - Prioritize: academic, official, reputable news > blogs > forums ### Step 4: Deep-Read Key Sources For the most promising URLs, fetch full content: **With firecrawl:** ``` firecrawl_scrape(url: "<url>") ``` **With exa:** ``` crawling_exa(url: "<url>", tokensNum: 5000) ``` Read 3-5 key sources in full for depth. Do not rely only on search snippets. ### Step 5: Synthesize and Write Report Structure the report: ```markdown # [Topic]: Research Report *Generated: [date] | Sources: [N] | Confidence: [High/Medium/Low]* ## Executive Summary [3-5 sentence overview of key findings] ## 1. [First Major Theme] [Findings with inline citations] - Key point ([Source Name](url)) - Supporting data ([Source Name](url)) ## 2. [Second Major Theme] ... ## 3. [Third Major Theme] ... ## Key Takeaways - [Actionable insight 1] - [Actionable insight 2] - [Actionable insight 3] ## Sources 1. [Title](url) — [one-line summary] 2. ... ## Methodology Searched [N] queries across web and news. Analyzed [M] sources. Sub-questions investigated: [list] ``` ### Step 6: Deliver - **Short topics**: Post the full report in chat - **Long reports**: Post the executive summary + key takeaways, save full report to a file ## Parallel Research with Subagents For broad topics, use Gemini CLI's Task tool to parallelize: ``` Launch 3 research agents in parallel: 1. Agent 1: Research sub-questions 1-2 2. Agent 2: Research sub-questions 3-4 3. Agent 3: Research sub-question 5 + cross-cutting themes ``` Each agent searches, reads sources, and returns findings. The main session synthesizes into the final report. ## Quality Rules 1. **Every claim needs a source.** No unsourced assertions. 2. **Cross-reference.** If only one source says it, flag it as unverified. 3. **Recency matters.** Prefer sources from the last 12 months. 4. **Acknowledge gaps.** If you couldn't find good info on a sub-question, say so. 5. **No hallucination.** If you don't know, say "insufficient data found." 6. **Separate fact from inference.** Label estimates, projections, and opinions clearly. ## Examples ``` "Research the current state of nuclear fusion energy" "Deep dive into Rust vs Go for backend services in 2026" "Research the best strategies for bootstrapping a SaaS business" "What's happening with the US housing market right now?" "Investigate the competitive landscape for AI code editors" ```
Related Skills
research-ops
Evidence-first current-state research workflow for ECC. Use when the user wants fresh facts, comparisons, enrichment, or a recommendation built from current public evidence and any supplied local context.
market-research
Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Use when the user wants market sizing, competitor comparisons, fund research, technology scans, or research that informs business decisions.
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.
workspace-surface-audit
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Gemini CLI or understanding what capabilities are actually available in their environment.
visa-doc-translate
Translate visa application documents (images) to English and create a bilingual PDF with original and translation
videodb
See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio, video), and create real time alerts for events from live streams or desktop capture.
video-editing
AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.
verification-loop
Comprehensive verification system for code changes
unified-notifications-ops
Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.
ui-demo
Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.
token-budget-advisor
Offers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero controlar cuánto usas", or clear variants where the user is explicitly asking to control answer size or depth. DO NOT TRIGGER when: user has already specified a level in the current session (maintain it), the request is clearly a one-word answer, or "token" refers to auth/session/payment tokens rather than response size.
terminal-ops
Evidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.