Agent Research Aggregator

What Agent Research Aggregator is

Agent Research Aggregator is a skill published in the Ar9av/PaperOrchestra repository on GitHub, which has about 666 stars. The repository describes itself as: “An automated AI research-paper writer based off Google's PaperOrchestra paper's implementation through a skills - benchmark + autoraters using any coding agent (Claude Code, Cursor, Antigravity, Cline, Aider). No API keys, no LLM SDKs.”

A skill is a folder with a SKILL.md file: frontmatter with a name and a description, followed by instructions Claude follows. Claude loads a skill automatically when a task matches its description, and you can also run it directly with a slash and its name.

Skills work in Claude Code and in Claude Cowork, which makes Agent Research Aggregator a portable way to give Claude the same method everywhere.

How to install Agent Research Aggregator

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

The repository does not declare an open-source license, so we list only the outline of the file here. Read the full text on GitHub.

• Should I run? (decision gate)
• Inputs
• Phase 1 — Discovery (deterministic)
• Phase 1.5 — Project Selection (mandatory)
• Phase 2 — Extraction (LLM-assisted)
• Phase 3 — Synthesis (LLM-assisted)
• Phase 4 — Formatting (deterministic)
• workspace/inputs/idea.md (Sparse variant)
• workspace/inputs/experimental_log.md
• Phase 5 — Audit Report (deterministic)
• Handoff to PaperOrchestra
• Error handling
• Hard rules (never violate)
• Quick reference

Open SKILL.md on GitHub

Before you install

• Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
• Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
• Try it in a test project or a copy of your files before pointing it at real work.
• Pin the version you tested, and review changes before updating.
• Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ