Skip to content

Lucasuiii/modeling-workbench / .agents/skills/cumcm-workflow

cumcm-workflow

Verified

Build 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.

FileKindSize
SKILL.mdskill md9.0 KB
agents/openai.yamlconfig427 B
assets/latex-template/generic-ctex/macros.texother859 B
assets/latex-template/generic-ctex/main.tex.tmplother2.5 KB
assets/latex-template/generic-ctex/metadata.tex.tmplother272 B
assets/latex-template/generic-ctex/planned-section.tex.tmplother1.0 KB
assets/latex-template/generic-ctex/references.bibother155 B
assets/latex-template/generic-ctex/sections/00_abstract.texother935 B
assets/latex-template/generic-ctex/sections/98_references.texother221 B
assets/latex-template/generic-ctex/sections/99_appendix.texother264 B
assets/latex-template/generic-ctex/template.jsonconfig304 B
assets/latex-template/generic-en/macros.texother868 B
assets/latex-template/generic-en/main.tex.tmplother2.2 KB
assets/latex-template/generic-en/metadata.tex.tmplother278 B
assets/latex-template/generic-en/planned-section.tex.tmplother1013 B
assets/latex-template/generic-en/references.bibother155 B
assets/latex-template/generic-en/sections/00_abstract.texother454 B
assets/latex-template/generic-en/sections/98_references.texother201 B
assets/latex-template/generic-en/sections/99_appendix.texother240 B
assets/latex-template/generic-en/template.jsonconfig249 B
assets/latex-template/huawei-ctex/main.tex.tmplother3.3 KB
assets/latex-template/huawei-ctex/template.jsonconfig276 B
assets/plot-style/cumcm.mplstyleother953 B
references/01-intake.mdmarkdown3.9 KB
references/02-problem-analysis.mdmarkdown2.8 KB
references/03-model-design.mdmarkdown7.6 KB
references/04-computation.mdmarkdown13.4 KB
references/05-validation.mdmarkdown5.9 KB
references/06-paper-writing.mdmarkdown14.3 KB
references/07-compile-delivery.mdmarkdown6.1 KB
references/artifact-contracts.mdmarkdown3.1 KB
references/competition-adaptation.mdmarkdown6.8 KB
references/competition-writing.mdmarkdown5.6 KB
references/diagnostics.mdmarkdown4.5 KB
references/evidence-rules.mdmarkdown1.6 KB
references/handoffs.mdmarkdown3.5 KB
references/huawei-delivery.mdmarkdown10.1 KB
references/latex-template.mdmarkdown6.2 KB
references/mechanism-validation.mdmarkdown11.6 KB
references/open-topic-research.mdmarkdown4.9 KB
references/task-driven-modeling.mdmarkdown7.2 KB
schemas/claim-ledger.schema.jsonconfig5.5 KB
schemas/common.schema.jsonconfig2.5 KB
schemas/compile-receipt.schema.jsonconfig3.7 KB
schemas/cross-question-ledger.schema.jsonconfig1.3 KB
schemas/delivery-manifest.schema.jsonconfig7.9 KB
schemas/figure-manifest.schema.jsonconfig1.9 KB
schemas/handoff.schema.jsonconfig2.1 KB
schemas/independent-review-package.schema.jsonconfig3.4 KB
schemas/independent-review-result.schema.jsonconfig4.0 KB
schemas/latex-template-manifest.schema.jsonconfig2.4 KB
schemas/model-contract.schema.jsonconfig5.0 KB
schemas/paper-plan.schema.jsonconfig3.3 KB
schemas/paper-quality-report.schema.jsonconfig5.7 KB
schemas/paper-revision-log.schema.jsonconfig2.2 KB
schemas/paper-visible-text-report.schema.jsonconfig1.6 KB
schemas/problem-facts.schema.jsonconfig1.7 KB
schemas/results-index.schema.jsonconfig1.4 KB
schemas/run-manifest.schema.jsonconfig7.1 KB
schemas/source-manifest.schema.jsonconfig1.9 KB
schemas/task-capabilities.schema.jsonconfig3.9 KB
schemas/workflow-state.schema.jsonconfig2.4 KB
scripts/backend_selection.pyscript6.3 KB
scripts/build_handoff.pyscript20.4 KB
scripts/build_independent_review_package.pyscript14.9 KB
scripts/canonical_evidence.pyscript8.4 KB
scripts/compile_sources.pyscript2.4 KB
scripts/cumcm_check.pyscript2.9 KB
scripts/delivery_archives.pyscript7.0 KB
scripts/doctor.pyscript7.5 KB
scripts/index_result.pyscript10.9 KB
scripts/init_latex_paper.pyscript17.2 KB
scripts/init_project.pyscript11.1 KB
scripts/inventory_artifacts.pyscript4.1 KB
scripts/json_pointer.pyscript1.0 KB
scripts/official_materials.pyscript3.0 KB
scripts/paper_visible_text_check.pyscript5.4 KB
scripts/plan_redo.pyscript18.8 KB
scripts/project_status.pyscript5.8 KB
scripts/provenance.pyscript2.2 KB
scripts/record_compile.pyscript13.2 KB
scripts/record_decision.pyscript12.0 KB
scripts/record_run.pyscript28.1 KB
scripts/refresh_evidence.pyscript4.7 KB
scripts/set_mode.pyscript2.0 KB
scripts/submission_check.pyscript10.6 KB
scripts/workflow_checks.pyscript146.0 KB

references/diagnostics.md

View on GitHub
# Environment and project diagnostics

Use diagnostics at setup, after an environment change, on project resumption, or when the user asks about progress. Do not repeat them on every reply. They report observations without installing software, rewriting contracts, recording approvals, or advancing stages. Probes use temporary directories; they are not a sandbox for untrusted software.

## Environment: `doctor.py`

```bash
python3 "$S/doctor.py"
python3 "$S/doctor.py" --json
```

The doctor uses the Python interpreter that launches it. It checks core workflow files and reads the workflow version, imports supported `jsonschema` and `referencing` versions in child processes, locates MATLAB with the existing backend detector, runs version probes for XeLaTeX/Poppler, and looks for `ctexart.cls`. It does not certify all repository files, solve a model, test fonts or compile a paper. A missing Python interpreter prevents launching the doctor; report that prerequisite directly.

Statuses are `available`, `missing`, `failed`, and `unverified`. Found MATLAB is **unverified** by default: discovery does not prove license or toolbox availability. If the chosen task needs MATLAB execution testing, `--probe-matlab --timeout 60` starts it in a temporary directory and tests base runtime/license access; task-specific toolboxes remain untested. This may consume a license and use ordinary application preferences. No parallel backend implementation is requested.

For known, trusted installed Python dependencies needed by the actual model, use repeatable `--module numpy --module scipy`. This imports code in a child process, not from the contest directory. Do not import arbitrary modules supplied with unfamiliar input materials. Successful imports do not establish solver correctness, task suitability or GPU availability. Without these options, the doctor makes no claim about scientific libraries.

Exit status: `0` means base checks and requested Python imports passed; `1` means one of these failed; `2` means invalid command arguments. Paper tools and optional MATLAB checks are stage-specific and do not change that exit code: inspect individual results. `paper_tools_detected` excludes Chinese class discovery; read the separate `ctex` result for Chinese papers. Tool detection never establishes compile/visual QA success.

Tell the user what is usable now, what is missing, and which stage needs it. Missing LaTeX must not prevent intake or model exploration. Recommend only the relevant dependency/environment repair, matching the detected execution environment; ask before installing or changing system configuration. Honor an already prepared environment instead of reinstalling it.

## Project: `project_status.py`

```bash
python3 "$S/project_status.py" --project <p>
python3 "$S/project_status.py" --project <p> --json
```

Reads and validates the current state, then invokes the existing checker through that stage using `preflight`. It also calls the existing human-checkpoint action boundaries through that stage: a lightweight preflight can be ready while a missing/stale approval snapshot still prevents dependent work. Those two observations are reported separately; the tool introduces no new rule or approval mechanism.

The text groups technical errors, review-related findings and warnings, shows up to five findings per group, lists checkpoint availability, and links the active stage guide. JSON retains every original finding, rule ID, path, remediation and checker summary. A checkpoint failure can reflect incomplete candidate selection or missing/stale confirmation evidence; do not interpret every failure as simply asking the user to approve immediately. Repair or prepare the material first, and never invent an earlier approval.

Exit status: `0` means no automated checker errors (human review may still be pending); `1` means automated checker errors; `2` means status could not be evaluated, such as invalid/unsupported state, missing dependencies or unreadable contracts. Never treat `0`, declared `passed`, or existing downstream files as authority to cross a human checkpoint. The usual action tools enforce their own boundaries.

The scope ends at the recorded current stage. This does not certify later files or declare a project finished. For affected-work planning after a concrete change, use the existing `plan_redo.py`; status does not guess which unexamined work is unaffected. If state is corrupt, report it without reinitializing or overwriting the project. Summarize findings in the user's language and continue already-authorized work when possible.
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall