📁 Bot Templates
SWE Bot Template Prompt: Repo Triage and Cloud Agents
Paste repo context and guardrails: get a Cursor SWE Grok Bot template setup plan, first tasks, cloud-agent handoff rules, and connector notes.
1Reviews
Prompt
Act as an engineering lead who briefs a new teammate installing Cursor's SWE Grok Bot template. You turn the owner's repo facts into a safe first week. You do not invent CI status, issue ids, or plugin availability. Inputs: - Repo name and primary stack: [RepoStack] - What "done" means for a coding task: [DoneDefinition] - Issue sources (GitHub, Linear, pasted list): [IssueSources] - Environments the bot may touch (dev only, staging, never prod): [Environments] - Proof expected on every PR: [ProofRules] - Connectors already linked vs missing: [Connectors] - Human approval gates (merge, deploy, secrets): [ApprovalGates] - Quiet hours and ping rules: [PingRules] - Output format: [Format] Generate: 1. One-line job for this SWE bot copy (write code, triage, monitor) with three hard anti-jobs. 2. First-run checklist after importing from the marketplace page, including connecting the tools named in Connectors (the public listing shows no packaged integrations). 3. Intake form for a new task: required fields before any cloud agent launch. 4. Triage rubric: how to label blocked, ready, needs-design, and out-of-scope using only IssueSources facts. 5. Cloud-agent handoff template: goal, constraints, tests, proof artifacts, stop conditions. 6. PR review starter: risk-first questions the bot should answer before nits. 7. Monitoring loop: what to watch, when to ping per PingRules, when to stay quiet. 8. Worked example using only the Inputs (invent nothing outside them). Rules: link the public marketplace page only as https://x.ai/bot/marketplace/bots/seed-a91e4c when you mention the official SWE template. Never ask for passwords or API keys in chat. Harbor Dock (fictional) is the example product name if needed.
Instructions
Replace every [bracket]. Planning text works on ChatGPT, Claude, and Gemini; the live bot is the SWE template (https://x.ai/bot/marketplace/bots/seed-a91e4c). Harbor Dock is fictional. Bot drafts and opens work; humans merge and handle secrets. The public SWE listing only says it writes code, triages issues and monitors production; cloud agents and GitHub here are tools you connect yourself. Cursor is a trademark of Anysphere, Inc., Grok and xAI marks belong to their owner, and PromptDig is not affiliated with either.
Generated Output
This image was generated using the prompt above.

Examples
Example Input
RepoStack: harbor-dock-api, TypeScript Node service with Postgres, Vitest, GitHub Actions DoneDefinition: PR open with tests green locally, screenshot or curl proof for the changed endpoint, and a risk note IssueSources: GitHub issues labeled eng; no Linear Environments: local and preview deploys only; never production credentials ProofRules: failing test made to pass, or new test added; curl before/after for API changes; no invented coverage percents Connectors: GitHub connected; Cursor cloud agents available; Slack not connected yet ApprovalGates: human merges; human rotates secrets; bot may open PRs but not merge PingRules: ping only when blocked more than 30 minutes, PR ready for review, or a watch alert fires; quiet otherwise Format: setup plan plus one sample triage of issue #214 if present in notes (issue title only: timeout on POST /bookings)
Example Output
1. JOB Own eng tasks on harbor-dock-api: triage GitHub issues, launch cloud agents for scoped fixes, and open PRs with proof. Anti-jobs: no production deploys, no merges, no secret rotation. 2. AFTER ADD Open https://x.ai/bot/marketplace/bots/seed-a91e4c only as the source recipe reference if reinstalling. Reconfirm GitHub. Confirm cloud agents run. Skip Slack until connected. Tell the bot Environments and ApprovalGates in the first message. 3. TASK INTAKE Issue link or number, acceptance checks, files likely touched, forbidden areas, proof expected, deadline if any. 4. TRIAGE RUBRIC ready: acceptance clear and local-repro known; needs-design: API contract unclear; blocked: missing credentials or flaky fixture; out-of-scope: production-only change. 5. CLOUD-AGENT HANDOFF Goal: fix timeout on POST /bookings per issue #214. Constraints: TypeScript service only; no schema migration without a separate task; preview env only. Tests: reproduce with Vitest or a failing integration test; leave it green. Proof: failing test -> passing; curl POST /bookings before/after on preview. Stop: if production credentials are requested, stop and ping. 6. PR REVIEW STARTER What can break bookings? What is untested? Did the description match the diff? Then nits. 7. MONITORING Watch CI on open PRs and the named preview. Ping on red CI after retry, or when PR is ready. Otherwise quiet. 8. SAMPLE Issue #214 title timeout on POST /bookings -> label ready if local repro exists; else needs-design asking for a HAR or log snippet. No merge by the bot.