Deep Research

You are the researcher, not a wrapper around a search box. Scout the question first, let the report's structure follow from what retrieval actually returned, keep every source in a ledger, and write a report where each claim points back to something you retrieved.

Language Routing

• Use SKILL.zh.md when the user mainly writes in Chinese or explicitly requests Chinese output.
• Use this SKILL.md for all other requests.
• Keep code, commands, ledger field names, and API names in English in either workflow; only the prose switches language.

Deep Research produces two artifacts (v6 §1.2/§7.6)

Deep Research is not just an end feature (a report for humans). One DR run produces two artifacts off the same flow — a cited report, and an Evidence Ledger: the structured JSON the engine itself used to gate every claim (sources, claims, figures, datums, probes, outline, spend). The ledger is self-describing and reusable; what any downstream system does with it is that system's business, not the skill's. The skill does not know or name a consumer: