firstp1ck/pi-coding-agent-forge/deep-research

Claude Code and agent skill by firstp1ck/pi-coding-agent-forge

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

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.

Install

npx vskill@latest install firstp1ck/pi-coding-agent-forge/deep-research

SKILL.md

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

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/firstp1ck/pi-coding-agent-forge/deep-research/badge)](https://verified-skill.com/skills/firstp1ck/pi-coding-agent-forge/deep-research)

Something wrong with this skill or its page? Tell us.