Deep Research logo

Deep Research

Organization
shobcoder
deep-research

GOD MODE deep research skill. Multi-phase autonomous research loop: query decomposition → multi-source crawling → claim cross-referencing → conflict resolution → structured synthesis with inline citations. Use for any question that demands depth, sourcing, and verifiable accuracy.

Overview

Publishershobcoder
Repositoryshob
Skill namedeep-research
Stars
576
Forks
3
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by shobcoder on GitHub. Read the source before you install it.

Installation

Install the Deep Research AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/shobcoder/shob/tree/main/skills/research-knowledge
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/shobcoder/shob.git /tmp/shob
mkdir -p .claude/skills
cp -r /tmp/shob/skills/research-knowledge .claude/skills/deep-research
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Deep Research in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Deep Research on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Deep Research is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Deep Research — GOD MODE

Trigger

/deep-research <query> or when user says "research this deeply", "go deep on", "full research report on", "investigate this thoroughly".

Core Philosophy

Raw search results are noise. Verified synthesis is signal. Every claim needs a source. Every conflict needs a resolution. A great deep research report is a structured intelligence brief, not a search summary.

Architecture

Query
  └── Phase 1: Decompose → Sub-questions
        └── Phase 2: Parallel Search → Raw Sources
              └── Phase 3: Crawl & Extract → Claims
                    └── Phase 4: Cross-Reference → Verify / Conflict
                          └── Phase 5: Synthesize → Report
                                └── Phase 6: Quality Gates → Deliver

Phase 1 — Query Decomposition

Break the user's query into 3–7 atomic sub-questions. Each must be:

  • Independently searchable
  • Non-overlapping with others
  • Ordered from foundational to advanced

Example:

Query: "Is Company X profitable?"

Sub-questions:

  1. What is Company X's current revenue model?
  2. What are its reported ARR and revenue figures?
  3. What is its burn rate and cost structure?
  4. What do investors say about its path to profitability?
  5. How does it compare to competitors on unit economics?

Phase 2 — Multi-Source Search Strategy

For each sub-question, issue 2–4 targeted searches using varied query angles:

[primary term] [year]
[primary term] site:official OR filetype:pdf
[primary term] analysis OR breakdown OR report
[primary term] vs [competitor]

Source Priority Tiers:

TierTypeTrust Weight
1Official docs, SEC filings, company blogs, government data, peer-reviewed papers1.0
2Major news outlets (Reuters, Bloomberg, FT), industry analysts (Gartner, CB Insights)0.85
3Tech blogs, newsletters, podcasts0.65
4Forums, Reddit, social media0.40

Minimum sources per report: 8 unique domains Target for complex topics: 15–25 sources


Phase 3 — Deep Crawl and Extraction

For each source, fetch the full page (not just the snippet), then extract structured claims:

  • Numerical facts (stats, dates, prices, percentages)
  • Named entities (people, companies, products)
  • Causal claims ("X caused Y because Z")
  • Comparative claims ("A is better than B")

Tag each claim with source URL, publish date, tier rating, and a paraphrase or verbatim quote under 15 words.

Extraction template per source:

yaml
source: https://example.com/article
published: 2026-04-12
tier: 2
claims:
  - text: "Company reached $100M ARR in Q1 2026"
    type: numerical
    confidence: high
  - text: "CEO stated profitability target by 2027"
    type: causal
    confidence: medium

Phase 4 — Cross-Reference and Conflict Resolution

4a. Claim Clustering

Group identical or related claims across sources. If 3+ Tier 1–2 sources agree, mark as Verified.

4b. Conflict Detection

Flag claims where sources contradict each other:

CONFLICT DETECTED
  Claim A: "Revenue is $50M ARR" — Source A, 2026-01
  Claim B: "Revenue is $80M ARR" — Source B, 2026-03
  Resolution: Use most recent Tier 1–2 source. Note discrepancy in report.

4c. Gap Detection

If a sub-question has zero Tier 1–2 sources, mark it [unverified] and flag it in the report.

4d. Confidence Scoring

Confidence = (sum of tier_weights x recency_factor) / num_claims

recency_factor:
  < 30 days:   1.0
  30–90 days:  0.9
  3–12 months: 0.75
  > 1 year:    0.60

Phase 5 — Report Synthesis

Report Structure

markdown
# [Topic] — Deep Research Report

> Researched: [date] | Sources: [N] | Confidence: [X]% | Sub-questions: [N]

---

## Executive Summary

2–4 sentence synthesis of the most important findings.
Lead with the single most important fact.

---

## Table of Contents

1. [Sub-question 1 title](#anchor)
2. [Sub-question 2 title](#anchor)
...
N.   Conflicts and Uncertainties
N+1. Sources

---

## 1. [Sub-question Title]

### Finding
One clear, direct answer to the sub-question.

### Evidence
- [Claim] — Source: [Name], [Date], Tier 1
- [Claim] — Source: [Name], [Date], Tier 2
- [Claim] — Source: [Name], [Date], unverified

### Confidence: [X]% | Coverage: [N] sources

---

## [Repeat for each sub-question]

---

## Conflicts and Uncertainties

| Topic | Claim A | Claim B | Resolution |
|-------|---------|---------|------------|
| Revenue | $50M (Source A) | $80M (Source B) | Use Source B (more recent) |

---

## Knowledge Gaps

- [Field X]: No Tier 1–2 sources found. Flagged as unverified.
- [Field Y]: Only sources older than 12 months available.

---

## Research Metadata

| Metric | Value |
|--------|-------|
| Total sources | N |
| Tier 1–2 sources | N |
| Sub-questions answered | N / N |
| Average confidence | X% |
| Date range of sources | YYYY-MM to YYYY-MM |
| Conflicts detected | N |
| Gaps flagged | N |

---

## Sources

| # | URL | Type | Tier | Date | Used For |
|---|-----|------|------|------|----------|
| 1 | https://... | Official | 1 | 2026-05-01 | Revenue data |
| 2 | https://... | News | 2 | 2026-04-10 | Funding round |

Phase 6 — Quality Gates

Run all checks before delivering the report. Fail = do not deliver until resolved.

GateRequirementAction if Fail
Source minimum8+ unique domainsRun additional search passes
Tier coverage40%+ Tier 1–2 sourcesFlag low-quality sourcing in report
Conflict resolutionAll conflicts documentedAdd to conflicts table
Gap flaggingAll unanswered sub-questions notedAdd to gaps section
Citation accuracyEvery claim has a sourceRemove or flag orphan claims
Recency50%+ sources within 12 monthsFlag stale data in report

Output Modes

Use a flag in the trigger to switch modes:

FlagModeDescription
(none)StandardFull report as specified above
[academic]AcademicAdds abstract, methodology, limitations, further research
[brief]Quick BriefExecutive summary + top 5 facts + source list. Max 300 words
[compare]ComparisonSide-by-side table of N items across shared dimensions

Iteration Protocol

If confidence is below 70% after the first pass:

ITERATION 2:
  - Re-run searches with refined queries
  - Target gaps identified in Phase 4
  - Fetch Tier 1 sources directly (company.com, arxiv.org, gov sites)
  - Update confidence scores
  - Note in report: "This section required 2 research iterations"

Maximum iterations: 3
If confidence remains below 60% after 3 iterations, deliver with prominent uncertainty warnings.

Anti-Hallucination Rules

  1. Never invent a statistic. If a number is not sourced, write [no data found].
  2. Never paraphrase into a stronger claim. If a source says "may reach", do not write "will reach".
  3. Never merge two sources' claims into one sentence without attributing both.
  4. Never omit a conflict because it is inconvenient — surface it in the conflicts table.
  5. Date every claim. Undated claims receive a recency penalty in confidence scoring.
  6. If uncertain, say so explicitly using [unverified] or [disputed] inline tags.
  7. Never reproduce more than 15 words verbatim from any single source.

Trigger Examples

/deep-research What is the current state of fusion energy?
/deep-research [academic] Impact of LLMs on scientific paper quality
/deep-research [compare] React vs Vue vs Svelte for large-scale apps
/deep-research [brief] What caused the 2023 banking crisis?

Skill Outputs

FileDescription
{topic}/report.mdFull research report
{topic}/sources.yamlStructured source list with tier ratings
{topic}/claims.yamlAll extracted claims with provenance
{topic}/conflicts.mdConflict log with resolutions
{topic}/metadata.jsonConfidence scores, coverage stats, iteration log

Frequently asked questions

What does the Deep Research AI skill do?

GOD MODE deep research skill. Multi-phase autonomous research loop: query decomposition → multi-source crawling → claim cross-referencing → conflict resolution → structured synthesis with inline citations. Use for any question that demands depth, sourcing, and verifiable accuracy.

Why use Deep Research on TypingMind?

Because you install it once and use it with any model. Deep Research is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Deep Research in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/shobcoder/shob/tree/main/skills/research-knowledge. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Deep Research?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Deep Research?

As many as you like. As long as a model supports skills, you can use Deep Research with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Deep Research AI skill free?

Yes. It is published on GitHub by shobcoder under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇