Computational-chemistry-agent-skills dft-abinit

Route ABINIT requests to task-specific subskills based on user intent. Use when the user asks for ABINIT workflows and you must decide between static, relaxation, molecular dynamics, or electronic-analysis preparation. This orchestration skill dispatches to the correct ABINIT subskill and enforces consistent handoff to submission skills.

install

source · Clone the upstream repo

git clone https://github.com/jinzhezenggroup/computational-chemistry-agent-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/jinzhezenggroup/computational-chemistry-agent-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/quantum-chemistry/dft-abinit" ~/.claude/skills/jinzhezenggroup-computational-chemistry-agent-skills-dft-abinit && rm -rf "$T"

manifest: quantum-chemistry/dft-abinit/SKILL.md

source content

ABINIT Task Router

Use this skill as the top-level ABINIT orchestration layer.

Purpose

This skill routes requests to one task-specific ABINIT subskill path:

```
dft-abinit/static
```
```
dft-abinit/relax
```
```
dft-abinit/md
```
```
dft-abinit/electronic
```

Scope

This router skill should:

require user-provided structure or prerequisite context
classify request intent into one ABINIT task type
collect minimal shared context before dispatch
delegate detailed parameter handling to selected subskill
enforce consistent output/handoff policy across subskills

This router skill should not:

own detailed templates for all ABINIT tasks
execute or submit calculations
bypass subskill-specific guardrails

Hard requirement

The user must provide enough starting context:

structure input for
```
static
```
/
```
relax
```
/
```
md
```
prerequisite converged context for
```
electronic
```

If prerequisites are missing, stop and ask for them.

Routing rules

If user requests single-point SCF/energy: route to
```
dft-abinit/static
```
.
If user requests geometry optimization: route to
```
dft-abinit/relax
```
.
If user requests molecular dynamics: route to
```
dft-abinit/md
```
.
If user requests electronic analysis workflow: route to
```
dft-abinit/electronic
```
.
If intent is ambiguous, ask one focused clarification question before routing.

Shared policy for all subskills

do not invent missing pseudopotential files
expose assumptions and unresolved scientific choices explicitly
return handoff-ready task layout
if execution is requested, hand off to
```
dpdisp-submit
```

Output from router

Provide:

selected subskill path
why it was selected
minimal missing inputs (if any)
explicit next step (invoke selected subskill)