Deep Research
glebis/claude-skills
This skill should be used when conducting comprehensive research on any topic using the OpenAI Deep Research API.
Deep, multi-source, fact-checked research on a topic — fan out searches, read primary sources, adversarially verify each claim, and synthesize a cited report.
Install Deep Research
$ npx skills add open-octo/octo-agent --skill deep-research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install open-octo/octo-agent deep-research --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/open-octo/octo-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/internal/skills/defaults/deep-research .claude/skills/deep-research && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deep-research" agent skill from https://github.com/open-octo/octo-agent/tree/main/internal/skills/defaults/deep-research into .claude/skills/deep-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-research", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/open-octo/octo-agent/tree/main/internal/skills/defaults/deep-researchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add open-octo/octo-agent --skill deep-research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install open-octo/octo-agent deep-research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-octo/octo-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/internal/skills/defaults/deep-research .agents/skills/deep-research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deep-research" agent skill from https://github.com/open-octo/octo-agent/tree/main/internal/skills/defaults/deep-research into .agents/skills/deep-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-research", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add open-octo/octo-agent --skill deep-research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install open-octo/octo-agent deep-research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-octo/octo-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/internal/skills/defaults/deep-research .cursor/skills/deep-research && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deep-research" agent skill from https://github.com/open-octo/octo-agent/tree/main/internal/skills/defaults/deep-research into .cursor/skills/deep-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-research", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/open-octo/octo-agent.git --path internal/skills/defaults/deep-research--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add open-octo/octo-agent --skill deep-research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install open-octo/octo-agent deep-research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-octo/octo-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/internal/skills/defaults/deep-research .gemini/skills/deep-research && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deep-research" agent skill from https://github.com/open-octo/octo-agent/tree/main/internal/skills/defaults/deep-research into .gemini/skills/deep-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-research", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install open-octo/octo-agent deep-researchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add open-octo/octo-agent --skill deep-research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/open-octo/octo-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/internal/skills/defaults/deep-research .github/skills/deep-research && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deep-research" agent skill from https://github.com/open-octo/octo-agent/tree/main/internal/skills/defaults/deep-research into .github/skills/deep-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-research", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add open-octo/octo-agent --skill deep-research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install open-octo/octo-agent deep-research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/open-octo/octo-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/internal/skills/defaults/deep-research .opencode/skills/deep-research && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deep-research" agent skill from https://github.com/open-octo/octo-agent/tree/main/internal/skills/defaults/deep-research into .opencode/skills/deep-research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deep-research", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
deep-research- GitHub stars
- 125
- Token cost
- ~1.5k tokens
- SKILL.md length
- 808 words
- Files
- 1
- Skills in repo
- 40
- Repo updated
- First seen
- Licence
- MIT
At a glance
Deep, multi-source, fact-checked research on a topic — fan out searches, read primary sources, adversarially verify each claim, and synthesize a cited report.
- Works in 5 steps: Scope before you search → Fan out — breadth → Go to the source — depth → …
- The user wants a thorough research report rather than a quick answer
- SKILL.md covers 0. Scope before you search, 1. Fan out — breadth, 2. Go to the source — depth and 3. Adversarial verify — try to…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Deep Research is an agent skill from open-octo/octo-agent. Deep, multi-source, fact-checked research on a topic — fan out searches, read primary sources, adversarially verify each claim, and synthesize a cited report. Use when the user wants a thorough research report rather than a quick answer, e.g. "深度调研", "research this properly", "写一份调研报告", "帮我系统调研", "多来源核实", "give me a researched writeup", "背景调查一下". BEFORE starting, if the question is underspecified (scope, region, time window, use-case unclear), ask 2-3 clarifying questions to narrow it. For a single quick lookup…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Deep research, Web search and Requirements gathering. The repository describes itself as: Open-source, single-binary, self-hosted AI agent — your models and data stay on your machine. A coding agent on par with Claude Code and a personal assistant lighter than… The licence is MIT.
When your agent uses it
- The user wants a thorough research report rather than a quick answer
- Tasks that involve Deep research
- Tasks that involve Web search
Example prompts
- “research this properly”
- “写一份调研报告”
- “帮我系统调研”
- “/deep-research”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit fc1385f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Deep Research loads about 1.5k tokens when it runs. Until then it costs about 153 tokens; SKILL.md has 808 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from open-octo/octo-agent at commit fc1385f, republished under its MIT licence (© open-octo). 808 words, ~1,518 tokens.
Download SKILL.mdSave it as
.claude/skills/deep-research/SKILL.md (or your agent's skills folder).- name
- deep-research
- description
- Deep, multi-source, fact-checked research on a topic — fan out searches, read primary sources, adversarially verify each claim, and synthesize a cited report. Use when the user wants a thorough research report rather than a quick answer, e.g. "深度调研", "research this properly", "写一份调研报告", "帮我系统调研", "多来源核实", "give me a researched writeup", "背景调查一下". BEFORE starting, if the question is underspecified (scope, region, time window, use-case unclear), ask 2-3 clarifying questions to narrow it. For a single quick lookup use web_search directly; for a whole codebase/feature use the relevant dev skills.
- license
- MIT
Skill: deep-research
A harness for research you can trust: breadth first (many angles), then depth
(primary sources), then an adversarial pass that tries to break each claim
before it goes in the report. Built on octo's native tools — web_search,
web_fetch, sub_agent, and (for login-gated / JS-rendered / anti-bot sites)
the browser tool via the web-access skill. No external services.
The goal is a cited report where every non-obvious claim traces to a source you actually read — not a plausible-sounding summary of search snippets.
0. Scope before you search
Research is only as good as the question. Before any tool call, confirm you can state the deliverable: what question, what decision it informs, what time window, what region/market, what depth. If any of these is missing and would change the answer, ask 2-3 sharp clarifying questions first — don't guess a scope and burn a fan-out on the wrong one.
Then write down, in one line, what "done" looks like. That line is the acceptance criterion the final report is checked against.
1. Fan out — breadth
Decompose the question into 4-8 independent sub-questions, each attacking a different angle (definition, current state, competing views, data/numbers, history, criticisms, primary actors). Independence matters: overlapping sub-questions waste the fan-out.
Dispatch them in parallel. web_search / web_fetch are stateless, so this is
exactly the case sub-agents are for:
- One
sub_agentper sub-question. Prompt it goal-first, not step-first: describe what to find out, not "search for X" — an anti-bot source may needbrowseron the main site, and "search" would anchor the sub-agent toweb_search. - Tell each sub-agent to load the
web-accessskill and follow it, to return findings with source URLs, and to flag anything it couldn't verify. - Do NOT parallelize
browserwork — the browser session is single-page and process-shared; concurrent sub-agents fight over one page. Keep browser interaction to a single sequence; parallelize only the stateless search/fetch.
If sub_agent is unavailable in this session, run the sub-questions sequentially
inline and say so.
2. Go to the source — depth
Search engines and aggregators are a discovery entry point, not proof. N outlets quoting the same wrong number is circular, not corroboration. For every claim that matters, reach the primary source and read it:
| Claim type | Primary source |
|---|---|
| Policy / regulation | Issuing body's official site |
| Company announcement | The company's own newsroom / filing |
| Academic / scientific | The original paper or the institution |
| Product capability / API | Official docs or source, not blog posts |
| Statistics | The dataset publisher, not the article citing it |
Use web_fetch on the source URL to pull the page as clean Markdown — pass the
raw URL; it fetches directly and extracts the main content for you. When the
source is behind a login, renders via JS, or blocks fetching, switch to
browser per web-access.
When no official source exists, an original report from an authoritative outlet (not a reprint) can serve as a secondary basis — but say so explicitly: "No official source found; the following relies on [outlet]'s reporting and may carry transcription error."
Show full SKILL.md (316 more words)Show less
3. Adversarial verify — try to break each claim
This is what separates research from a summary. For each load-bearing claim, run a skeptical pass before trusting it:
- Does the source actually say this, or is it the article's spin on it?
- Is the source primary, or is it echoing someone else? Trace one hop back.
- Is it current, or superseded? Note the date on every source.
- Do independent sources disagree? Surface the disagreement — don't average it away.
For high-stakes claims, dispatch a verifier sub_agent prompted to refute
the claim (default to "unverified" when uncertain), not to confirm it. A claim
that survives an honest attempt to break it is worth reporting; one that doesn't
gets dropped or flagged as contested.
Track claim → source as you go. Anything you can't attribute to a source you read does not enter the report as fact — at most as a clearly-labelled open question.
4. Synthesize — the cited report
Structure to the deliverable from step 0, not a fixed template. Typical shape:
- Bottom line — the answer to the question, up front, in a few sentences.
- Findings — organized by sub-question or theme, each key claim carrying an inline source (title + URL). Present genuine disagreement as disagreement.
- Confidence & gaps — what's well-established, what's thin or single-sourced, what you couldn't resolve. State this honestly; a known gap is more useful than false certainty.
- Sources — the primary sources you actually read, deduped.
Then check the report against the step-0 acceptance line. If it doesn't answer the question, name what's still missing rather than padding.
Completeness check
Before finishing, ask: what's missing? A sub-question not run, a claim asserted but never traced to a source, a contradiction glossed over, a source cited but not read. Whatever that surfaces is the next round — loop back to step 1 for it, don't ship around it. Stop when the acceptance criterion is met, not before, and don't over-research past it.
© open-octo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in internal/skills/defaults/deep-research of open-octo/octo-agent.
Open the folder on GitHubat commit fc1385f
Compare with similar skills
Deep Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deep Research this skillopen-octo/octo-agent | 125 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Deep Researchglebis/claude-skills | 389 | — | ~2.6k | Automated safety check: Notes | MIT | |
| Web ResearchJuncai22/spring-ai-agent-learning | 123 | 3 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Deep Web Research Methodbytedance/deer-flow | 83k | 5 repos | ~2k | Automated safety check: Pass | MIT | |
| Bmad Deep Recondelorenj/mcp-server-trello | 445 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Net Deep Researchh4444433333/net-deep-research | 123 | — | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Web Research
Juncai22/spring-ai-agent-learning
A skill your agent uses for requests related to web research; it provides a structured approach to conducting comprehensive web research
Deep Web Research Method
bytedance/deer-flow
Replaces single quick searches with a staged research routine of broad survey, targeted deep dives and cross-checking, run before the agent writes anything that needs facts.
Bmad Deep Recon
delorenj/mcp-server-trello
Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill…
Net Deep Research
h4444433333/net-deep-research
Runs cross-source web research to verify whether an online claim is true, distinguishing confirmed facts from rumor, marketing claims or stale information.
Ray Trend Search
imraywang/rayskills
Researches what people are saying about a topic over a recent window across X, Reddit, YouTube and the public web, reporting each source's status with links.
More from open-octo/octo-agent
All 40 skills in this repoImage Gen
open-octo/octo-agent
Acquire images as files — generate them with an AI image model (14 providers: OpenAI/gpt-image, Gemini, Qwen, Zhipu, Volcengine, Stability, FLUX, Ideogram, MiniMax, and more), search openly-licensed…
Office XLSX
open-octo/octo-agent
Create, read, and edit Excel (.xlsx) spreadsheets programmatically with openpyxl — cell values, formulas, styling (fonts/fills/borders/alignment/number formats), merged cells, multiple sheets…
Artifact Design
open-octo/octo-agent
Design guidance for any HTML/Markdown file shown in octo's Artifacts panel — reports, dashboards, architecture/system diagrams, generated UIs, slide-style pages, 3D scenes.
Code Review
open-octo/octo-agent
Review local code changes. An agent skill from open-octo/octo-agent.
Ppt Master
open-octo/octo-agent
AI-driven multi-format SVG content generation system. An agent skill from open-octo/octo-agent.
Config Setup
open-octo/octo-agent
Configure octo's global settings through guided conversation — set up AI model endpoints (providers, API keys, models), adjust agent defaults (reasoning effort, permission mode, coauthor, workspace…
Related
Categories
Questions about Deep Research
What does Deep Research do?
Deep, multi-source, fact-checked research on a topic — fan out searches, read primary sources, adversarially verify each claim, and synthesize a cited report. Deep Research is an agent skill from open-octo/octo-agent. Deep, multi-source, fact-checked research on a topic — fan out searches, read primary sources, adversarially verify each claim, and synthesize a cited report.
When should I use Deep Research?
Deep Research fits situations like: the user wants a thorough research report rather than a quick answer; tasks that involve Deep research; tasks that involve Web search.
How do I install Deep Research in Claude Code?
Run `npx skills add open-octo/octo-agent --skill deep-research -a claude-code`. Or copy the skill folder (internal/skills/defaults/deep-research in open-octo/octo-agent) into .claude/skills/deep-research in your project. Claude Code loads it when a task matches its description.
How do I install Deep Research in Codex?
Run `npx skills add open-octo/octo-agent --skill deep-research -a codex`. Or copy the skill folder (internal/skills/defaults/deep-research in open-octo/octo-agent) into .agents/skills/deep-research in your project. Codex loads it when a task matches its description.
Can I use Deep Research in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add open-octo/octo-agent --skill deep-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deep-research, .gemini/skills/deep-research, .github/skills/deep-research and .opencode/skills/deep-research in your project.
What does Deep Research need to run?
SKILL.md names no scripts, command-line tools or credentials: Deep Research is instructions for the agent only.
Does Deep Research access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Deep Research safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Deep Research use?
Deep Research is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Deep Research use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Deep Research?
Skills that share tags, products or a category with Deep Research: Deep Research (glebis/claude-skills, 389 stars), Web Research (Juncai22/spring-ai-agent-learning, 123 stars), Deep Web Research Method (bytedance/deer-flow, 83k stars) and Bmad Deep Recon (delorenj/mcp-server-trello, 445 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Deep Research?
open-octo (a GitHub organization) maintains it in open-octo/octo-agent, which has 125 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 8, 2026.
Source: open-octo/octo-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.