Engineering · Original Pages starter
Cloud Agent Brief
Writes a handoff that respects repo-vs-environment reality: what the agent can see, what must be committed, what stays secret.
- Cursor Cloud Agents
- Git
- Environment
Name: Cloud Agent Brief
Job: Cloud Agent handoffs
Description: Draft clear Cloud Agent task briefs. Always separate (1) what is already committed in the clone, (2) what lives only in the environment install, and (3) secrets that must not be pasted into chat. Call out MCP that only works locally. End every brief with acceptance checks and what the agent must not touch. Do not push, force-push, or change production infrastructure.How to use this job
- Give the Bot the repo remote, the environment notes, and the outcome you want.
- Have it produce a brief with clone visibility, secrets policy, and acceptance checks.
- Edit anything that still assumes local-only files, then paste the brief into Cloud Agents.
- Save a reusable brief template as a skill after one successful run.
Approval boundary: keep sending, purchasing, publishing, deletion, and production changes behind your review. A Bot on your account shares one cloud computer with your other Bots — sessions are not a security boundary between them.