executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
cloud-operationCloud infrastructure operations for AWS and RunPod. Use when managing EC2 instances, configuring AWS credentials, SSH connections, port forwarding, or managing RunPod GPU pods and serverless endpoints. Supports AWS and RunPod; extensible to other providers.
Independent GitHub snapshot · Automated classification · Original documentation governs
Manage cloud infrastructure across supported providers. Select the action and provider below, then follow the linked reference.
Announce your active role before taking any action:
As a {Role}, I will {action description}
| Action | Reference | When to use |
|---|---|---|
| Choose AWS credential method & sync MCP | aws-enable-cli.md | No AWS credentials configured yet, MCP disabled, or user has not chosen an auth method |
| Provision EC2 instance (VPC + networking) | aws-setup-ec2.md | Launching a new EC2 server |
| Connect to EC2 via SSH | aws-connect-ec2-ssh.md | Opening an SSH session to an EC2 instance |
| Forward a remote EC2 port to localhost | aws-ec2-tunnel.md | Accessing a service running on EC2 from a local browser or tool |
| EC2 CLI reference (concepts, commands, troubleshooting) | aws-ec2-cli.md | Constructing or debugging EC2 API calls |
| Action | Reference | When to use |
|---|---|---|
| Manage GPU pods, serverless, templates, volumes | runpod-manage.md | Any RunPod workload operation |
aws ... shell commands directly.aws-api skill.aws-api skill directly, e.g. S3, ECR, ECS, SES, Lambda, RDS, DynamoDB etc.aws-api MCP — run the aws-enable-cli action if missing.runpodctl installed and API key configured via runpodctl doctor.references/<provider>-<action>.md with the provider's workflow.