菜单
Guides working with exe.dev VMs. Use when the user mentions exe.dev, exe VMs, *.exe.xyz, or tasks involving exe.dev infrastructure.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Debugs Buck2 build failures systematically by analyzing error logs, checking common issues (cache, visibility, cycles), and suggesting fixes. Use when builds fail, tests won't run, or Buck2 reports errors.
Scaffolds new Buck2 projects with proper BUILD/PACKAGE files, SPDX headers, and depot shims. Use when creating new Rust binaries/libraries, Deno tools, or C++ projects in the monorepo. Ensures consistent structure and metadata from the start.
Runs common Buck2 queries for dependency analysis, target inspection, and build graph exploration. Use when investigating dependencies, finding reverse dependencies, filtering by rule type, or understanding target relationships in the monorepo.
This skill should be used when determining which Buck2 targets are affected by code changes for incremental builds and tests. Use this when users ask to test/build changed code, find affected targets, or run incremental workflows with jj revisions.
Comprehensive testing workflow that should be used proactively after ANY code changes. Covers immediate testing, recursive package validation with `...`, target determination for affected packages, and reverse dependency testing. Use this skill after modifying BUILD files, changing code, fixing tests, or before committing to ensure nothing breaks downstream. (project)
Create Buck2 tests with local resources (processes, services, databases) using LocalResourceInfo and ExternalRunnerTestInfo. Use when tests need external dependencies like databases, HTTP servers, message queues, or Unix sockets that Buck2 should manage automatically. (project)
| name | using-exe-dev |
| description | Guides working with exe.dev VMs. Use when the user mentions exe.dev, exe VMs, *.exe.xyz, or tasks involving exe.dev infrastructure. |
exe.dev provides Linux VMs with persistent disks, instant HTTPS, and built-in auth. All management is via SSH.
The index is organized for progressive discovery: start there and follow links as needed.
ssh exe.dev help # show commands
ssh exe.dev help <command> # show command details
ssh exe.dev new --json # create VM
ssh exe.dev ls --json # list VMs
ssh exe.dev rm <vm> # delete VM
ssh exe.dev vm-logs <vm> # boot logs for debugging
ssh <vm>.exe.xyz # connect to VM
scp file.txt <vm>.exe.xyz:~/ # transfer file
Every VM gets https://<vm>.exe.xyz/ with automatic TLS.
ssh exe.dev <command> — the exe.dev lobby. A REPL for VM lifecycle, sharing, and configuration. Does not support scp, sftp, or arbitrary shell commands.ssh <vm>.exe.xyz — a direct connection to a VM. Full SSH: shell, scp, sftp, port forwarding, everything.Coding agents often run SSH in non-interactive shells or sandboxes. Common issues and workarounds:
scp/sftp failures: Ensure you're targeting <vm>.exe.xyz rather than exe.dev. Use ssh-based workarounds.
Hung connections: Non-interactive SSH can block on host key prompts with no visible output. Use -o StrictHostKeyChecking=accept-new on first connection to a new VM.
SSH config: Check whether both destinations are configured to use the right key:
Host exe.dev *.exe.xyz
IdentitiesOnly yes
IdentityFile ~/.ssh/id_ed25519