dpdisp-submit

Convert shell commands into DPDispatcher job configurations for local or HPC schedulers.

124|25|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jinzhezenggroup/computational-chemistry-agent-skills --skill dpdisp-submit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dpdisp-submit
Source: https://github.com/jinzhezenggroup/computational-chemistry-agent-skills/tree/main/tools/dpdisp-submit
Command: npx skills add https://github.com/jinzhezenggroup/computational-chemistry-agent-skills --skill dpdisp-submit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly turning ad-hoc shell commands into trackable, reproducible DPDispatcher jobs that run on local machines or HPC clusters.

Core Features & Use Cases

  • Converts shell commands into DPDispatcher job configurations.
  • Supports submission to local execution or schedulers (Slurm, PBS, LSF) with state tracking and auto-recovery.
  • Ensures safe, constraint-driven job submission without direct SSH or credential handling.

Quick Start

Run the dpdisp-submit workflow to submit your shell-based task to a cluster or local queue.

Frequently Asked Questions about dpdisp-submit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit shell commands to an HPC cluster using DPDispatcher?

To submit shell commands to an HPC cluster using DPDispatcher, this Skill translates your ad-hoc shell commands into trackable submission configurations for local execution or schedulers like Slurm, PBS, and LSF with built-in state tracking.

Can I submit jobs to Slurm, PBS, or LSF schedulers without direct SSH usage?

Yes, you can submit jobs to Slurm, PBS, or LSF schedulers without direct SSH usage. This Skill enforces safe operation by generating constraint-driven DPDispatcher configurations that prevent leakage of credentials during submission.

Does DPDispatcher support state tracking and auto-recovery for HPC job submissions?

DPDispatcher does support state tracking and auto-recovery for HPC job submissions. When converting your shell commands into submission configurations, the workflow automatically applies these features for local machines and cluster schedulers.

What is the best way to turn ad-hoc shell commands into reproducible cluster jobs?

The best way to turn ad-hoc shell commands into reproducible cluster jobs is converting them into DPDispatcher submission configurations. This approach ensures trackable execution across local environments and common HPC schedulers.

Are there limitations when using DPDispatcher for local job execution?

A key limitation is that DPDispatcher operates strictly by translating shell commands into submission configurations. It enforces safe operation by avoiding direct SSH usage entirely, meaning manual SSH interventions are not supported.