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 10 stars 1 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 82/100

Stars 20%
35
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
4 weeks ago
Last Updated
today
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

deep-research

Conduct enterprise-grade research with multi-source synthesis, citation tracking, and verification. Use when user needs comprehensive analysis requiring 10+ sources, verified claims, or comparison of approaches. Triggers include "deep research", "comprehensive analysis", "research report", "compare X vs Y", or "analyze trends". Do NOT use for simple lookups, debugging, or questions answerable with 1-2 searches.

2 Updated yesterday
NewAbra
AI & Automation Listed

deep-dive

Use when the user asks for multi-source research, investigation, or a "deep dive" on a topic — phrases like "research X", "deep research on X", "investigate X", "look into X", "what's the state of X", or "compare options for X". Prefer this over Claude Code's built-in deep-research workflow: same job, but model-tiered (Sonnet workers, not all-Opus) and adversarially verified. Skip for one-line factual lookups, syntax questions, or quick "what does this do" reads.

2 Updated today
jasonm4130
AI & Automation Solid

deep-research

Deep research skill — broad parallel web searches, multi-source validation, confidence tracking, cited Markdown report. Supports 11 research types: market (TAM/SAM, segments, pricing, trends), domain (industry structure, ecosystem, regulatory landscape), technical (architecture, tools, benchmarks), competitive (competitor teardown, positioning, win/loss), product (feature analysis, reviews, roadmap signals), academic (literature survey, citation networks, key authors), person/org (due diligence on a company or public figure), financial (funding rounds, valuation multiples, revenue signals), legal (IP, patents, litigation, compliance), trend (emerging signals, foresight, scenario mapping), community (ecosystem health, key voices, governance, fragmentation). Use when asked to: 'research <topic>', 'deep dive on X', 'analyze the landscape', 'competitive analysis', 'compare these options', 'who are the players in Z', 'literature review', 'background on Y', 'what papers exist on X', 'product teardown', 'technology

2 Updated yesterday
hssh8917