Skip to content
cccskills
FreePublished on GitHub

paper-formal-writer

正式论文的唯一撰写路径,制定写作计划、按章节写作与审计、全文统一改写,并生成原生公式 Word 与 PDF 渲染检查。当运行证据已通过校验、需要撰写或续写完整竞赛论文、或需要产出 final_paper.docx 与渲染 PDF 时使用。

The English summary is being prepared. Showing the original description.

Works withWord
See how to install

Files included (18)

  • SKILL.md7.5 KB
  • agents/openai.yaml335 B
  • references/competition-scope.md2.1 KB
  • references/cumcm-paper-standard.md3.5 KB
  • references/figure-table-writing-rules.md1.2 KB
  • references/formal-paper-template.md1.7 KB
  • references/metric-claims.md7.1 KB
  • references/section-expansion-rules.md1.3 KB
  • scripts/assemble_sections.py3.6 KB
  • scripts/authoring_contracts.py15.5 KB
  • scripts/build_paper_outline.py14.5 KB
  • scripts/check_paper_format.py36.1 KB
  • scripts/claim_bindings.py17.4 KB
  • scripts/format_formal_docx.py28.8 KB
  • scripts/formula_omml.py9.6 KB
  • scripts/paper_scope.py4.3 KB
  • scripts/prepare_authoring.py7.3 KB
  • scripts/validate_authoring.py17.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Paper Formal Writer

Resolve <SKILL_ROOT> to the parent directory of this loaded skill folder, using its actual absolute path. Run commands from the contest project root, never from the installed skill directory. The placeholder is not a shell environment variable.

This skill is the sole formal author and final manuscript producer in Standard. It turns a fresh S6 evidence chain into an audited Markdown source and native-equation Word document.

Entry

Run before formal work:

python "<SKILL_ROOT>/paper-workflow-orchestrator/scripts/workflow_guard.py" --skill paper-formal-writer

S0-S6 must pass. If workflow state is uncertain, run workflow_guard.py --status and follow its current artifact report rather than memory.

Single Formal Path

S6 evidence PASS
-> writing plan
-> chapter drafts
-> chapter audits
-> queued local repair when required
-> deterministic assembly
-> Agent global revision
-> final Markdown audit
-> formal DOCX
-> S8 format/render gate

Do not promote quickstart, legacy, or mechanically merged micro-unit output into a formal filename.

Prepare

  1. Build the evidence-aware outline:
python "<SKILL_ROOT>/paper-formal-writer/scripts/build_paper_outline.py"
  1. Prepare adaptive authoring:
python "<SKILL_ROOT>/paper-formal-writer/scripts/prepare_authoring.py" --mode auto

Default delivery is competition: plan at least 14000 effective characters, with a main-paper floor of 8000 and at least 18 rendered pages before appendices. These are adjustable project defaults, not contest rules. Verify the actual contest's page cap and counting rules before writing. auto therefore selects section; a short report needs --delivery short-report --scope-reason "user-requested scope". Custom floors use --min-pages / --min-body-chars with a reason; never lower them merely to turn a failed check green.

Read references/competition-scope.md when preparing scope or repairing a short manuscript. Several authoring turns may produce one coherent chapter; preserve evidence and notation between turns instead of compressing the paper into one response.

The authoritative S7 contracts are:

  • paper_output/plan/writing_plan.json
  • paper_output/context/authoring_state.json
  • paper_output/qa/draft_audit.json
  • paper_output/qa/repair_queue.json

Draft And Audit

For numerical results, read references/metric-claims.md. Formal preparation binds each required metric to its unit, sample/split, CSV row and successful experiment. Missing metadata blocks S7 instead of being guessed from prose. Maintain a sibling .claims.json for each draft and the final source; use an empty claims list for chapters without numbers. Only declared conversions are allowed. Never promote a feasible solution to an optimal one without recorded verification.

Write only to the path recorded for the current unit in authoring_state.json. Each chapter must be a complete, coherent section and must include its required removable marker:

<!-- mathmodel-evidence: evidence-id-1, evidence-id-2 -->

Audit every changed draft:

python "<SKILL_ROOT>/paper-formal-writer/scripts/validate_authoring.py" --section <section-id>

Routing is deterministic:

  • global repeats the same blocking category twice: switch to section.
  • A section fails once: rewrite that section.
  • A section repeats the same category twice: paper-micro-unit-generator may repair only queued locations.
  • The third changed attempt with the same category: S7 becomes BLOCKED; report the cause and suggest Lite as a user choice without switching automatically.

Audits block short drafts, missing chapters/evidence/numbers, broken formulas, placeholders, duplicate prose, broken figure/table references, and internal workflow language.

Assemble And Revise

After all active units pass:

python "<SKILL_ROOT>/paper-formal-writer/scripts/assemble_sections.py"
python "<SKILL_ROOT>/paper-formal-writer/scripts/validate_authoring.py" --assembled

The assembler follows outline order, strips evidence comments, merges claim sidecars, and preserves existing numbering. It writes paper_output/drafts/assembled_draft.md.

Then read the entire assembled draft and evidence chain, and rewrite the paper globally into:

paper_output/final_paper_source.md

This pass must unify terminology, notation, transitions, argument order, citations, captions, and conclusions. Copying the assembled draft unchanged is rejected. Update final_paper_source.claims.json with the revised quotes and exact source hash; do not copy stale bindings. Sidecars remain outside the rendered manuscript.

Run the final source audit:

python "<SKILL_ROOT>/paper-formal-writer/scripts/validate_authoring.py" --final

Any change to evidence, writing plan, approved section draft, assembly, or final source invalidates downstream PASS state.

Word And S8

Only after authoring_state.status = PASS:

python "<SKILL_ROOT>/paper-formal-writer/scripts/format_formal_docx.py"
python "<SKILL_ROOT>/paper-formal-writer/scripts/check_paper_format.py" --render required

Formal mode requires fresh S6 and S7 hashes. --allow-draft may create final_paper_draft.docx for layout diagnosis, but never satisfies S7/S8 or overwrites the formal DOCX.

format_formal_docx.py converts LaTeX to editable Word OMML and blocks failed conversion. check_paper_format.py checks dynamic length, required hierarchy, citations, evidence-linked figures/tables, formulas, duplicate prose, DOCX structure, LibreOffice PDF rendering, page count, and extractable text.

Writing Standard

  • Use 1 / 1.1 / 1.1.1 headings and complete CUMCM sections.
  • For each question, connect assumptions, variables, derivation, algorithm, computed values, validation, uncertainty, and conclusion.
  • Define symbols before formulas and explain every displayed result.
  • Cite and interpret every included figure/table.
  • Use only current evidence; never invent runs, values, sources, or validation.
  • Avoid copied or number-swapped paragraphs used only to meet length.
  • Keep implementation language out of body prose; reproducibility paths belong in the appendix.

References

Read only the reference needed for the current writing or repair decision.

Handoff

After each meaningful transition, run workflow status and update paper_output/context/workflow_memory.json:

python "<SKILL_ROOT>/paper-workflow-orchestrator/scripts/workflow_guard.py" --status
python "<SKILL_ROOT>/context-memory-keeper/scripts/update_workflow_memory.py"

S8 is complete only when the machine-readable format report is PASS and fresh.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

定位并获取权威公开数据,优先使用官方 API 与批量下载,产出可复现的抓取代码、来源与许可说明、校验记录。当赛题未提供附件、需要用人口或经济或气象或交通等官方统计补齐数据,或用户要求从权威来源取数时使用。

The English summary is being prepared. Showing the original description.

yushui2022/MathModel-Skill455Updated Oct 22, 2026

维护跨会话的项目记忆,记录长期规则与当前任务清单,供后续阶段恢复上下文。当长对话需要压缩、已确认的决策与约束需要落盘、或用户要求记住或恢复之前进展时使用。

The English summary is being prepared. Showing the original description.

yushui2022/MathModel-Skill455Updated Oct 22, 2026

清洗原始数据并生成论文级图表,处理缺失值、异常值、单位与格式不一致,产出加载报告、数据计划、图表索引、可复现的图文件与图注。当用户提供 csv 或 xlsx 原始附件需要清洗、需要为某一问画图或补图注、或数据与可视化计划待执行时使用。

The English summary is being prepared. Showing the original description.

yushui2022/MathModel-Skill455Updated Oct 22, 2026

数学建模全流程技能包:赛题与附件预检、题意与模型路线、数据与图表计划、真实运行建模代码、证据门禁、分章节正式写作与 Word/PDF 渲染检查,产出可复现的竞赛论文和全套证据。当用户要做完整篇数学建模竞赛论文时使用。

The English summary is being prepared. Showing the original description.

yushui2022/MathModel-Skill455Updated Oct 22, 2026

按已确定的模型路线为每一问生成可运行代码,并沉淀结果证据契约、评价指标、结构化结论与论文表格。当模型路线已定、需要编写并真实运行各问求解代码、或运行结果需要可核验的契约记录时使用。

The English summary is being prepared. Showing the original description.

yushui2022/MathModel-Skill455Updated Oct 22, 2026

按评分点组织论文结构并给出模型路线,产出论文大纲、评分点对齐表与候选模型对照实验方案。当需要在多个候选模型间取舍、需要把评分要求映射成章节结构、或模型路线尚未确定时使用。赛题原文解析由 problem-doc-model-selector 负责。

The English summary is being prepared. Showing the original description.

yushui2022/MathModel-Skill455Updated Oct 22, 2026

See all skills by yushui2022

Report a problem with this skill