Skip to content
Agentmart
Submit a tool

mxl-core

This skill should be used when users need the canonical MaxwellLink workflow, including socket vs embedded coupling, units/time handling, and MPI/HPC…

Skill by TaoELi

IndexedGPL-2.0★ 9
Write a review

Chalk Labs

Need help deploying mxl-core?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/taoeli-mxl-core

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

This skill should be used when users need the canonical MaxwellLink workflow, including socket vs embedded coupling, units/time handling, and MPI/HPC invariants.

Use cases: productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 26, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found
Runs as
Python package

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/mxl-core

What's inside

Skill name
mxl-core
Description
This skill should be used when users need the canonical MaxwellLink workflow, including socket vs embedded coupling, units/time handling, and MPI/HPC invariants.
License
GPL-2.0
Instructions
33 lines in SKILL.md · view on GitHub

Before installing

  • Ships executable scripts

Files (4)

  • SKILL.md
  • driver_quickref.md · references/
  • solver_quickref.md · references/
  • validate_skills_structure.py · scripts/

SKILL.md (first lines)

# MaxwellLink core workflow

## Enforce invariants
- Create new runnable inputs only under `projects/YYYY-MM-DD-NAME/`.
- Keep runs reproducible by storing parameters in a `config.json` (or similar) and avoiding hard-coded absolute paths.
- Never pass both `hub=...` and `driver=...` to `maxwelllink.Molecule`; provide exactly one.

## Choose coupling mode
- Use embedded mode when the driver can run in the same Python process:
  - Construct molecules with `Molecule(driver="<id>", driver_kwargs={...})`.
- Use socket mode when drivers must run as separate processes or nodes:
  - Construct a `SocketHub(...)`, pass `hub=hub` into each `Molecule(...)`, and launch one `mxl_driver --model <id> ...` per molecule.
- If local socket runs fail with MPI/network permission errors, prefer embedded mode (`Molecule(driver="...", ...)`) on local machines and reserve socket mode for SLURM/HPC.
- For local socket mode, you can disable MPI auto-init with `MPI4PY_RC_INITIALIZE=0` and ensure loopback NIC usage (use `127.0.0.1`; set site-specific NIC selection env vars if MPI/OFI tries a non-loopback interface).

## Handle units/time
- For Meep: set `time_units_fs` on `MeepSimulation(...)` and keep it consistent when interpreting driver times.
- For SingleMode/LaserDriven: work directly in atomic units and set `dt_au` explicitly.

## Handle MPI and multi-process execution
- Launch socket drivers only once (rank 0) under MPI; rely on MaxwellLink broadcasts for other ranks.
- Set generous `timeout` for HPC and tune `latency` to match driver cost.
- If attaching many molecules, consider `store_additional_data=False` for most molecules to limit memory usage; keep it `True` only for the molecules you intend to export/plot.

## Validate before running
- Use `skills/mxl-project-scaffold/scripts/mxl_validate_project.py` to sanity-check `config.json` and required files.
- When debugging behavior, compare to patterns in `tests/` and `docs/source/usage.rst`.

## References
- Solver choice: `skills/mxl-core/references/solver_quickref.md`
- Driver choice: `skills/mxl-core/references/driver_quickref.md`

From TaoELi/MaxwellLink, GPL-2.0.

More from TaoELi/MaxwellLink

Signals

Stars
9
Forks
5
Open issues
0
Last commit (this folder)
May 9, 2026 (6 months ago)
Last release
Oct 22, 2026 (14 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
GPL-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from TaoELi

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get mxl-core running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying mxl-core?

CallGet help
Cite this page

mxl-core skill. Agent Mart. https://agentmart.dev/skills/taoeli-mxl-core (last updated 2026-10-24)