Skip to content
alyn
lingzhi227

Paper Assembly skill

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.

$npx skills add lingzhi227/agent-research-skills --skill paper-assembly
View this skill on GitHublingzhi227/agent-research-skills/skills/paper-assembly/SKILL.md
Pack stars
462
Pack installs
60k
Alyn Score
50/99
Updated
9 months ago
– views – installs via Alyn

lingzhi227

Paper Assembly

Install Paper Assembly

Pick your agent. Every command is ready to paste.

$npx skills add lingzhi227/agent-research-skills --skill paper-assembly

The open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.

01

Install it

Run the command above, or upload the folder in Claude.

02

Ask naturally

Describe the task. Your agent loads paper-assembly when the request matches its description.

03

Name it if needed

If it does not trigger, say “use the paper-assembly skill”. In Codex, type $paper-assembly.

The skill itself

SKILL.md

FolderGitHub

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

  1. Scan the paper directory for existing artifacts
  2. Identify which phases are complete vs pending
  3. 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 PDF
11. Review self-review PDF Review scores

Step 3: State Propagation

After each phase completes:

  1. Save output artifacts to the paper directory
  2. Propagate results to downstream phases
  3. 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

  1. Merge all sections into main.tex
  2. Verify all \includegraphics files exist
  3. Verify all \cite keys exist in .bib
  4. Compile to PDF
  5. 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

Tips for Paper Assembly

  • • Start a fresh session after installing so your agent picks up the new skill.
  • • This skill ships scripts. Read them before the first run, and run it in a project without secrets first.
  • • It bundles reference files. The agent reads them only when needed, so they cost no context until then.
  • • It is part of a pack with 30 skills. Install only the ones you need with --skill to keep triggers precise.
  • • If two skills overlap, mention the one you want by name.

Questions about Paper Assembly

What does the Paper Assembly skill do?

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.

How do I install Paper Assembly?

Run "npx skills add lingzhi227/agent-research-skills --skill paper-assembly" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.

Does Paper Assembly work in Cursor and Codex?

Yes. Paper Assembly uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.

Is Paper Assembly free?

Paper Assembly is open source on GitHub. It is free to install; check the license before commercial use.

Who made Paper Assembly?

Paper Assembly is published by lingzhi227 in the lingzhi227/agent-research-skills repository, together with 29 other skills.

Similar skills. From other creators.