remote-computer
by paoloanzn14 days ago3Configure and provision a remote development VM on AWS EC2 or Google Cloud Compute Engine, verify cloud context, choose a machine tier, create dedicated VM-access SSH keys, optionally discover and port local Git/GitHub/GPG configuration with shared GitHub authentication keys, maintain the ~/.vms.json live-VM registry, reconcile status, and prepare direct SSH access. Use when a user asks to create, deploy, configure, resume, inspect, connect to, or prepare GitHub access on a remote cloud development VM on AWS or GCP.
Install
Show step-by-stepHide step-by-step
Open your terminal
- Mac: Press ⌘ Space, type "Terminal", press Enter
- Windows: Press Win R, type "cmd", press Enter
Paste the command above and press Enter
Use the Copy command button, then paste in your terminal (Mac: ⌘V, Windows: Ctrl V).
Restart Claude Code
Close and reopen Claude Code, or start a new session, so it picks up the new skill.
Where it lives
Comments
"just shipped remote-computer -- an agent skill that lets codex/claude spin up auditable dev VMs on AWS or GCP for you agent discovers your cloud CLI, picks..."
"just shipped remote-computer -- an agent skill that lets codex/claude spin up auditable dev VMs on AWS or GCP for you agent discovers your cloud CLI, picks..."
"just shipped remote-computer -- an agent skill that lets codex/claude spin up auditable dev VMs on AWS or GCP for you agent discovers your cloud CLI, picks..."
Related skills
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
maintainer-orchestrator
Coordinate multiple maintainer issues, PRs, or repositories with bounded workers, serialized public actions, and clear owner decisions. Do not use for one issue or PR.
setup-codebase-harness
Master skill — set up the full agent harness for any repo so an agent can work it reliably: legible (map-not-manual docs + custom lints), executable (one-command dev stack), verifiable (e2e gate + a verify-before-ship loop), plus commit hygiene and entropy control. Use when onboarding a new/unfamiliar codebase to agent-driven development — "set up the harness", "make this repo agent-ready", "harness this codebase".