Overview
ASE Skill (Jinzhe Zeng Group) is an instruction-based entry point for ASE-related task preparation within the computational-chemistry-agent-skills collection. Its role is to classify a request and delegate it to a workflow or calculator branch, rather than perform atomistic calculations itself. The named Skill describes routes for static calculations, relaxation, molecular dynamics and NEB workflows, with GPAW and MACE identified as optional backend adapters.
The router takes a user's task intent and gathers the minimum context needed for the appropriate branch. Workflow requests go to ase/ase-workflows; backend selection or configuration requests go to ase/ase-calculators. When a request combines both concerns, it starts with the workflow branch and treats calculator configuration as a dependency. Its specified output is a selected branch path, an explanation of that choice, any missing minimum inputs and an explicit next delegation step.
This separation keeps workflow decisions distinct from calculator-specific setup. The top-level instructions prohibit directly embedding task-specific or backend-specific parameters and prohibit executing calculations. Python and ASE are stated requirements, with GPAW or MACE needed only for the corresponding adapter. Task preparation is the stated scope; execution, when requested, is delegated through dpdisp-submit. The supplied excerpt documents the routing contract, but does not establish the detailed behavior of the downstream branches or demonstrate scientific validation.
Key Features
- Routes static, relaxation, molecular dynamics and NEB task intents to `ase/ase-workflows`.
- Routes backend selection and calculator configuration requests to `ase/ase-calculators`, with GPAW and MACE named as optional adapters.
- Handles mixed workflow/backend requests by selecting the workflow branch first and delegating calculator setup as a dependency.
- Requires a structured routing response containing the branch path, selection rationale, missing minimum inputs and next delegation step.
- Separates task/configuration preparation from execution, directing requested submission and running to `dpdisp-submit`.
Use Cases
- Intended evaluation: check whether an assistant routes static, relaxation, molecular dynamics and NEB preparation requests to the documented workflow branch.
- Intended evaluation: assess whether GPAW or MACE configuration questions are delegated to the calculator branch without introducing backend parameters at the top level.
- Intended evaluation: use a combined workflow/backend request to inspect delegation order, identification of missing inputs and separation of preparation from execution.
How to Use
- Read the named Skill as routing instructions, not as an executable agent or an ASE installation guide.
- Describe the intended task: static calculation, relaxation, molecular dynamics, NEB, backend selection or a combination. Provide available context and let the router identify missing minimum inputs rather than assume task parameters.
- Check the selected branch. Workflow intent should lead to
ase/ase-workflows; backend setup should lead toase/ase-calculators. A mixed request should begin with the workflow branch. - Inspect the response for all four required elements: branch path, selection rationale, missing inputs and the next delegation step. Evaluate routing behavior separately from any later scientific calculation.
- Consult the collection repository for the delegated instructions. Confirm the stated Python/ASE requirements and relevant optional backend dependencies. Keep execution outside this router; the Skill identifies
dpdisp-submitfor requested submission and running.