exe-dev

**Judgement:** Potentially useful but immature and somewhat risky; best for experienced exe.dev users who can verify every action. **What it does:** - Manages exe.dev persistent VMs: list/create VMs, configure HTTP sharing and ports, manage collaborators, and support custom domains. - Wraps the documented CLI-style commands (e.g., `ssh exe.dev ls --json`, `ssh exe.dev new`, `ssh exe.dev share ...`). **Key strengths:** - Covers the core workflow for hosting and development on exe.dev (VM lifecycle, sharing, proxy/ports, custom domains). - Good fit for standing up persistent dev environments, personal services, and demos with HTTPS endpoints. - Leverages exe.dev’s authentication headers and sharing model for controlled access. **Risks and limitations:** - **Explicitly marked as auto-built and untested** by the author, so behavior may not fully match documentation and may contain bugs or missing parameters. - Misconfiguration could accidentally expose a VM or service publicly (e.g., `set-public`, incorrect port sharing, or overly broad share links). - Strongly tied to exe.dev; not useful outside that ecosystem and assumes the underlying exe.dev setup, billing, and permissions are in place. - Documentation snippet is high-level; some advanced or edge operations (teardown, SSH key nuances, cost control) may require manual CLI use or reading full docs. **Recommended scenarios:** - You already use exe.dev and want to **automate basic VM management** (create, list, share, adjust ports) from within an agent workflow. - Rapid **prototyping and demo hosting** where you can manually verify URLs, access control, and proxy configuration after each change. - **Developer sandboxes** or internal tools where occasional misconfigurations are tolerable and can be corrected via the exe.dev CLI or dashboard. **Use with extra caution if:** - The VM handles **sensitive data** or production workloads; double-check sharing and public access settings outside the skill. - You have **strict compliance or security requirements**; rely on manual review via exe.dev’s official tools until this skill is tested and validated. - You are unfamiliar with exe.dev; learn the native CLI and concepts first so you can detect and correct any mistakes the skill makes.