Modal Run
Use when the user asks to run heavy or GPU work on Modal (the cloud compute platform) — writing a Modal function in the workspace, running it with the user's own `modal` CLI + token, and bringing results back. Data-to-compute for jobs too big for the laptop, without a Slurm cluster.
Install
npx skills add ai4s-research/open-science --skill modal-rungit clone --depth 1 https://github.com/ai4s-research/open-science.git /tmp/open-science
mkdir -p ~/.claude/skills
cp -r /tmp/open-science/runtime/skills/core/modal-run ~/.claude/skills/modal-runPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Run compute on Modal Modal runs code in the cloud on demand (CPU/GPU), billed to the **user's own** Modal account. Like the HPC/Slurm path, the app never handles credentials — you use the user's installed `modal` CLI and their token. Prefer local execution or Slurm first; reach for Modal when the job needs cloud GPUs or elastic scale and no cluster is available. ## 1 · Check Modal is ready Modal must be installed and authenticated (the Settings **Cloud compute (Modal)** card shows this). Verify before writing code: ```bash modal --version # installed? test -f ~/.modal.toml && echo "authenticated" || echo "run: modal token new" ``` If it is not installed, tell the user to `pip install modal`; if not authenticated, ask them to run `modal token new` in their terminal (it opens a browser). Do **not** attempt to create or store tokens yourself. ## 2 · Write the Modal function into the workspace Put the script in the workspace so provenance records it. Pin dependencies in the image so the run is reproducible, and fix any random seed.
Details
- Skill name
modal-run- Repository
- ai4s-research/open-science
- Path
runtime/skills/core/modal-run/SKILL.md- Repo updated
- 17 November 2026
FAQ
What does the Modal Run skill do?
Use when the user asks to run heavy or GPU work on Modal (the cloud compute platform) — writing a Modal function in the workspace, running it with the user's own `modal` CLI + token, and bringing results back. Data-to-compute for jobs too big for the laptop, without a Slurm cluster.
How do I install the Modal Run skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ai4s-research/open-science --skill modal-run. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Modal Run popular?
It lives in ai4s-research/open-science, which has 2,105 GitHub stars and 231 forks.
Related skills
Computer Use
2.1kai4s-research/open-science
Use when a task needs an app on the user's own screen — a native desktop application (instrument control software, Origin, GraphPad, ImageJ, a reference manager, a spreadsheet), or a desktop browser window that needs window-level control. Read before the first `computer` call. Covers the observe-act-observe loop, why element indexes go stale, which action to prefer for which control, what "unverified" means and why it must never be reported as success, and the recovery for each error code. Not for page-level web automation (use the browser connector) and not for anything that can be done from
Domain Check
2.1kai4s-research/open-science
Use ONLY when the user asks to check, validate, review or audit analysis code for scientific correctness, or when you are the reviewer agent running its checks. Never run it unprompted as part of ordinary analysis work. Covers physics, earth/geo, biology, chemistry, social science and bioprocess/fermentation. Runs a deterministic domain-correctness gate that catches code which runs but is scientifically wrong (unit/dimension mismatch, Euclidean distance on lat/lon without a CRS, 0-based/1-based coordinate and strand errors, impossible SMILES valence, uncorrected multiple comparisons, averaging
Large File
2.1kai4s-research/open-science
Use BEFORE reading any data file that could be large (CSV/TSV, Parquet, HDF5, FITS, NetCDF, NDJSON, genomics FASTQ/FASTA/VCF/BAM, GRIB, ROOT, or big text/simulation logs like VASP OUTCAR). Returns a compact memory pointer — header/schema/shape/sample/key numbers — by introspection and sampling in bounded memory, so you never load a file bigger than the context window into the model. Reference data via the pointer; read specific ranges deterministically.
Content Strategy
3.4kOwl-Listener/designer-skills
Define what content a product needs, how it is structured, and who owns it. Use when content itself is the problem. For the words in the interface use `ux-writing` (designer-toolkit); for structural hierarchy use `information-architecture`.
Technical Documentation
2.7kwondelai/skills
Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or tutorial", "API reference", "docstrings", "CLI help text", "changelog or release notes", "migration guide", or "our docs are confusing". Also use it when writing docs from code, rewriting a doc for clarity, fixing headings, procedures, or code samples, or enforcing consistent voice and ter
Critique Information Density
3.4kOwl-Listener/designer-skills
Critique a rendered screen's density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure. Use when a screen feels overwhelming. For the underlying choice-count principle, use `hicks-law` (interaction-design).
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.