Use dpdata Python Driver plugins to label systems (energies/forces/virials) via System.predict(), list available drivers, and build Driver objects (ase/deepmd/gaussian/sqm/hybrid). Use when working with dpdata Python API (not CLI) and you need driver-based energy/force prediction, plugin registration keys, or examples of using dpdata with ASE calculators or DeePMD models.
npx skills add https://github.com/jinzhezenggroup/computational-chemistry-agent-skills --skill dpdata-driver
Use dpdata “driver plugins” to label a dpdata.System (predict energies/forces/virials) and obtain a dpdata.LabeledSystem.
System into a LabeledSystem by computing:energies (required)forces (optional but common)virials (optional)In dpdata, this is exposed as:
System.predict(*args, driver="dp", **kwargs) -> LabeledSystemdriver can be:
"ase", "dp", "gaussian"Driver.get_driver("ase")(...)When unsure what drivers exist in *this* dpdata version/env, query them at runtime:
import dpdata
from dpdata.driver import Driver
print(sorted(Driver.get_drivers().keys()))
import dpdata ensures built-in plugins are loaded before listing registered drivers.
In the current repo state, keys include:
asedp / deepmd / deepmd-kitgaussiansqmhybrid(Exact set depends on dpdata version and installed extras.)
import dpdata
from dpdata.system import System
sys = System("input.xyz", fmt="xyz")
ls = sys.predict(driver="ase", calculator=...) # returns dpdata.LabeledSystem
assert "energies" in ls.data
# optional:
# assert "forces" in ls.data
# assert "virials" in ls.data
This is the easiest *fully runnable* example because it doesn’t require external QM software.
Dependencies (recommended): declare script dependencies with uv inline metadata, then run with uv run.
# /// script
# requires-python = ">=3.8"
# dependencies = [
# "dpdata",
# "numpy",
# "ase",
# ]
# ///
Script:
from pathlib import Path
import numpy as np
from ase.calculators.lj import LennardJones
from dpdata.system import System
# write a tiny molecule
Path("tmp.xyz").write_text("""2\n\nH 0 0 0\nH 0 0 0.74\n""")
sys = System("tmp.xyz", fmt="xyz")
ls = sys.predict(driver="ase", calculator=LennardJones())
print("energies", np.array(ls.data["energies"]))
print("forces shape", np.array(ls.data["forces"]).shape)
if "virials" in ls.data:
print("virials shape", np.array(ls.data["virials"]).shape)
else:
print("virials: <not provided by this driver/calculator>")
from ase.calculators.lj import LennardJones
from dpdata.driver import Driver
from dpdata.system import System
sys = System("tmp.xyz", fmt="xyz")
ase_driver = Driver.get_driver("ase")(calculator=LennardJones())
ls = sys.predict(driver=ase_driver)
Use driver="hybrid" to sum energies/forces/virials from multiple drivers.
The HybridDriver accepts drivers=[ ... ] where each item is either:
Driver instance{"type": "sqm", ...} (type is the driver key)Example (structure only; may require external executables):
from dpdata.driver import Driver
hyb = Driver.get_driver("hybrid")(
drivers=[
{"type": "sqm", "qm_theory": "DFTB3"},
{"type": "dp", "dp": "frozen_model.pb"},
]
)
# ls = sys.predict(driver=hyb)
dp requires deepmd-kit + a model filegaussian requires Gaussian and a valid executable (default g16)sqm requires AmberTools sqmGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take jinzhezenggroup/dpdata-driver from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.