Remote Computer

Configure and provision a remote development VM on AWS EC2 or Google Cloud Compute Engine, or a local SSH-ready Linux development container with apple/container on an Apple silicon Mac. Verify provider context, size the machine (host-aware container resource suggestions and Dockerfile configurations saved under ~/Documents/Containers), 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 creat

22 stars 1 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add paoloanzn/remote-computer --skill remote-computer
Manual install
git clone --depth 1 https://github.com/paoloanzn/remote-computer.git /tmp/remote-computer
mkdir -p ~/.claude/skills
cp -r /tmp/remote-computer/. ~/.claude/skills/remote-computer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Remote Computer

Provision one auditable development VM at a time: an AWS or Google Cloud VM, or a local Apple container, which is a Linux VM on the user's Mac that is reached and tracked exactly like a cloud VM. Resolve bundled `scripts/`, `references/`, and `assets/` paths relative to the directory containing this `SKILL.md`, not the user's current project. Treat cloud creation, firewall changes, billable resources, image builds, volumes, and containers as consequential actions: inspect first, show the exact deployment summary, and obtain explicit confirmation immediately before creating resources.

## Non-negotiable rules

- Never expose credentials, private key contents, access tokens, or cloud credential files.
- Treat VM-access keys, GitHub authentication keys, and commit-signing keys as separate roles. Never replace or remove one while configuring another.
- Never copy HTTPS tokens or credential-store contents between computers. Prefer a verified SSH key or an interactive `gh auth login` flow.
- Ask explicitly before copying any private SSH key or GPG secret key to a VM. Show paths and fingerprints, never key contents.
- Never assume that a tier is free. Show provider, region/zone, machine type, disk, image, network exposure, and likely billing status before confirmation.
- Restrict SSH ingress to the user's confirmed public IPv4 `/32` or IPv6 `/128`; do not open port 22 to the world unless the user explicitly requests it after a warning.
Read the full skill on GitHub

Details

Skill name
remote-computer
Repo updated
22 October 2026

FAQ

What does the Remote Computer skill do?

Configure and provision a remote development VM on AWS EC2 or Google Cloud Compute Engine, or a local SSH-ready Linux development container with apple/container on an Apple silicon Mac. Verify provider context, size the machine (host-aware container resource suggestions and Dockerfile configurations saved under ~/Documents/Containers), 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 creat

How do I install the Remote Computer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add paoloanzn/remote-computer --skill remote-computer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Remote Computer popular?

It lives in paoloanzn/remote-computer, which has 22 GitHub stars and 1 forks.

Related skills

Oss Launch

16

AnayDhawan/oss-launch

Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG, .gitignore, .github/ issue + PR templates, CI/CD). Also covers launch (GitHub metadata, badges, Show HN, Reddit, YouTube), release cadence (SemVer + CHANGELOG), and demo-GIF generation. Triggers on "open source this", "OSS checklist", "prep for launch", "make this repo public", "add a license / co

Git & Code Review

Irpf Brasil

19

Danielbluz/skill-irpf-brasil

Assistente especializado em Imposto de Renda Pessoa Física (IRPF) Brasil — ciclo 2026, ano-base 2025. Use quando o usuário mencionar "IRPF", "Imposto de Renda", "declaração de IR", "malha fina", "DARF", "REVAR", "Cashback IRPF", "pré-preenchida", "Núcleo Familiar", "restituição IR", "bets imposto", "ComprovaBet", "e-Social IR", "DIRF", "ganhos bolsa imposto", "day trade", "GCAP", "ganho de capital", "vender imóvel", "isenção 180 dias", "MEI declaração", "lucro distribuído", "espólio inventário herança", "saída definitiva exterior", "residência fiscal", "IRPFM", "imposto mínimo", "Lei 15.270",

Git & Code Review

Github Stars Curator

22

Leexunhuan743/github-stars-curator

Organize starred GitHub repos into stable, clear lists: detect new stars, download READMEs into a local corpus, classify each repo against the taxonomy, and sync the approved mapping back to GitHub via gh. Use this when a user wants their starred repos sorted into lists, a recent batch of new stars filed incrementally, or their star-list taxonomy reviewed and refined. Do not use for general GitHub issue/PR management, repo code search, or bookmarking non-GitHub resources.

Git & Code Review

Git Ship

20

oil-oil/git-ship

自动化 Git 工作流一键发布助手,执行完整的「ship」流程: 基于最新 main 切新分支 → commit → 推送 → 创建 PR → squash merge → 回 main。 调用 ship 本身就是对完整流程的授权;自动推断分支名、commit message 和 PR 内容, 并主动解决 Git 冲突、测试、lint、类型检查、构建和 CI 失败,持续修复和重试, 直到改动成功合并。不要因可自行修复的失败暂停,只在认证、权限、仓库保护等 无法由当前环境解决的外部阻塞出现时请求用户介入。 仅在用户明确表达「ship」意图时触发,例如: - 直接说「ship」「/ship」「git ship」 - 明确要求完整走完 git 流程:「帮我走一遍 git 流程」「拉 main、切分支、提 PR、合并」 - 使用类似「发布这次改动」「把这些改动提成 PR 并合并」的表达 不应触发的情况: - 只是想 commit - 只是想创建 PR - 只是想 push 代码 - 讨论 git 相关问题或解释 git 概念

Git & Code Review

Repo to Skill

19

shuyhere/repo-to-skill

Generate an agent skill from a GitHub open-source repository. Use when asked to create a skill from a repo URL, turn a GitHub project into a usable skill, or generate skill files for a CLI/library/framework. Triggers on phrases like "create a skill from this repo", "make a skill for vllm", "turn this GitHub project into a skill", "generate a skill from repo". Also use when asked to "skillify" a tool or generate usage instructions from source code. Command usage — `/skill repo-to-skill <github-repo-url>`.

Git & Code Review

Rsshub Route Authoring Skill

27

AboutRSS/rsshub-route-authoring-skill

Author PR-ready RSSHub routes — namespace.ts, route handler, Radar rules and PR description — that survive code review. Distilled from 2,727 route PRs. Use when asked to write, fix or review an RSSHub route, add an RSS feed for a website via RSSHub, contribute a route to DIYgod/RSSHub, or when working with cheerio selectors, cache.tryGet, parseDate, Radar rules, or the RSSHub PR template. Trigger on RSSHub, RSS route, RSS feed for X, 给 X 做 RSS 订阅, namespace.ts, DataItem. Do not use for deploying RSSHub, debugging runtime errors, tuning cache/config, or non-RSSHub scraping.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.