Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →awslabs/hyperpod-ssm
Remote command execution and file transfer on SageMaker HyperPod cluster nodes via AWS Systems Manager (SSM). This is the primary interface for accessing HyperPod nodes — direct SSH is not available.
Passed 19 of 21 test cases with the skill, and 9 of 21 without it.
and 12 more in the full report
11 fixed9 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
When executing non-interactive commands on a SageMaker HyperPod node via SSM using `AWS-StartNonInteractiveCommand` without specifying a user account, under which Linux user account do commands run by default?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies root as the default non-interactive user account | Missed | Passed |
The instructions your model reads when the skill loads.
aws CLI v2, authenticated for the target account/Region.session-manager-plugin — installed alongside the AWS CLI.jq — the scripts build JSON payloads with it.unbuffer (from the expect package) — wraps aws ssm start-session with a PTY so the session-manager-plugin flushes stdout instead of racing to close. Without it, calls intermittently return empty output with Cannot perform start session: EOF even when the command ran. Install with sudo yum install expect, sudo apt install expect, or brew install expect. ssm-exec.sh detects and uses it automatically; falls back with a warning if missing.Target: sagemaker-cluster:<CLUSTER_ID>_<GROUP_NAME>-<INSTANCE_ID>
CLUSTER_ID: Last segment of cluster ARN (NOT the cluster name). Extract via get-cluster-info.sh.GROUP_NAME: Instance group name — retrieve via list-nodes.sh.INSTANCE_ID: EC2 instance ID (e.g., i-0123456789abcdef0)Three scripts under scripts/. Resolve cluster info and nodes once, then execute per node.
scripts/get-cluster-info.sh CLUSTER_NAME [--region REGION]
# Output: {"cluster_id":"...","cluster_arn":"...","cluster_name":"...","region":"..."}
scripts/list-nodes.sh CLUSTER_NAME [--region REGION] [--instance-group GROUP] [--instance-id ID]
# Output: JSON array of ClusterNodeSummaries (InstanceId, InstanceGroupName, InstanceStatus, etc.)
list-cluster-nodes paginates at 100 nodes. This script handles pagination automatically.
test cases passed, vs 9 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.