google-deep-research
Skill0 starsChanged 9 months agoMITView on GitHub
Use Google's Deep Research API (Gemini) to conduct comprehensive, multi-source research that runs for 5-20 minutes server-side and produces detailed research reports. Use when the user asks for "deep research", thorough investigation of complex topics, market analysis, competitive landscaping, or any research requiring multiple web sources synthesized into comprehensive reports. This skill uses the Gemini Deep Research Agent API.
- Reads credentials
In this repository13 other files it gives its agents.
- agent-browserSkill
- bunny-netSkill
- changelogSkill
- company-researchSkill
- fikenSkill
- instagram-pipelineSkill
- ios-developmentSkill
- klarsprakSkill
- parallel-researchSkill
- soft-glass-uiSkill
- transcribeSkill
- transparency-generationSkill
- world-buildingSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use Google Deep Research when:
- Distinctive: line 19
Do NOT use for:
- Distinctive: line 58
Use Python to submit the query:
- Distinctive: line 171
If you have multiple API keys, rotate through them:
- Distinctive: line 233
Create a new API key
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Google Deep Research Skill
This skill provides access to Google's Deep Research API, which runs comprehensive research queries server-side for 5-20 minutes, searching multiple web sources and synthesizing findings into detailed reports.
When to Use This Skill
Use Google Deep Research when:
- User explicitly asks for "deep research" on a topic
- Research requires comprehensive multi-source investigation
- Topic needs 10+ web sources synthesized
- User wants a detailed report (5,000-40,000 chars)
- Standard web searches would be insufficient
Do NOT use for:
- Quick factual lookups (use WebSearch instead)
- Single-source questions
- Time-sensitive queries needing instant answers
API Configuration
Endpoint
POST https://generativelanguage.googleapis.com/v1beta/interactionsRequired Headers
Content-Type: application/json
x-goog-api-key: <API_KEY>Request Payload
{
"input": "Your detailed research query here",
"agent": "deep-research-pro-preview-12-2025",
"background": true
}Response (Success)
{
"id": "v1_ChdXXXXXXXXX...",
"status": "pending"
}Workflow
Step 1: Submit Research Query
Use Python to submit the query:
import requests
import json
API_KEY = "<user's API key>"
URL = "https://generativelanguage.googleapis.com/v1beta/interactions"
headers = {
"Content-Type": "application/json",
"x-goog-api-key": API_KEY
}
payload = {
"input": "Research query here - be specific and detailed",
"agent": "deep-research-pro-preview-12-2025",
"background": True
}
response = requests.post(URL, headers=headers, json=payload)
data = response.json()
interaction_id = data.get("id")
print(f"Started research: {interaction_id}")Step 2: Poll for Completion
Research takes 5-20 minutes. Poll the status:
import time
def check_status(interaction_id, api_key):
url = f"https://generativelanguage.googleapis.com/v1beta/interactions/{interaction_id}"
headers = {"x-goog-api-key": api_key}
while True:
resp = requests.get(url, headers=headers)
data = resp.json()
status = data.get("status") or data.get("state")
if status == "completed":
# Get the report text
outputs = data.get("outputs", [])
if outputs:
return outputs[-1].get("text", "")
return None
elif status in ["failed", "cancelled"]:
return None
else:
print(f"Status: {status} - waiting...")
time.sleep(30)Step 3: Save Results
Save the report to a markdown file with metadata:
from datetime import datetime
from pathlib import Path
def save_report(name, report_text, output_dir="research_results"):
Path(output_dir).mkdir(parents=True, exist_ok=True)
timestamp = datetime.now().strftime("%Y%m%d_%H%M%S")
filename = f"{name}_{timestamp}.md"
filepath = Path(output_dir) / filename
with open(filepath, "w") as f:
f.write(f"# Deep Research Report: {name}\n\n")
f.write(f"**Generated:** {datetime.now().isoformat()}\n\n")
f.write("---\n\n")
f.write(report_text)
return filepathQuery Design Best Practices
Good Queries
Be specific with names, locations, and what you want:
Research solar panel installations at Norwegian shopping centers including
Citycon properties, Steen & Strøm centers, and AMFI centers. For each,
find: building name, address, installation size (kWp), installer company,
and completion year. Search ESG reports, press releases, and sustainability reports.Bad Queries
Too vague:
Tell me about solar panels in NorwayInclude in Your Queries
- Specific entities - Company names, building names, locations
- Data fields needed - Address, size, date, installer, etc.
- Source hints - "Search ESG reports, press releases, LinkedIn..."
- Geographic scope - Cities, regions, countries
- Time frame - "2020-2024", "recent", etc.
Quota Management
Tier 1 Limits
- ~3 Deep Research queries per API key per day
- Rate limit resets at midnight Pacific Time
Multi-Key Strategy
If you have multiple API keys, rotate through them:
API_KEYS = [
"AIzaSy...", # Key 1
"AIzaSy...", # Key 2
"AIzaSy...", # Key 3
]
for key in API_KEYS:
response = submit_query(query, key)
if response.status_code == 200:
break
elif response.status_code == 429:
continue # Try next keyTracking Interactions
Maintain a JSON log to track all research jobs:
{
"started": "2025-01-01T00:00:00",
"interactions": [
{
"name": "research_topic_name",
"id": "v1_ChdXXXX...",
"started_at": "2025-01-01T00:00:00",
"status": "completed",
"api_key_used": "...last8chars",
"output_file": "path/to/report.md",
"report_length": 25000
}
]
}Error Handling
Common Errors
| Status | Meaning | Action |
| 400 | Invalid API key | Check key format, regenerate if needed |
| 429 | Quota exceeded | Use different API key or wait 24h |
| 500 | Server error | Retry after 1 minute |
Invalid API Key Response
{
"error": {
"code": 400,
"message": "API key not valid",
"status": "INVALID_ARGUMENT"
}
}Getting API Keys
- Go to https://aistudio.google.com/apikey
- Create a new API key
- Store securely (environment variable or secure storage)
Example: Full Research Script
See ~/.claude/skills/google-deep-research/deep_research.py for a complete implementation.
Output Format
Deep Research reports typically include:
- Executive summary
- Detailed findings organized by topic
- Source citations with URLs
- Data tables where applicable
- Recommendations or conclusions
Reports range from 5,000 to 40,000 characters depending on topic complexity.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

