Schrodinger AWS Hpc Ssm Connector
Connect Claude Science to a remote Schrödinger Suite jobserver running on an AWS ParallelCluster (or any Slurm HPC) that is reachable only through AWS SSM, and submit/monitor/harvest Schrödinger jobs from it. Use this skill whenever the user mentions Schrödinger, jobserver, jsc, testapp, Maestro, Glide, Desmond, FEP+, or MMLIBS licensing on a remote cluster; whenever they want to reach an HPC head node "over SSM", "through Session Manager", "in a private subnet", or via an ssh_config ProxyCommand; or whenever an SSH compute provider that proxies over SSM fails to connect. It covers reducing SS
Install
npx skills add bioteam/claude-science-hpc-integrations --skill schrodinger-aws-hpc-ssm-connectorgit clone --depth 1 https://github.com/bioteam/claude-science-hpc-integrations.git /tmp/claude-science-hpc-integrations
mkdir -p ~/.claude/skills
cp -r /tmp/claude-science-hpc-integrations/skills/schrodinger-aws-hpc-ssm-connector ~/.claude/skills/schrodinger-aws-hpc-ssm-connectorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Claude Science → Schrödinger jobserver on AWS ParallelCluster (over SSM)
This skill is a field-verified playbook for wiring Claude Science to a
Schrödinger **jobserver** on an AWS ParallelCluster (or any Slurm cluster) whose
head/submit node is reachable **only through AWS Systems Manager (SSM)**. It was
built and confirmed end-to-end against a live cluster (Schrödinger 2026-1,
`jobserverd` 73163 / API v1.19.4, ParallelCluster + Slurm), so the failure modes
and fixes here are the ones that actually bite, not just the ones the manuals
predict.
## The one idea
Claude Science's native compute provider speaks **SSH**, not SSM. So the whole
integration is: **reduce the SSM channel to an ordinary SSH connection** using an
`aws ssm start-session` `ProxyCommand` in `ssh_config`, register the head node as
an SSH compute provider, and run `jsc`/`testapp` on it through the provider.
```
Claude Science ──SSH──▶ [ ProxyCommand: aws ssm start-session ] ──SSM──▶ head/submit node
│
jsc / testapp -HOST │ (gRPC/TLS :8030)
▼
jobserverd ──sbatch──▶ Slurm
```
## How jobs run
Run `jsc`/`testapp` **on the submit node** through the SSH-over-SSM provider —Details
- Skill name
schrodinger-aws-hpc-ssm-connector- Repository
- bioteam/claude-science-hpc-integrations
- Path
skills/schrodinger-aws-hpc-ssm-connector/SKILL.md- License
- MIT
- Repo updated
- 1 July 2026
FAQ
What does the Schrodinger AWS Hpc Ssm Connector skill do?
Connect Claude Science to a remote Schrödinger Suite jobserver running on an AWS ParallelCluster (or any Slurm HPC) that is reachable only through AWS SSM, and submit/monitor/harvest Schrödinger jobs from it. Use this skill whenever the user mentions Schrödinger, jobserver, jsc, testapp, Maestro, Glide, Desmond, FEP+, or MMLIBS licensing on a remote cluster; whenever they want to reach an HPC head node "over SSM", "through Session Manager", "in a private subnet", or via an ssh_config ProxyCommand; or whenever an SSH compute provider that proxies over SSM fails to connect. It covers reducing SS
How do I install the Schrodinger AWS Hpc Ssm Connector skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add bioteam/claude-science-hpc-integrations --skill schrodinger-aws-hpc-ssm-connector. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Schrodinger AWS Hpc Ssm Connector popular?
It lives in bioteam/claude-science-hpc-integrations, which has 5 GitHub stars and 1 forks.
Related skills
AWS Hpc Slurm Ssm Connector
5bioteam/claude-science-hpc-integrations
Connect Claude Science to a private-subnet AWS HPC cluster (AWS ParallelCluster, AWS PCS, or any Slurm head/login node) reachable ONLY through AWS Systems Manager (SSM), by reducing the SSM channel to an ordinary SSH connection the native compute provider can open. Works for AWS ParallelCluster and AWS PCS (same design; verified on ParallelCluster) as long as SSM access is enabled to the login/head node. Use whenever the user wants to reach an HPC head/login node "over SSM", "through Session Manager", "in a private subnet", or via an ssh_config ProxyCommand; mentions AWS ParallelCluster, AWS P
Create Pasqal Cloud Account
9pasqal-io/agent-marketplace
Get access to Pasqal Cloud - create the account on portal.pasqal.cloud and optionally couple it to Google Cloud Marketplace, which is what makes real QPUs and the advanced emulators available. For requests such as "create a Pasqal Cloud account", "I need a PASQAL_PROJECT_ID", "subscribe to Pasqal on GCP Marketplace", "how do I run on FRESNEL", or "my project only shows EMU_FREE". Access only, not running experiments. Unsure which route fits? Use choose-access-method.
Novnc
9Vincent-the-gamer/skills
Deploy noVNC — a browser VNC client — using websockify-js. Use when the user wants to view or control a VNC server in the browser, to set up noVNC + websockify, or needs GBK clipboard support in noVNC.
Adp Observability
9redpanda-data/skills
Read what Agentic Data Plane agents did and why, through traces, conversation transcripts, the audit log, and the monitoring views in the ADP UI at ai.redpanda.com and the `rpk ai` CLI. Use when finding which call made an agent run slow, failed, or expensive with `rpk ai trace`, reading or filtering a conversation with `rpk ai agent transcript`, finding conversations with a failed tool call, investigating a denied or masked call with `rpk ai auditlog`, working out on whose behalf an agent acted, or reading the Agent network or Home views. For budgets, cost, and access policies, see `/redpanda:
Cloud Byoc
9redpanda-data/skills
Provisions, changes, and tears down Redpanda Cloud BYOC (Bring Your Own Cloud) clusters through the Control Plane API and the `rpk cloud byoc` plugin, where the VPC, IAM roles, and storage stay in your own AWS, GCP, or Azure account. Use when creating or deleting a BYOC cluster or its Network, running `rpk cloud byoc` apply, destroy, or validate, scaling a BYOC cluster, editing its cloud provider tags or cluster properties, configuring its private connectivity and listeners, or setting up Shadow Link disaster recovery, cross-account AWS access, or Enterprise features such as Tiered Storage on
Octo Operator
10meshmakers/octo-claude-skills
Use this skill for developing and operating the OctoMesh Communication Operator — the .NET 10 KubeOps Kubernetes operator that watches CommunicationPool CRDs, connects to the Communication Controller over SignalR (/operatorHub), and runs helm upgrade/uninstall for Adapter and Application workloads. Covers edge vs central deployment modes, the Helm values layering model (context < base < overrides), secret injection tiers, CRD generation, the TUnit + Microsoft.Testing.Platform test workflow on .NET 10, and the local kind cluster developer loop. Also covers the octo-helm-core chart repository (o
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.