migrate-to-builds

Tests Cloud Agent environment compatibility with prebuilt environment builds and recommends required changes.

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill migrate-to-builds-ferrarifankid04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-builds
Source: https://github.com/ferrarifankid04/ai-skills-public/tree/main/cursor/skills-cursor/migrate-to-builds
Command: npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill migrate-to-builds-ferrarifankid04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Migrating a Cursor Cloud Agent environment to prebuilt environment builds can break setup when install, start, and terminals phases are misconfigured. This Skill tests build compatibility, classifies configuration sources, and recommends the exact changes needed before enabling builds. ## Core Features & Use Cases - Build Compatibility Testing: Validates that the current Cloud Agent environment works with prebuilt environment builds before the user enables them on the Builds tab. - Phase Classification: Diagnoses misplaced setup work by classifying each action into install (durable repository setup), start (per-boot initialization), or terminals (long-running foreground processes). - Configuration Precedence Resolution: Determines whether the effective environment configuration comes from .cursor/environment.json, a personal saved environment, or a team saved environment. - Use Case: A team's Cloud Agent loses its dev server after every snapshot restore. The Skill identifies that the server was started in install, recommends moving it to terminals, and validates the fix with a build plus fresh-agent smoke test. ## Quick Start Test whether my current Cloud Agent environment is compatible with environment builds and tell me what changes are needed before I enable builds.

Frequently Asked Questions about migrate-to-builds

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

FAQPage Schema
How do I migrate a Cursor Cloud Agent environment to builds?

Run a build compatibility test against the current environment, fix any misplaced setup actions between install, start, and terminals, then validate with a build and fresh-agent smoke test. The user enables builds manually on the Builds tab after review.

What is the difference between install, start, and terminals in environment.json?

Install handles durable repository setup like package installation and code generation. Start runs per-boot initialization such as launching daemons. Terminals run long-running foreground processes like dev servers that the agent inspects and restarts.

Why does my dev server disappear after an environment snapshot restore?

The server was likely started during install, whose processes are not preserved as durable state. Move the server to terminals for visible logs and restarts, or to start if a process manager supervises it on every boot.

Which environment configuration source takes precedence in Cursor?

Cursor resolves configuration in this order: .cursor/environment.json from the repository revision, then a personal saved environment, then a team saved environment. The first available source wins.

Why does environment setup hang during install?

A foreground server, watcher, or interactive command is likely running in install, preventing it from completing. Identify the blocking command from setup logs and move long-running processes to start or terminals.