Deep Research logo

Deep Research

Community
Firstp1ck
deep-research

Agents should invoke this skill for high-stakes or complex research needing multi-source evidence, scientific/technical fact-checking, decision traces, or rigorous verification. Runs deterministic two-phase research with schema/policy validation.

Overview

PublisherFirstp1ck
Repositorypi-coding-agent-forge
Skill namedeep-research
Stars
93
Forks
22
Bundled files
4
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.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Firstp1ck 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/Firstp1ck/pi-coding-agent-forge/tree/main/pi-skill-deep-research/skills/deep-research
  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/Firstp1ck/pi-coding-agent-forge.git /tmp/pi-coding-agent-forge
mkdir -p .claude/skills
cp -r /tmp/pi-coding-agent-forge/pi-skill-deep-research/skills/deep-research .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

Deterministic research pipeline that produces reproducible, schema-validated output. Same input + same state = same output.

Triggers

Activate when the user asks for rigorous multi-source research or uses any of these commands:

  • /deep-research [topic]
  • /deepresearch [topic]
  • /dpr [topic]
  • /dp [topic]
  • /dr [topic]

Quick Start

bash
S="{baseDir}/scripts"
B="{baseDir}"

# Full deterministic run (after claims + evidence are collected):
python3 $S/run_deep_research.py \
  --topic "Does caffeine improve focus?" \
  --topic-summary "Common belief that caffeine enhances concentration." \
  --claims-file /tmp/dr-claims.json \
  --evidence-file /tmp/dr-evidence.json \
  --policy $B/policy.json \
  --schema $B/output-schema.json \
  --state $B/state.json \
  --output-json /tmp/dr-output.json \
  --output-md /tmp/dr-output.md

Exit codes: 0 success, 1 validation/policy error, 2 partial retrieval, 3 no-evidence fallback.

Workflow

Phase 1: General Research (Agent-Driven)

Search the web to understand the topic. Identify up to 5 key claims to fact-check.

Write claims to a JSON file using this exact schema:

json
[
  {
    "claim_text": "Caffeine (100-300mg) improves sustained attention",
    "evidence_required": "RCTs or meta-analyses on caffeine and attention",
    "confidence_target": 0.7
  }
]

Required fields per claim: claim_text, evidence_required, confidence_target.

Phase 2: Scientific Fact-Check (Agent-Driven)

For each claim, search source databases in tier order:

TierSourcesFlag
peer_reviewedPubMed, Google Scholar✅
preprintarXiv, bioRxiv, medRxiv📝
communityReddit, StackExchange, forums🗨️
socialX/Twitter🐦

Evidence budget per claim: 2 peer-reviewed + 1 fallback (max 5 total).

Write evidence to a JSON file:

json
[
  {
    "claim_id": "C001",
    "sources": [
      {
        "title": "Effects of caffeine on cognitive performance",
        "authors": "Smith et al.",
        "year": 2020,
        "tier": "peer_reviewed",
        "url": "https://pubmed.ncbi.nlm.nih.gov/12345678",
        "citation": "Smith et al., \"Effects of caffeine on cognitive performance\", J. Neuroscience, 2020. https://pubmed.ncbi.nlm.nih.gov/12345678",
        "supports_claim": true,
        "relevance_note": "RCT showing improved reaction time at 200mg dose",
        "retrieved_at": "2026-02-26T10:00:00+00:00"
      }
    ]
  }
]

Important: Always trace secondary-source citations back to original papers.

Phase 3: Deterministic Classification (Runner)

Run the deterministic runner. It applies these verdict rules from policy.json:

VerdictRule
Supported>= 2 peer-reviewed sources, agreement ratio >= 0.8
Partially Supported>= 1 peer-reviewed source, agreement ratio >= 0.5
Insufficient Evidence0 peer-reviewed sources or no evidence at all
Contradicted>= 1 contradicting source, agreement ratio < 0.3

Every verdict includes a decision_trace entry with rule_id, inputs, and result.

Fallback Behaviors

All fallbacks are explicit and policy-defined. There is no implicit "best effort" path.

ConditionActionVerdict Cap
No peer-reviewed sources foundDescend to next tier in fallback orderpartially_supported max
No sources found at allEmit insufficient_evidenceinsufficient_evidence
Source database unreachableMark partial, continue with availableExit code 2
Cannot extract claims from topicReject run, require explicit claimsExit code 1

Fallback Text Blocks (Verbatim)

No peer-reviewed sources:

No peer-reviewed papers found on this specific claim. Checking alternative sources.

No sources at all:

No evidence found across any source tier for this claim.

Retrieval failure:

One or more source databases were unreachable. Results may be incomplete.

Claim extraction failure:

Could not extract structured claims from the topic. Provide explicit claims.

Output Contract

All outputs validate against output-schema.json. Required top-level fields: topic, run_id, policy_version, claims[], verdict_summary, decision_trace[], failures[].

Run IDs follow the pattern: dr-YYYYMMDDTHHMMSSZ-<8-char topic hash>.

Deterministic Ordering

  • Claims ordered by claim_id ascending (C001, C002, ...).
  • Evidence per claim ordered by: tier (highest first) -> recency (newest first) -> URL lexical.
  • Sections in fixed order: topic_summary, claims, evidence_matrix, verdict_summary, decision_trace, failures.

Source Priority

  1. Highest: Peer-reviewed journals (open access)
  2. Medium: Preprints (arXiv, bioRxiv) — flag as "not peer-reviewed"
  3. Low: Community discussions — flag as anecdotal
  4. Lowest: Social media — flag as unverified

Deduplication

Sources are deduped by composite key: title_normalized + canonical_url_host + publication_year. URLs are normalized by stripping query parameters and fragments.

File Inventory

skills/deep-research/
  SKILL.md              # This file
  policy.json           # Deterministic decision rules
  output-schema.json    # JSON Schema for output validation
  state.json            # Run history, dedupe fingerprints, claim canonicalization
  scripts/
    ./scripts/run_deep_research.py  # Deterministic runner (collect/normalize/classify/render/validate)
  tests/
    fixtures/             # Test input fixtures
    ./tests/test_determinism.py   # Reproducibility and schema tests

Scripts Reference

./scripts/run_deep_research.py

ArgRequiredDescription
--topicYesResearch topic
--topic-summaryNoPhase 1 summary text
--claims-fileYesJSON file with structured claims
--evidence-fileNoJSON file with pre-collected evidence
--policyYesPath to policy.json
--schemaNoPath to output-schema.json
--stateYesPath to state.json
--output-jsonNoWrite JSON output to file
--output-mdNoWrite Markdown output to file
Exit CodeMeaning
0Success
1Validation or policy error
2Upstream retrieval partial
3No-evidence fallback produced

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Deep Research AI skill do?

Agents should invoke this skill for high-stakes or complex research needing multi-source evidence, scientific/technical fact-checking, decision traces, or rigorous verification. Runs deterministic two-phase research with schema/policy validation.

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/Firstp1ck/pi-coding-agent-forge/tree/main/pi-skill-deep-research/skills/deep-research. TypingMind reads its SKILL.md and bundles its files 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 Firstp1ck 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 👇