Mathodology gateway api

Skill sweetcornna/mathodology/.claude/skills/mathodology-gateway-api

专为数学建模竞赛设计的数模 Agent Skills：MCM/ICM 美赛、CUMCM 国赛、华数杯、M3、HiMCM 等，面向 Claude Code 与 Codex 的获奖级建模工作流。Math modeling contest skills for Claude Code & Codex.

Install

npx -y skills add sweetcornna/mathodology --skill mathodology-gateway-api

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Use when a Mathodology workflow needs export/packaging/API reasoning, or when consulting archived knowledge about the former gateway and API subsystem.

SKILL.md

2.8 KB, as published. Nobody here has run it

Mathodology Gateway API Archive

Scope

This skill preserves architectural knowledge about the former Mathodology gateway and public API surface.

The current GitHub branch does not contain the gateway source, contracts, migrations, tests, or generated clients. Use this skill for archived guidance and reconstruction planning, not for editing or compiling a gateway in this checkout.

Archived Concepts

The former gateway acted as the service boundary for the product:

request intake for modeling runs
run status, event streaming, and artifact access
authentication for development and hosted usage
persistence through application state and backing stores
LLM provider routing, streaming, fallback, and cost accounting
paper export and submission bundle generation
API contracts shared with the worker and web UI

Workflow Adapter Role

In the award-level workflow, use this skill when the submission package needs service or product-style reasoning from the former gateway design:

define a clean boundary between user prompt, computation, artifacts, and final package
preserve event-log thinking for phase logs and reproducibility trails
treat exports and submission bundles as first-class deliverables
keep API-contract thinking when specifying output schemas for code, data, tables, figures, and paper sections

Codex agents should use this as architecture guidance, not as a command to rebuild the removed gateway.

Claude Code subagents should reference this only when package boundaries, artifacts, exports, or reproducibility contracts are unclear.

How To Maintain This Skill

When updating archived gateway guidance:

Mark implementation details as historical unless verified from Git history.
Prefer behavior and contract concepts over missing source paths.
Do not add build, test, migration, or contract-generation commands as current validation.
If exact route behavior is needed, recover it from an older commit in a separate worktree.
Keep cross-boundary notes aligned with the pipeline and web UI archive skills.

Useful Questions

Use this skill for questions like:

What responsibilities did the former gateway own?
How did gateway concepts connect worker runs, web streaming, exports, and LLM providers?
What should be preserved before reconstructing API contracts?
Which historical areas need Git-history inspection before implementation work?

Current-Branch Rule

Any current-branch edit should be limited to skills or documentation. Do not add gateway source, contracts, migrations, generated clients, service config, or tests back to this branch unless the user explicitly changes the repository strategy.