Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Documents

paper-spine

Write, rewrite, or build a paper or report (journal, conference, report, review, competition) end to end, then output LaTeX/PDF/Word. Contribution-first, reviewer-aware.

WUBING2023 · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add WUBING2023/PaperSpine --skill paper-spine

About this skill


name: paper-spine description: Write, rewrite, or build a paper or report (journal, conference, report, review, competition) end to end, then output LaTeX/PDF/Word. The main PaperSpine entry point that orchestrates every step.

PaperSpine Orchestrator

Use this skill as the suite entrypoint. PaperSpine exposes one main skill: paper-spine. Each stage is executed by reading the corresponding playbook under references/.

Update detection: If the user asks to update, upgrade, or check for updates, read references/update.md and execute without starting the full writing workflow.

Command Routing

TriggerRead
Default / full workflowThis file (Non-Negotiable Route below)
resume / continue / "continue from"references/resume.md
update / "check for updates"references/update.md
submission / "submission materials"references/submission.md
auditreferences/audit.md
translatereferences/translate.md
humanizereferences/humanize.md
respond / response letter / reviewer commentsreferences/respond.md

For fine-grained stage execution, the orchestrator reads the playbook for each stage from references/ rather than requiring a separate skill invocation:

StagePlaybook
Intake / configreferences/intake.md
Resume / checkpointreferences/resume.md
Researchreferences/research.md
Citationreferences/citation.md
Rewritereferences/rewrite.md
Buildreferences/build.md
Humanizereferences/humanize.md
LaTeXreferences/latex.md
Translatereferences/translate.md
Respondreferences/respond.md
Auditreferences/audit.md

Historical worker skill names (paper-spine-research, etc.) are legacy only and are not user entry points.

Operating Principle

PaperSpine is a research-writing workflow, not a prose patcher. Its job is to learn the target scene and strong examples first, force a user-confirmed motivation, design the paper row by row, and only then write or rebuild the manuscript.

Never fabricate data, metrics, p-values, datasets, citations, figures, or experimental claims. User materials are authoritative for this paper's results. External examples teach structure and rhetoric only.

Contribution-First, Reviewer-Aware Rules (V4)

These three rules sit above the motivation thread. Motivation remains required, but it supports the contribution rather than replacing it.

  1. Contribution-First. The manuscript's highest-priority organizing unit is the confirmed contribution. Do not begin substantive writing until confirmed_contribution.md exists (what the paper adds, what problem/gap/ challenge makes it necessary, what evidence validates it, what claim boundary to respect, why a reviewer should find it publishable). Template + per-section checklists: references/contribution.md. Gate: contribution_check.py.
  2. Results-as-Validation. Each major Results subsection must validate at least one contribution promise; metric-only units with no contribution mapping are a failure. Record this in results_validation.md. Template: references/results-validation.md. Gate: results_validation_check.py (journal / conference / competition scenes).
  3. Reviewer-Aware. Before claiming submission-ready, create reviewer_audit.md (reviewer value map + objection register + editorial fit), populating the objection register from the three structured_review reviewer agents. Template: references/reviewer-audit.md. Gate: reviewer_audit_check.py.

The Stage 12 Final Audit hard gate runs all three checks; do not declare the work complete while any of them fails.

User-Facing Language

When the user writes in Chinese, ui_language=zh, output_language=zh, or translation_package=zh, all user-facing communication must be in Chinese throughout the whole run, not only in the final completion report. This includes intermediate progress updates, status bullets, tool-result summaries, blocked messages, gate re-run notes, final delivery tables, and error explanations.

Do not write English progress sentences such as "Chinese .docx generated", "Now writing the word report", "All stages passed", "Deliverables", or "PaperSpine Workflow Complete" in those Chinese-facing runs. Use Chinese status phrases instead, for example:

  • 中文 Word 文档已生成:final_paper/paper.zh.docx。正在写入 Word 检查报告并重新运行关卡检查。
  • PaperSpine 工作流已完成
  • 全部阶段已通过
  • 交付文件清单

Tool names, file paths, command names, and required English manuscript text may remain literal, but explanatory prose around them must be Chinese.

Required Configuration

Prefer reading paper_rewriting_output/paper_spine_config.json. If it is missing, read references/intake.md and collect configuration.

Required fields:

FieldAllowed Values
workflowrewrite_existing, build_from_materials
scenejournal, conference, report_review, competition
tierflash, pro
output_languageen, zh
target_namefree text
materials_dirpath or empty
draft_pathpath or empty
user_motivationfree text or empty
official_urlslist
special_requirementslist
word_outputnone, docx
translation_packagenone, zh
reference_modelocal_first, specified_paths, web
reference_pathslist of local reference folders/files; default ["."]
citation_target_countinteger; default 20
humanize_tiernone, light, medium, heavy

Non-Negotiable Route

Resume-first rule: Before starting any workflow, read references/resume.md and run progress_check.py against paper_rewriting_output/. If earlier stages have produced valid artifacts, start from the first incomplete stage. After executing that stage, run its gate, run the full progress check again, and continue until fin

Read the complete source ↗