| name | deep-research |
| display_name | Deep Research |
| short_description | Multi-round web research with cross-source verification and cited markdown report |
| description | Run an iterative deep-research workflow — reformulate the query, search multiple times with refined terms, summarise each source, cross-check for contradictions, and produce a markdown report with inline citations. |
Deep Research
Use this skill when the user asks for a "deep dive", "research", "调研", "deepsearch", or otherwise needs a synthesized report drawing on multiple web sources.
Workflow
Run the steps below in order. Do not skip steps; do not collapse them into a single search.
1. Clarify scope (skip only if unambiguous)
Restate the question in one sentence. If the question is broad (e.g. "research X"), ask the user one focused clarifying question covering: time range, depth, audience, output format. If the user has already specified these, skip.
2. Plan sub-queries
Decompose the question into 3–6 sub-queries that together cover the topic. Examples:
- definition / background
- current state / latest developments (include year)
- comparisons / alternatives
- criticisms / failure modes
- primary sources (papers, docs, vendor pages)
Write the list as a numbered plan before searching.
3. Search iteratively
For each sub-query:
- Call the web search tool with terms that include the current year when recency matters.
- Open the top 2–4 results that look authoritative (primary sources > aggregators > blogs).
- Extract: title, URL, publish date, 3–6 bullet key points, any numbers / quotes verbatim.
- If a result contradicts an earlier source, run a follow-up search to disambiguate before moving on.
Do not rely on a single source per sub-question.
Tool-budget rules (CRITICAL — do not skip)
- Never call
browser_snapshot during deep research. Full a11y snapshots are tens of KB each and stack across turns; a few of them blow past Azure's per-request output cap and the upstream returns response.failed, which the user sees as "Reconnecting…". Use browser_evaluate with () => document.title + '\n' + document.body.innerText.slice(0, 4000) instead. Always slice the text to ≤ 4000 chars per page.
- Never take screenshots during research. Text only.
- Per page: at most one
browser_navigate + one browser_evaluate. Then move on.
- Per turn: hard cap at 20 tool calls. If you cannot finish, write the report with what you have and clearly mark the gaps under "Open questions".
- Prefer native
web_search if available. Use Playwright only to read a specific URL the search results gave you.
- After every 5 tool calls, take stock: do you have enough to write the report? If yes, stop searching and write.
4. Cross-check
After all sub-queries, build a small contradictions table:
| Claim | Source A | Source B | Resolution |
|---|
If a claim only appears in one source, mark it single-source. Do not promote single-source claims to the executive summary.
5. Produce the report
Output a single markdown document with:
- Executive summary — 3–6 bullets, each ending with a
[n] citation.
- Background — what the topic is and why it matters.
- Findings — one subsection per sub-query, each with bulleted facts +
[n] citations.
- Disagreements & open questions — from the cross-check table.
- References — numbered list of
[n] Title — URL (publish date).
Rules for the report:
- Every non-obvious claim has a
[n] citation pointing at the References list.
- No marketing language. No speculation presented as fact.
- Quote numbers verbatim from the source; do not round silently.
- If the user gave a language preference, write the report in that language; otherwise mirror the user's input language.
6. Self-critique pass
Before returning, re-read the report and check:
Fix issues before returning.
When NOT to use this skill
- Quick factual lookups ("what is the current version of X") — answer directly.
- Code-writing tasks — use the developer skills instead.
- Internal-only questions that the web cannot answer — say so and ask the user for sources.
Output artifact (optional)
If the user asks for a deliverable file (e.g. "save it as a doc"), pass the final markdown to the office / documents skill to materialise it; otherwise return the markdown inline in the chat.
