deep-researchlisted

Deep, multi-source, fact-checked research reports — entirely on the Claude subscription, no API keys. Plans a TOC + acceptance criteria, fans out parallel Task subagents that search the live web (native WebSearch/WebFetch), gap-fills weak sections, then synthesizes a long-form report with inline [n] citations and a Sources list whose every URL is DETERMINISTICALLY verified against URLs that actually appeared in search results (fabricated citations are dropped). A subscription-only port of NVIDIA AI-Q's deep-research core. Use when the user wants a thorough researched report, a literature/landscape/market scan, a cited comparison, or "deep research" / "research X for me". BEFORE invoking, if the question is underspecified (e.g. "what car should I buy" with no budget/use/region), ask 2-3 clarifying questions to narrow scope, then research the refined question.
WillInvest/ClaudeX · ★ 4 · AI & Automation · score 80

Install: claude install-skill WillInvest/ClaudeX

# deep-research A subscription-only port of NVIDIA AI-Q's deep-research core (Apache-2.0 — see `NOTICE`). The **main agent is the orchestrator**: it plans, fans out parallel `Task` researchers that use native `WebSearch`/`WebFetch`, gap-fills, synthesizes a long-form cited report, and then runs a **deterministic** citation verifier so every `[n]` maps to a real, captured source URL. `$SKILL_DIR` below is this skill's directory; prompts live in `prompts/`, the verifier in `scripts/verify_citations.py`. Read each `prompts/*.md` when you reach its step. ## When to use Researched reports, landscape/market/literature scans, cited comparisons, "deep research on …", "research X and tell me the alternatives". Skip it for trivial chit-chat or pure factual one-liners (the router will route those to a direct answer / shallow pass). ## Flow **0. Route & disambiguate** — read `prompts/router.md`. Classify meta vs research, then shallow vs deep. For a plainly trivial question, answer directly. If the query is genuinely ambiguous and you can't pause for the user, state ONE interpretation line at the top of the report and proceed. **1. Set up a per-run working dir** — create a fresh run directory: `<vault>/<topic>/runs/<run-id>/`. Inside it create: - `<run-dir>/notes/` - `<run-dir>/yt-report/` - `<run-dir>/report_draft.md` - `<run-dir>/report_final.md` - `<run-dir>/audit.json` Prior runs are never verifier input. The lane must not write to persistent shared `notes/`; only the current