Lucasuiii/modeling-workbench / .agents/skills/cumcm-workflow
cumcm-workflow
VerifiedBuild or resume mathematical-modeling competition work, including CUMCM, MCM/ICM, graduate and regional contests, data challenges, and open-topic statistical modeling. Guide problem framing, modeling, computation, validation, Chinese or English LaTeX writing, and reviewed PDF/source delivery using current official requirements. Not for ordinary paper polishing.
references/competition-writing.md
View on GitHub# Writing across competition languages and audiences
Use for English-language work, audience-specific deliverables or reference verification. Combine with [paper writing](06-paper-writing.md), which remains the common argument and QA guide. Choose `--language en` or `zh` and the actual `--competition` for the shared LaTeX/PDF chain; see [competition adaptation](competition-adaptation.md). A generic English scaffold is not an official Summary Sheet or proof of format compliance. Word export remains unsupported.
## Organize around the requested answer
Read the current official requirements for language, required sections, summary/cover sheets, supplementary letters or memoranda, anonymity, page accounting and output formats. Competition labels and previous papers do not establish any of these. An official requirement overrides a generic scaffold's default, including whether a table of contents is present.
Use the existing `PAPER_PLAN.paper_structure` and claim/representation selection for the mathematical argument. A Chinese engineering paper, an English modeling paper and a data-analysis report share the need to connect formulation, solution, result, evidence and limitations; they need not share heading order, length or typography. A diagram belongs when it explains a mechanism or dependency more clearly, not because a template demands one.
Apply the common paper guide's default of developed explanations and useful, varied visual evidence in both Chinese and English. Match depth to the audience: explain the key modeling choices, non-obvious derivations and implications in a technical paper; preserve the decision, tradeoffs and supporting evidence in a concise client memo. Language choice does not change evidence standards or impose a fixed length. Expand substance where a reader would otherwise have to guess, and use the current organizer's space limits to prioritize it.
For a client-facing memo or recommendation, identify its audience and decision. Lead with the action, supporting result, tradeoff and conditions under which it should change. Map every quantitative statement back to the same reviewed claims as the technical paper. Do not add stronger causal, optimality or deployment claims for rhetorical impact. Include such a document only when requested or required, and verify its actual packaging separately from the paper.
## English summary and terminology
Write the summary after the body and results stabilize. Explain the problem, the decisive modeling idea, a few supported results with units or comparisons, and the important reliability boundary. If the organizer requires a separate Summary Sheet, check its exact current specification; do not manufacture a universal one-page or total-page limit.
Maintain consistent technical terms, notation, units and tense across sections. Preserve the strength of the evidence in translation: a feasible solution is not an optimal solution; a numerical check is not a proof; an association is not an effect. “Significant,” “robust,” “accurate” and “generalizable” need the corresponding evidence or a more precise description.
Use problem numbering when it helps navigation or is required, but do not force every paragraph to start with “For Problem N.” Independent questions may be presented separately; coupled questions should expose their shared mechanism and dependencies. Do not expand English prose to fill an estimated characters-per-page target.
## References and borrowed methods
For a reference actually used, verify bibliographic identity and that the inspected source supports the cited statement. Prefer the original method, dataset documentation or primary evidence. A valid DOI or search result proves neither that the source was read nor that it supports the claim. Keep uncertain references out of the final bibliography until checked; never invent a title, author, DOI or numerical benchmark.
Distinguish published benchmark values from results reproduced in this project. Cite external constants, datasets and borrowed equations where they enter the argument, preserving their units and applicability. Use only literature lookup allowed by the task and competition; missing organizer materials still follow the user-supplied-source boundary. There is no minimum citation count.
## Review explanatory depth and visual coverage
First repair task omissions, mathematical ambiguity, unsupported comparisons and contradictions between summary, tables and conclusions. Then look for underdeveloped reasoning and missed visualization opportunities in the existing evidence, following the common paper guide's reader review. Expand explanations and add complementary figures where they answer a concrete reader question; review captions, interpretation and layout together. More pages, more charts or a mandatory “de-AI” rewrite alone does not establish quality.
Use the current quality report/revision log when a real finding needs tracking. Stop when consequential findings are resolved or transparently retained within scope, and further changes add little value under the available budget. A new experiment or changed conclusion follows the existing upstream revision and approval process. Recompile and inspect the changed artifact when source edits affect it; prior PDF review does not automatically cover the new PDF.
For Word or other formats, the scientific argument and evidence standards still apply, but inspect the actual exported equations, captions, tables, fonts and pagination. A good Markdown draft is not a verified DOCX or PDF, and it cannot satisfy v0.6's LaTeX receipt. Report that limitation rather than bypassing the checker.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |