sim-paths

Validate critical simulation file paths on remote machines via SSH before GROMACS/plumed job submission.

1|1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/BioKT/Skills-BIOKT --skill sim-paths
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sim-paths
Source: https://github.com/BioKT/Skills-BIOKT/tree/main/sim-paths
Command: npx skills add https://github.com/BioKT/Skills-BIOKT --skill sim-paths

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that simulation files exist on a target machine before launching jobs, catching missing paths early and avoiding failed submissions.

Core Features & Use Cases

  • Remote path validation: checks essential simulation files (coordinates, topology, mdp, and related inputs) on the designated machine before submission.
  • Safe isolation: spawns a context-free subagent so the check does not inherit the current session's token budget.
  • Use cases: before submitting GROMACS/plumed jobs on machines such as rubisco, villin, insulin, calmodulin, agamede, or hyperion.

Quick Start

Spawn the general-purpose subagent on the target machine and supply the list of absolute file paths to verify.

Frequently Asked Questions about sim-paths

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

FAQPage Schema
How do I validate simulation file paths on a remote machine before job submission?

Validate simulation file paths on a remote machine by spawning a context-free subagent that uses SSH to run a test -e check for each absolute path, returning a machine-specified report of missing files before launch.

Can I check if GROMACS input files exist on remote machines like rubisco or hyperion?

Yes, you can check if GROMACS input files exist on machines like rubisco, villin, insulin, calmodulin, agamede, or hyperion by supplying a list of absolute file paths for remote existence verification prior to job submission.

What is the best way to preflight simulation files before launching remote jobs?

The best way to preflight simulation files is to spawn an isolated subagent that performs an SSH remote existence check on essential inputs such as coordinates, topology, and mdp files, catching missing paths early to avoid failed submissions.

How do I run a remote existence check for simulation paths without affecting my current session's token budget?

Run a remote existence check for simulation paths without affecting your token budget by spawning a context-free subagent that independently executes the SSH validation and returns the file path report.

Does path validation work for plumed workflows across multiple machines?

Path validation works for plumed workflows across multiple machines by verifying that all critical simulation input files are present on the designated target machine via an SSH connection before you submit the job.