AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Deep Research

skill-firstp1ck-pi-coding-agent-forge-deep-research · by Firstp1ck

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.

No reviews yet
0 installs
31 views
0.0% view→install

Install

$ agentstack add skill-firstp1ck-pi-coding-agent-forge-deep-research

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-firstp1ck-pi-coding-agent-forge-deep-research)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Deep Research? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

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:

[
  {
    "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:

| Tier | Sources | Flag | |---|---|---| | peer_reviewed | PubMed, Google Scholar | ✅ | | preprint | arXiv, bioRxiv, medRxiv | 📝 | | community | Reddit, StackExchange, forums | 🗨️ | | social | X/Twitter | 🐦 |

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

Write evidence to a JSON file:

[
  {
    "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:

| Verdict | Rule | |---|---| | Supported | >= 2 peer-reviewed sources, agreement ratio >= 0.8 | | Partially Supported | >= 1 peer-reviewed source, agreement ratio >= 0.5 | | Insufficient Evidence | 0 peer-reviewed sources or no evidence at all | | Contradicted | >= 1 contradicting source, agreement ratio `.

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: topicsummary, claims, evidencematrix, verdictsummary, decisiontrace, 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/rundeepresearch.py

| Arg | Required | Description | |---|---|---| | --topic | Yes | Research topic | | --topic-summary | No | Phase 1 summary text | | --claims-file | Yes | JSON file with structured claims | | --evidence-file | No | JSON file with pre-collected evidence | | --policy | Yes | Path to policy.json | | --schema | No | Path to output-schema.json | | --state | Yes | Path to state.json | | --output-json | No | Write JSON output to file | | --output-md | No | Write Markdown output to file |

| Exit Code | Meaning | |---|---| | 0 | Success | | 1 | Validation or policy error | | 2 | Upstream retrieval partial | | 3 | No-evidence fallback produced |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.