cloud-dev

Start, stop, and list cloud development EC2 instances via MCP tools.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/codepresso-dev/codepresso-ai-plugin --skill cloud-dev-codepresso-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cloud-dev
Source: https://github.com/codepresso-dev/codepresso-ai-plugin/tree/main/skills/cloud-dev
Command: npx skills add https://github.com/codepresso-dev/codepresso-ai-plugin --skill cloud-dev-codepresso-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers waste time opening the AWS console or writing CLI commands just to start or stop their personal cloud development EC2 instance, and often forget to stop instances, incurring unnecessary cost. ## Core Features & Use Cases - Instance Status Check: Query the current state of your tagged dev instance directly from Claude Code or Codex. - Start/Stop Control: Start a stopped instance and get its public IP, or stop a running instance with a single confirmation. - Team Instance Listing: Display a table of all team instances with Name, Email, State, and IP columns. - Use Case: At the start of your workday, ask to start your dev environment, receive the public IP once running, and rely on the auto-stop Lambda to shut it down when idle. ## Quick Start Ask the assistant to start my cloud dev instance and show me its public IP address.

Frequently Asked Questions about cloud-dev

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

FAQPage Schema
How do I start my EC2 dev instance from Claude Code?▼

Ask to start your cloud dev instance and the skill calls the cloud_dev_start MCP tool. Once running, it reports the public IP address so you can connect immediately.

How do I check the status of my cloud development environment?▼

The skill calls the cloud_dev_status MCP tool to retrieve the current state of your instance. It then presents available actions based on whether the instance is running or stopped.

What AWS configuration is required for EC2 instance management?▼

You need AWS credentials configured via CLI profile, environment variables, or IAM role. Instances must be tagged with Purpose=cloud-dev-env and your git email, with region defaulting to ap-northeast-2.

Can I see all team EC2 instances, not just my own?▼

Yes, the cloud_dev_list MCP tool displays a table of all team instances with Name, Email, State, and IP columns. Select the show all instances option when prompted.

What happens if no instance is found or credentials fail?▼

The skill shows the error message clearly and suggests running codepresso:setup or configuring AWS credentials. It does not attempt further actions until the configuration issue is resolved.

Do I need to manually stop my EC2 dev instance?▼

No, an auto-stop Lambda shuts down the instance after it has been idle. The skill reminds you of this after starting an instance, though manual stopping is still available.