Mathodology Gateway Api
Use when maintaining archived knowledge about Mathodology's former gateway, API routes, auth, state, LLM routing, exports, submission bundles, or contracts.
Install
$ agentstack add skill-sweetcornna-mathodology-mathodology-gateway-api ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sweetcornna
- Source: sweetcornna/mathodology
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.