ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

paper-research-agent

Autonomous multi-agent paper research system. When user wants to research a topic, find related papers, or analyze academic literature, use this skill to orchestrate the full pipeline: intelligent search → PDF download → parallel agent analysis → comprehensive report generation. Triggers on: "research papers on X", "find related literature", "analyze papers", "调研论文", "查找相关文献", "分析论文", "帮我调研XXX领域"

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/changer-changer/paper-research-agent
Or

Paper Research Agent - Autonomous Multi-Agent Research System

When to Use

Use this skill when the user wants to:

  • Research papers on a specific topic
  • Find related literature for a research area
  • Analyze academic papers in depth
  • Build a literature survey
  • Identify research gaps
  • Compare methods across papers

Core Workflow

The system autonomously executes the full research pipeline:

User Query → Research Probe → PDF Download → Parallel Agent Analysis → Integrated Report

Phase 1: Research Probe (Automated)

  • Parse user's research intent from natural language
  • Execute vertical deep search or iterative exploration
  • Generate research graph with papers at different levels

Phase 2: PDF Download (Automated)

  • Download PDFs from arxiv
  • Deduplicate and version management
  • Standard naming: {paper_title}-{arxiv_id}.pdf

Phase 3: Parallel Agent Analysis (Automated - Key)

  • Spawn multiple sub-agents (one per paper)
  • Each agent reads full PDF using paper-reader
  • Generate 6-section detailed analysis
  • Agents run in parallel for speed

Phase 4: Report Integration (Automated)

  • Collect all agent analyses
  • Generate comparison tables
  • Identify research gaps
  • Output comprehensive survey

Agent Analysis Requirements

Each sub-agent MUST generate a 6-section report following the detailed standards in: references/analysis_standards.md

SubAgent MUST read this reference file before starting analysis to understand:

  • Detailed requirements for each of the 6 sections
  • Possible sub-sections to consider (as hints, not rigid requirements)
  • Quality checklists
  • How to use paper-reader tool
  • Report format template

Summary of 6 Required Sections

Section 1: Research Background

  • Domain context and research lineage
  • Key prior works cited (3-5 papers)
  • Technical state when this paper was published
  • Goal: Help user understand the research landscape

Section 2: Research Problem

  • Specific problem being solved
  • Limitations of existing methods (cite original text)
  • Core assumptions and insights
  • Goal: Clarify what problem the author identified

Section 3: Core Innovation

  • Detailed method/system architecture
  • Technical details (network structure, dimensions)
  • Key formulas in LaTeX format
  • Comparison table with prior methods
  • Goal: Understand exactly what the author did

Section 4: Experimental Design

  • Dataset details (name, scale, characteristics)
  • Baseline methods used
  • Evaluation metrics
  • REAL experimental data tables (copy from paper)
  • Ablation study results
  • Goal: Extract real data for comparison

Section 5: Key Insights

  • Core findings from experiments
  • Domain insights (what works/doesn't work)
  • Practical recommendations
  • Goal: Learn actionable lessons

Section 6: Future Work

  • Limitations acknowledged by authors
  • Unsolved problems
  • Potential research directions (at least 3)
  • Goal: Identify research gaps for user's innovation

Metadata

Stars3875
Views0
Updated2026-04-07
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-changer-changer-paper-research-agent": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.