deep-research-advance

Solid

Advanced one-shot deep research. Runs token-heavy web acquisition (Perplexity) and reasoning/verification (Kimi) headless in a script, then Claude audits the findings, writes a cited report, and optionally distills to Odin. Use for a deep, multi-source, fact-checked report on a PUBLIC-web topic. Trigger on "deep-research-advance", "advanced deep research", "deep research on [topic] with verification". Do NOT use for private/internal questions (the topic and corpus go to third-party clouds), quick lookups (use /osint or WebSearch), or Odin-brain-only recall (use /odin). BEFORE running, if the question is underspecified, ask 2-3 clarifying questions to narrow scope.

AI & Automation 11 stars 1 forks Updated 2 days ago Apache-2.0

Install

View on GitHub

Quality Score: 82/100

Stars 20%
36
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Deep research advance Multi-source, verified deep research. The headless script handles token-heavy acquisition (Perplexity) and reasoning/verification (Kimi). Claude takes the intermediate output, audits it, writes a cited report, and proposes an Odin distillate for human approval before anything reaches the brain. ## Guardrail (non-negotiable, state first) This skill sends the user's question and the gathered web corpus to third-party clouds: Perplexity (acquisition), Kimi (reasoning and verification). Both are outside the 31C data boundary. - **NEVER run on a private or internal topic.** CRM contacts, pipeline data, Odin brain content, Exchange mail, Telegram history, partner names, pricing -- none of these belong in the question text or in `--domains`. - If the request references private data, refuse immediately. Point to `/recall` (workspace-wide semantic memory) or `/odin` (brain-scoped reasoning) instead. - If in doubt whether a topic is public-web, ask before running. ## Phase 0 -- Scope If the question is underspecified -- no clear domain, no time horizon, no geography where those matter -- ask 2-3 focused clarifying questions before running. Examples worth asking: "Which jurisdiction's regulation?", "What time window?", "Vendor landscape or technical depth?" Do not pad; ask only what materially changes the research angle. Confirm the topic is public-web before proceeding. ## Phase 1 and 2 -- Run the headless script Run the acquisition and reasoning ...

Details

Author
mishahanin
Repository
mishahanin/heading-os
Created
2 months ago
Last Updated
2 days ago
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

deep-research

Deep research harness — fan-out web searches, fetch sources, adversarially verify claims, synthesize a cited report.

64,796 Updated yesterday
asgeirtj
AI & Automation Listed

deep-research

Agentic multi-source deep research via Tavily MCP, calibrated to Perplexity Deep Research (100+ sources on exhaustive runs). Load when the user wants a planned, source-graded research report — /deep-research, "deep research on X", "recherche approfondie sur X", "analyse multi-sources", "comparative analysis with sources". Do NOT load for single-fact lookups, known-URL extractions, library doc lookups (use tavily_skill), fanning out parallel research subagents for a quick gist with no plan (use superpowers:dispatching-parallel-agents), or quick research with no graded artifacts (use /research — this skill is the 7-phase pipeline emitting five NATO-graded, script-verified artifacts; it runs autonomously and only pauses to ask a clarifying question when the query is genuinely ambiguous).

1 Updated 3 weeks ago
hashbulla
AI & Automation Listed

deep-research

Deep research harness — fan-out web searches, fetch sources, adversarially verify claims, synthesize a cited report. When the user wants a deep, multi-source, fact-checked research report on any topic. BEFORE invoking, check if the question is specific enough to research directly — if underspecified (e.g., "what car to buy" without budget/use-case/region), ask 2-3 clarifying questions to narrow scope. Then pass the refined question as args, weaving the answers in.

8 Updated yesterday
ek33450505