Install the "mat-melting-point" agent skill from https://github.com/learningmatter-mit/AtomisticSkills/tree/main/skills/mat-melting-point into .claude/skills/mat-melting-point/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mat-melting-point", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add learningmatter-mit/AtomisticSkills --skill mat-melting-point -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "mat-melting-point" agent skill from https://github.com/learningmatter-mit/AtomisticSkills/tree/main/skills/mat-melting-point into .agents/skills/mat-melting-point/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mat-melting-point", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add learningmatter-mit/AtomisticSkills --skill mat-melting-point -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "mat-melting-point" agent skill from https://github.com/learningmatter-mit/AtomisticSkills/tree/main/skills/mat-melting-point into .cursor/skills/mat-melting-point/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mat-melting-point", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add learningmatter-mit/AtomisticSkills --skill mat-melting-point -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "mat-melting-point" agent skill from https://github.com/learningmatter-mit/AtomisticSkills/tree/main/skills/mat-melting-point into .gemini/skills/mat-melting-point/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mat-melting-point", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add learningmatter-mit/AtomisticSkills --skill mat-melting-point -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "mat-melting-point" agent skill from https://github.com/learningmatter-mit/AtomisticSkills/tree/main/skills/mat-melting-point into .github/skills/mat-melting-point/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mat-melting-point", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add learningmatter-mit/AtomisticSkills --skill mat-melting-point -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "mat-melting-point" agent skill from https://github.com/learningmatter-mit/AtomisticSkills/tree/main/skills/mat-melting-point into .opencode/skills/mat-melting-point/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mat-melting-point", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
mat-melting-point
GitHub stars
176
Token cost
~2.1k tokens
SKILL.md length
777 words
Files
11 (incl. scripts)
Skills in repo
129
Repo updated
First seen
Licence
MIT
At a glance
Calculate the melting temperature of a material using the solid-liquid interface (coexistence) method.
Works in 10 steps: Background Research → Phase Preparation → Interface Creation: Use… → …
SKILL.md covers Goal, Instructions, Examples and Constraints
Runs Python scripts from its folder
What it does
Mat Melting Point is an agent skill from learningmatter-mit/AtomisticSkills. Calculate the melting temperature of a material using the solid-liquid interface (coexistence) method.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts (for example `examples/NaCl/README.md`, `scripts/check_phase.py` and `scripts/create_interface.py`).
It works with Model Context Protocol. The repository describes itself as: Integrating AtomisticSkills into Agentic IDEs (Cursor, Claude Code, Codex, Google Antigravity, Hermes Agent, etc). The licence is MIT.
Example prompts
“/mat-melting-point”
Requirements
Python 3
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
1Background Research
2Phase Preparation
3Interface Creation: Use create_interface.py to concatenate the two phases.
4Relaxation: Perform an ionic relaxation using the relax_structure MCP tool with relax_cell=True. This allows the unit cell to adjust…
5Phase Verification: Before running production MD, verify solid-liquid coexistence in all structures.
6Thermalization (Equilibration): Start from the 0 K relaxed structure and run a short NVT thermalization at the expected $T_m$ to properly…
7Production: Run an NVE MD simulation starting from the full .traj file of the thermalized structure with the monitor=True parameter…
8Auto-Termination: The integrated monitor will
9Phase Validation: Verify that the solid and liquid phases still coexist at the end of the simulation.
10Analysis: If coexistence is verified, calculate $T_m$ by averaging the temperature over the last 5 ps of the simulation.
What it can do on your machine
Read from SKILL.md and the folder at commit 6257444. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 5 files in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Mat Melting Point loads about 2.1k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 777 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~30
When it runs· the whole SKILL.md, loaded when a task matches
~2.1k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
Download SKILL.mdSave it as .claude/skills/mat-melting-point/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
mat-melting-point
description
Calculate the melting temperature of a material using the solid-liquid interface (coexistence) method.
metadata.category
materials
metadata.venv
cpu, mlip
Melting Point
<!-- mcp-tools-note -->
[!NOTE]
Steps written server.tool are MCP tool calls: mace.run_md is the run_md
tool of the mace server (mcp__mace__run_md, or
mcp__plugin_atomistic-skills_mace__run_md when installed as a plugin).
Without a connected server, run the same tools from the shell. Tools named in
one command share a process, so a model loaded by load_model stays loaded:
bash
${CLAUDE_SKILL_DIR}/../../venv/run mlip python -m src.mcp_server.cli mace run_md key=value relax_structure key=value
${CLAUDE_SKILL_DIR}/../../venv/run cpu python -m src.mcp_server.cli base visualize_structure key=value
Goal
To determine the thermodynamic melting temperature ($T_m$) of a bulk material by equilibrating a solid-liquid interface in an NVE ensemble.
Instructions
Background Research:
Search for the approximate melting point ($T_m$) and boiling/evaporation point ($T_{vap}$) of the material.
Choose a melting temperature $T_{melt}$ where $T_m < T_{melt} \ll T_{vap}$.
MD Parameters: Refer to the mat-md-monitors skill for best practices on timesteps and monitors. In general, use a 2.0 fs timestep for systems without Hydrogen.
Phase Preparation:
Solid: Create a supercell using create_supercell.py.
bash
${CLAUDE_SKILL_DIR}/../../venv/run cpu python ${CLAUDE_SKILL_DIR}/scripts/create_supercell.py [input_structure.cif] [solid_supercell.cif] --min_length 20.0
Liquid: Melt a block using 1D-NPT (with mask) to ensure matching dimensions.
bash
mace.run_md(
structure_data="solid_supercell.cif",
temperature=2000, # REPLACE with T_melt from Step 1
ensemble="npt",
steps=5000,
timestep=2.0, # Use 2.0 fs for most inorganic systems
pressure=1.0, # Apply positive pressure (1-2 bar) to prevent evaporation
pressure_mask=[1, 0, 0], # REQUIRED: Must match the stacking axis (e.g., x-axis)
output_dir="melt_stage"
)
Visual Inspection (CRITICAL): Sometimes the cell does not fully melt within the specified MD steps. You MUST use the base.visualize_structure tool to generate an image of the final liquid.cif structure (or trajectory) and have the VLM visually inspect the image to confirm that the long-range crystalline order has been destroyed and the cell is completely melted. If it has not, you must run the MD with a higher temperature or for more steps.
Interface Creation: Use create_interface.py to concatenate the two phases.
bash
${CLAUDE_SKILL_DIR}/../../venv/run cpu python ${CLAUDE_SKILL_DIR}/scripts/create_interface.py solid.cif liquid.cif --axis 0 --output interface.cif
Relaxation: Perform an ionic relaxation using the relax_structure MCP tool with relax_cell=True. This allows the unit cell to adjust (shrink/expand) to match the density, and remove the interface energy created by stacking the two cells.
Phase Verification: Before running production MD, verify solid-liquid coexistence in all structures.
First, extract reference atomic features:
bash
# (or venv/mlip)
# Extract from pure solid - use explicit output path
mace.predict_atomic_features(
structure_data="solid_supercell.cif",
output_path="<research_dir>/solid_features.json"
)
# Extract from pure liquid - use explicit output path
mace.predict_atomic_features(
structure_data="liquid_supercell.cif",
output_path="<research_dir>/liquid_features.json"
)
Then verify phases:
bash
# Solid should be ~100% solid
${CLAUDE_SKILL_DIR}/../../venv/run cpu python ${CLAUDE_SKILL_DIR}/scripts/check_phase.py <research_dir>/solid_features.json \
--solid_features <research_dir>/solid_features.json \
--liquid_features <research_dir>/liquid_features.json
# Liquid should be ~100% liquid
${CLAUDE_SKILL_DIR}/../../venv/run cpu python ${CLAUDE_SKILL_DIR}/scripts/check_phase.py <research_dir>/liquid_features.json \
--solid_features <research_dir>/solid_features.json \
--liquid_features <research_dir>/liquid_features.json
# Interface should show ~50% solid/liquid coexistence
# (Requires predicting features for the relaxed interface first)
mace.predict_atomic_features(
structure_data="interface_relax/relaxed_structure.cif",
output_path="<research_dir>/interface_features.json"
)
${CLAUDE_SKILL_DIR}/../../venv/run cpu python ${CLAUDE_SKILL_DIR}/scripts/check_phase.py <research_dir>/interface_features.json \
--solid_features <research_dir>/solid_features.json \
--liquid_features <research_dir>/liquid_features.json
Expected:
Solid: ≥95% solid
Liquid: ≥95% liquid
Interface: 40-60% solid (coexistence maintained)
If interface lost coexistence: Adjust melting temperature or relaxation parameters.
Thermalization (Equilibration): Start from the 0 K relaxed structure and run a short NVT thermalization at the expected $T_m$ to properly distribute kinetic and potential energy.
Production: Run an NVE MD simulation starting from the full .traj file of the thermalized structure with the monitor=True parameter. Passing the .traj file is critical because it preserves the velocities from the NVT run, providing a continuous MD sequence.
bash mace.run_md( structure_data="thermalization_md/<formula>_<temp>K_nvt.traj", # Pass .traj to preserve velocities temperature=933, ensemble="nve", steps=100000, timestep=2.0, monitor=True, monitor_type="melting", output_dir="production_md" )
Auto-Termination: The integrated monitor will:
Check for temperature and potential energy stability.
Automatically stop the MD simulation when the melting point is reached.
Log termination status in the research log.
mace.run_md will return once the simulation stops (either by finishing all steps or by monitor termination).
Phase Validation: Verify that the solid and liquid phases still coexist at the end of the simulation.
First, predict the atomic features of the final structure:
Fully Solidified: The NVE starting temperature was too low.
Fully Melted: The NVE starting temperature was too high.
Analysis: If coexistence is verified, calculate $T_m$ by averaging the temperature over the last 5 ps of the simulation.
Show full SKILL.md (79 more words)Show less
Examples
Creating a solid-liquid interface for Aluminum:
bash
${CLAUDE_SKILL_DIR}/../../venv/run cpu python ${CLAUDE_SKILL_DIR}/scripts/create_interface.py Al_solid.cif Al_liquid.cif --axis 0 --output Al_interface.cif
Constraints
Box Dimensions: The lattice parameters perpendicular to the stacking axis must be identical for both solid and liquid blocks.
Ensemble: The final production run must be in the NVE ensemble to allow the temperature to evolve to $T_m$.
Environments: Different MLIPs require specific environments (mlip for MACE and MatGL, fairchem for FairChem). Ensure the scripts are run within the correct environment for the chosen model.
Mat Melting Point next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Mat Melting Point compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Mat Melting Point this skilllearningmatter-mit/AtomisticSkills
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
Define a docking search box (center coordinates + box dimensions in Angstroms) from a co-crystal ligand, binding-site residues, or a saved JSON specification.
Calculate the melting temperature of a material using the solid-liquid interface (coexistence) method. Mat Melting Point is an agent skill from learningmatter-mit/AtomisticSkills. Calculate the melting temperature of a material using the solid-liquid interface (coexistence) method.
How do I install Mat Melting Point in Claude Code?
Run `npx skills add learningmatter-mit/AtomisticSkills --skill mat-melting-point -a claude-code`. Or copy the skill folder (skills/mat-melting-point in learningmatter-mit/AtomisticSkills) into .claude/skills/mat-melting-point in your project. Claude Code loads it when a task matches its description.
How do I install Mat Melting Point in Codex?
Run `npx skills add learningmatter-mit/AtomisticSkills --skill mat-melting-point -a codex`. Or copy the skill folder (skills/mat-melting-point in learningmatter-mit/AtomisticSkills) into .agents/skills/mat-melting-point in your project. Codex loads it when a task matches its description.
Can I use Mat Melting Point in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add learningmatter-mit/AtomisticSkills --skill mat-melting-point -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mat-melting-point, .gemini/skills/mat-melting-point, .github/skills/mat-melting-point and .opencode/skills/mat-melting-point in your project.
What does Mat Melting Point need to run?
Going by SKILL.md and its folder, Mat Melting Point needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Mat Melting Point access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Mat Melting Point safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Mat Melting Point use?
Mat Melting Point is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Mat Melting Point use?
About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Mat Melting Point?
Skills that share tags, products or a category with Mat Melting Point: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mat Melting Point?
learningmatter-mit (a GitHub organization) maintains it in learningmatter-mit/AtomisticSkills, which has 176 GitHub stars. The repository holds 129 skills in this directory. The repository was last updated on October 7, 2026.