deep-research
Run autonomous research tasks that plan, search, read, and synthesize information into comprehensive reports.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 3.3w
- Forks
- 3.9k
01 前言 Front Matter
- name
- deep-research
- metadata
- { "risk": "safe", "source": "https://github.com/sanjay3290/ai-skills/tree/main/skills/deep-research", "date_added": "2026-02-27" }
- description
- Run autonomous research tasks that plan, search, read, and synthesize information into comprehensive reports.
02 资源文件 1
- 参考文档agents/openai.yaml146 B
03 SKILL.md 正文
Gemini Deep Research Skill
Run autonomous research tasks that plan, search, read, and synthesize information into comprehensive reports.
When to Use This Skill
Use this skill when:
- Performing market analysis
- Conducting competitive landscaping
- Creating literature reviews
- Doing technical research
- Performing due diligence
- Need detailed, cited research reports
Requirements
- Python 3.8+
- httpx:
pip install -r requirements.txt - GEMINI_API_KEY environment variable
Setup
- Get a Gemini API key from Google AI Studio
- Set the environment variable:
Or create aexport GEMINI_API_KEY=your-api-key-here.envfile 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
- User requests research → Run
--query "..." - Inform user of estimated time (2-10 minutes)
- Monitor with
--streamor poll with--status - Return formatted results
- Use
--continuefor follow-up questions
Exit Codes
- 0: Success
- 1: Error (API error, config issue, timeout)
- 130: Cancelled by user (Ctrl+C)
04 同仓库更多 Skills
wealthville-pool-scoring
Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter/Hold/Exit/Reduce/Avoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.
technical-debt-auditor
Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when the user mentions "code rot", "legacy cleanup", "refactoring priorities", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say "technical debt" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.
readonly-sql-guard
Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production/ERP/analytics database (a "query" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write/DDL/side-effect/transaction-escape risks. Checks what a statement CALLS, not just its shape.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
discernment-nudge
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.