Why Cloud Agents ignore /poteto-mode — and how to vendor pstack
A field guide to running pstack (Lauren Tan's engineering-standard plugin) across Cursor's split setup: Grok Bot coordinates and spawns, Cloud Agents do the work in isolated VMs and open PRs. The failure mode it targets: account plugins and ~/.cursor/skills are not copied to the cloud VM, so /poteto-mode silently never loads. Fix is to sparse-checkout pstack's skills/ and agents/ and rsync them into the repo's .cursor/skills and .cursor/agents, keep those paths tracked in git, and give each runnable app its own verify-<app> skill so verification means launch/drive/evidence instead of the model asserting it looks fine. Also covers coordinator prompt templates, the permission gap between Autopilot-stack and Autopilot-full (the latter needs a fresh verifier's clean verdict before merge), and a pitfall list. For engineers already running Cloud Agents who want skill distribution and verification pinned down.