Cloud env setup + human git identity

When to use

• Brand-new project that will run on Cursor Cloud Agents
• Existing repo that still commits as Cursor Agent with a Co-authored-by: trailer
• You want Cloud Agent commits attributed to the human (and optionally SSH-signed as them)

What this skill adds (on top of /env-setup)

1. Cursor /env-setup first — agent-driven Cloud Environment setup (deps, Build/snapshot, install / start / terminals). Do not skip it.
2. This skill second — drop in git identity scripts + hooks and wire them into install / start.
3. Secrets last — tell the human how to set personal Cloud Agent secrets for name, email, and optional signing key.

Keep stack-specific install steps (Ruby, Node, Postgres, etc.) in the project's own .cursor/install.sh / start.sh. This skill only owns the git attribution layer.

Preferred git handling (defaults this skill installs)