Mxl Troubleshoot
This skill should be used when MaxwellLink simulations stall, diverge, or produce missing/incorrect observables; it provides a first-aid checklist for sockets, units, and driver configuration.
Install
npx skills add TaoELi/MaxwellLink --skill mxl-troubleshootgit clone --depth 1 https://github.com/TaoELi/MaxwellLink.git /tmp/MaxwellLink
mkdir -p ~/.claude/skills
cp -r /tmp/MaxwellLink/skills/mxl-troubleshoot ~/.claude/skills/mxl-troubleshootPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Troubleshooting first aid ## Socket stalls or deadlocks - Verify hub and driver agree on `--unix/--address/--port` and the same UNIX socket name or TCP port. - For SLURM two-step runs, confirm the host/port file is written to a shared directory and the driver job waits until it exists. - Increase `timeout` for HPC and slow drivers; reduce `latency` only after basic correctness is verified. - Launch external drivers only once under MPI (rank 0). ## Unit and axis mismatches - For Meep, verify `time_units_fs` is set and consistent; time is reported in atomic units in driver histories. - Verify `orientation` (TLS/QuTiP preset) and `coupling_axis` (SingleMode/LaserDriven) are consistent with simulation dimensionality. ## Driver errors - Confirm optional dependencies are installed in the driver environment (`pymeep`, `qutip`, `psi4`, `ase`). - For ASE/LAMMPS, confirm per-atom charges exist (`charges=[...]` or `recompute_charges=true`). - If `get_available_host_port(localhost=False)` fails on a locked-down cluster, avoid outbound probes: bind the hub to `host=""` and write a reachable hostname via `MXL_HOST` or `hostname -f`. - Enable `checkpoint=true`/`restart=true` when drivers may be pre-empted. ## Next actions - Compare behavior to minimal reference tests under `tests/`. - Use `skills/mxl-postprocess/SKILL.md` to export and inspect diagnostics.
Details
- Skill name
mxl-troubleshoot- Repository
- TaoELi/MaxwellLink
- Path
skills/mxl-troubleshoot/SKILL.md- License
- GPL-2.0
- Repo updated
- 17 November 2026
FAQ
What does the Mxl Troubleshoot skill do?
This skill should be used when MaxwellLink simulations stall, diverge, or produce missing/incorrect observables; it provides a first-aid checklist for sockets, units, and driver configuration.
How do I install the Mxl Troubleshoot skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add TaoELi/MaxwellLink --skill mxl-troubleshoot. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Mxl Troubleshoot popular?
It lives in TaoELi/MaxwellLink, which has 9 GitHub stars and 5 forks.
Related skills
Mxl CLI
9TaoELi/MaxwellLink
This skill should be used when users need to initialize, clean, or configure MaxwellLink workspaces using the mxl command family.
Mxl Core
9TaoELi/MaxwellLink
This skill should be used when users need the canonical MaxwellLink workflow, including socket vs embedded coupling, units/time handling, and MPI/HPC invariants.
Mxl Driver Ase
9TaoELi/MaxwellLink
This skill should be used when users want to run the ASE driver for classical/BOMD dynamics in MaxwellLink and need charge conventions and socket/embedded invocation patterns.
Revolut X Trades
9revolut-engineering/revolut-agent-skills
Revolut X trade data — market trade history, private fills, and execution details for completed orders, with pagination and date filtering. Use when the user asks to view trade history, check fills, see recent trades, or analyse order execution on Revolut X.
Mxl Singlemode
9TaoELi/MaxwellLink
This skill should be used when users need the MaxwellLink single-mode cavity solver for fast prototyping and regression, in either socket or embedded mode.
Robodk Station Audit
9RoboDK/RoboDK-Agent-Skills
Audit RoboDK stations for common structural mistakes.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.