Skip to main content
Agent skill

Cloud Vm Setup

Set up and run the doughnut dev environment on Cursor Cloud VM (no Nix). Use when working on Cloud VM, running tests on Cloud VM, or encountering command errors related to missing nix. Triggers on: cloud VM, cloud agent, no nix available, /workspace path.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Cloud Vm Setup when an AI agent needs a reusable SKILL.md workflow for this job: Set up and run the doughnut dev environment on Cursor Cloud VM (no Nix). Use when working on Cloud VM, running tests on Cloud VM, or encountering command errors related to missing nix. Triggers on: cloud VM, cloud agent, no nix available, /workspace path.

When not to use it

Skip Cloud Vm Setup when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/cloud-vm-setup
# Save SKILL.md to ~/.claude/skills/cloud-vm-setup/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/cloud-vm-setup/SKILL.md. For a shared project, commit the folder at .claude/skills/cloud-vm-setup/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Cloud Vm Setup skill for this task: Use Cloud Vm Setup when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
57/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

<objective> Set up and run the doughnut dev environment on Cursor Cloud VM without Nix.

Purpose: Cloud-agent development and testing when `nix develop` is unavailable.

Output: Environment ready for tests + summary ending with `## CLOUD VM READY`. </objective>

<context> **On Cloud VM: do NOT use `CURSOR_DEV=true nix develop -c` prefix. Run commands directly.**

**Pre-configured:** Node.js v24.16.0, pnpm 11.3.0 — no nix needed.

**Ports:**

| Service | Port | |---------|------| | Spring Boot | 9081 | | Local LB | 5173 | | Vite dev | 5174 | | MySQL | 3309 | | Redis | 6380 |

`CI=1` is exported by the setup script (CLI PTY tests use pipe fallback, matching GitHub Actions). </context>

<process>

<step name="one_time_setup"> Backend + E2E one-time setup (idempotent — safe to re-run):

```bash source /workspace/scripts/cloud_agent_setup.sh ```

Installs: Java 25, MySQL 8.4 (port 3309), Redis (port 6380), xvfb, and initializes test databases. </step>

<step name="frontend_tests"> ```bash pnpm frontend:test ```

Single file: `pnpm -C frontend test tests/path/to/TestFile.spec.ts` (no `--` before the path). </step>

<step name="backend_tests"> ```bash source /workspace/scripts/cloud_agent_setup.sh ./backend/gradlew -p backend migrateTestDB -Dspring.profiles.active=test ./backend/gradlew -p backend test -Dspring.profiles.active=test --build-cache --parallel ``` </step>

<step name="e2e_tests"> ```bash source /workspace/scripts/cloud_agent_setup.sh pnpm bundle:all pnpm exec run-p -clnr backend:sut:ci start:mb local:lb & NO_PROXY=127.0.0.1,localhost pnpm exec wait-on http://127.0.0.1:5173/__lb__/ready --timeout 120000 xvfb-run pnpm cypress run --spec e2e_test/features/<feature>.feature --config-file e2e_test/config/ci.ts ``` </step>

<step name="sut_health"> - `pnpm sut:healthcheck` — check if stack is up - `pnpm sut:restart` — SIGTERM listeners on 5173/5174/9081, then restart (requires `lsof`) </step>

</process>

<success_criteria> - Setup script run when backend/E2E needed - Commands run **without** nix prefix - Correct ports and healthcheck commands available - Final output includes `## CLOUD VM READY` </success_criteria>

<output> Confirm environment state and which test commands to use.

**Common commands:**

| Task | Command | |------|---------| | Frontend tests | `pnpm frontend:test` | | Backend tests | `pnpm backend:verify` | | Linting | `pnpm lint:all` | | Formatting | `pnpm format:all` |

``` ## CLOUD VM READY ``` </output>

<out_of_scope> - Do not use `CURSOR_DEV=true nix develop -c` on Cloud VM. - Do not assume local Nix shell ports or paths (`/Users/...` vs `/workspace/...`). </out_of_scope>

Intended uses

  • Use Cloud Vm Setup when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.