paper-spine
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.
WUBING2023 · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add WUBING2023/PaperSpine --skill paper-spine技能说明
name: paper-spine description: Build, rewrite, audit, submit, revise, or transfer scholarly papers end to end, producing verified LaTeX/PDF/Word and target-specific publication packages.
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, check for updates,
or configure automatic updates, read references/update.md and execute without
starting intake or the writing workflow. Automatic updates are opt-in only.
Command Routing
| Trigger | Read |
|---|---|
| Default / full workflow | This file (Non-Negotiable Route below) |
resume / continue / "continue from" | references/resume.md |
update / "check for updates" / 手动更新 | references/update.md |
| `auto-update on | off |
submission / "submission materials" / delivery package | references/publication-cycle.md, then references/submission.md |
audit | references/audit.md |
translate | references/translate.md |
humanize | references/humanize.md |
respond / rebuttal / minor or major revision | references/publication-cycle.md, then references/respond.md |
| rejection / resubmit / journal transfer / 转投 | references/publication-cycle.md, then references/journal-transfer.md |
Automatic Update Preflight
Before every normal workflow launch or resume, follow references/update.md
and run the installed updater with --auto. The preflight is a local no-op
unless the user has explicitly enabled automatic updates and the configured
interval is due. Never enable it on the user's behalf.
If the preflight installs a new version, stop before intake/research/writing and ask the user to reload or restart the host, then invoke PaperSpine again. If the preflight fails, warn once and continue with the current installation; do not turn an update-network failure into a paper-workflow blocker.
For fine-grained stage execution, the orchestrator reads the playbook for each
stage from references/ rather than requiring a separate skill invocation:
| Stage | Playbook |
|---|---|
| Intake / config | references/intake.md |
| Resume / checkpoint | references/resume.md |
| Research | references/research.md |
| Citation | references/citation.md |
| Review policy / autonomy | references/review-policy.md |
| Editorial completeness / manuscript scale | references/editorial-completeness.md |
| Semantic confirmation | references/semantic-confirmation.md |
| Contribution contract | references/contribution.md |
| Rewrite | references/rewrite.md |
| Build | references/build.md |
| Results validation | references/results-validation.md |
| Scientific evidence ledger | references/scientific-evidence-ledger.md |
| Reviewer audit | references/reviewer-audit.md |
| Humanize | references/humanize.md |
| Reader-facing claim voice | references/assertive-scientific-writing.md |
| LaTeX | references/latex.md |
| Visual readiness | references/visual-readiness-gate.md |
| Submission metadata | references/submission-metadata.md |
| Publication surface | references/publication-surface.md |
| Publication target profile | references/publication-target-profile.md |
| Submission / revision / transfer cycle | references/publication-cycle.md |
| Publication-cycle main-flow interface | references/publication-cycle-interface.md |
| Journal transfer | references/journal-transfer.md |
| Usage telemetry / phase receipts | references/usage-telemetry.md, references/phase-contracts.md |
| Translate | references/translate.md |
| Respond | references/respond.md |
| Audit | references/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 available evidence, confirm the controlling contribution and motivation, then give the writing Agent room to design the strongest argument and manuscript structure for the actual material.
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.
Keep scientific boundaries explicit without repeating the full provenance disclaimer in every paragraph. Define stable evidence scope at the paper or section boundary, inherit it until the evidence changes, and restate only the exception. This preserves caution without defensive repetition.
Default to review_policy=balanced. Gates are decision aids, not a substitute
for writing judgment. Hard-block fabricated facts/citations, unsupported primary
claims, unresolved figure/text conflicts, broken citations, missing required
metadata, and unusable deliverables. Treat stylistic preferences, literature
breadth inside a declared closed corpus, optional planning forms, and minor
review suggestions as advisory. Use strict only when the user requests it or
the task is explicitly a submission/final-compliance audit. Read
references/review-policy.md when selecting or changing this policy.
The internal evidence model may be precise; the manuscript should still sound
like a confident scholarly article. Read
references/assertive-scientific-writing.md: state supported results directly,
reserve hedging for genuine uncertainty or causal/generalization boundaries,
and do not repeat audit language in reader-facing prose.
Editorial North Star
The manuscript is the product; plans, ledgers, reviews, and receipts exist only to help the Agent write it. A workflow is not complete merely because its internal artifacts pass. The final paper must let its intended reader follow one visible arc: why the work was needed, what was done, what the
阅读完整来源 ↗