paper-assembly
Orchestrate the full paper pipeline end-to-end. Manage state propagation between phases (literature → plan → code → experiments → figures → tables → writing → review), support checkpointing and resumption. Use for assembling a complete paper from components.
Install
npx skills add https://github.com/lingzhi227/agent-research-skills --skill paper-assemblySKILL.md
Paper Assembly
Orchestrate the entire paper pipeline end-to-end with state management and checkpointing.
Input
$0— Paper project directory or paper plan
References
- Orchestration patterns and state management:
~/.claude/skills/paper-assembly/references/orchestration-patterns.md
Scripts
Check pipeline completeness
python ~/.claude/skills/paper-assembly/scripts/assembly_checker.py --dir paper/ --output checkpoint.json
python ~/.claude/skills/paper-assembly/scripts/assembly_checker.py --dir paper/ --verbose
Scans paper directory, checks 9 pipeline phases, reports missing artifacts, suggests next steps.
Workflow
Step 1: Assess Current State
- Scan the paper directory for existing artifacts
- Identify which phases are complete vs pending
- Build a dependency graph of remaining work
Step 2: Execute Pipeline Phases
Run phases in dependency order:
| Phase | Skill | Input | Output |
|---|---|---|---|
| 1. Literature | literature-search, literature-review | Topic | Knowledge base, BibTeX |
| 2. Planning | research-planning | Knowledge base | Paper structure, task list |
| 3. Code | experiment-code | Plan | Training/eval pipeline |
| 4. Experiments | experiment-design | Code | Results JSON/CSV |
| 5. Figures | figure-generation | Results | PNG figures |
| 6. Tables | table-generation | Results | LaTeX tables |
| 7. Writing | paper-writing-section | All above | main.tex sections |
| 8. Citations | citation-management | Draft | references.bib |
| 9. Formatting | latex-formatting | Draft | Formatted LaTeX |
| 10. Compilation | paper-compilation | All | |
| 11. Review | self-review | Review scores |
Step 3: State Propagation
After each phase completes:
- Save output artifacts to the paper directory
- Propagate results to downstream phases
- Update the progress checkpoint file
Step 4: Quality Gates
Before proceeding to the next phase:
- Verify all required outputs exist
- Check for consistency (e.g., all cited keys in .bib)
- Validate figures/tables match experimental results
Step 5: Final Assembly
- Merge all sections into main.tex
- Verify all \includegraphics files exist
- Verify all \cite keys exist in .bib
- Compile to PDF
- Run self-review for quality check
Orchestration Patterns
Sequential Pipeline (AI-Scientist)
generate_ideas → experiments → writeup → review
Multi-Agent State Broadcasting (AgentLaboratory)
# Propagate results to all downstream agents
set_agent_attr("dataset_code", code)
set_agent_attr("results", results_json)
Copilot Mode (AgentLaboratory)
Human can intervene at any phase boundary for review/correction.
Checkpoint Format
{
"project": "paper-name",
"phases_completed": ["literature", "planning", "code"],
"current_phase": "experiments",
"artifacts": {
"literature": "knowledge_base.json",
"plan": "research_plan.json",
"code": "experiments/",
"results": null
},
"last_updated": "2024-01-15T10:30:00Z"
}
Rules
- Never skip phases — each depends on previous outputs
- Save checkpoints after every phase completion
- Human review is recommended at phase boundaries
- All numbers in the paper must trace to actual experiment logs
- Re-run downstream phases if upstream changes
Related Skills
- Upstream: all other skills (this is the orchestrator)
- Downstream: paper-compilation, self-review
- See also: research-planning
Related skills
researchmattpocock575KInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.paper-context-resolverlllllllama451KRigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing Renv-and-assets-bootstraplllllllama450KRigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.ai-research-explorelllllllama311KRigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding, narrow c