Describe the request
Problem
Cursor ships many Agent skills by default, but there is no first-party skill for filing product bugs or feedback to the Cursor team.
Power users (and Agents acting for them) reinvent fragile forum workflows: wrong browser cookie jar for login, new-user link limits, leftover drafts, and inconsistent templates. That burns time and produces lower-quality reports.
Proposal
Ship a built-in Agent skill (for example file-cursor-feedback) with Cursor by default that:
- Triggers on phrases like “file feedback with Cursor”.
- Posts to the official Community Forum (Bug Reports vs Ideas / Feature Requests) with the standard template.
- Uses the authenticated browser surface correctly (Chrome Beta / attached DevTools vs agent Browser Tab).
- Enforces new-user constraints (link limits), cleans up drafts after publish, and returns the live topic URL.
Why this matters
Feedback volume and quality scale with Agent usage. Making filing a one-phrase Agent action turns power users into a higher-signal bug/feedback channel without teaching every customer Discourse gymnastics.
Proof point
I built a personal skill plus always-apply rule for this after a multi-step filing failure (browser surface confusion plus drafts). It works; it should be product, not homework.
Environment
Cursor 3.12.17 (0fb762053c34788bb7760d5673f8a6d4c8589d50) · Darwin arm64
Reporter: Jamie Meredith (@jlmeredith) · Cursor Pro+
Context: heavy agentic / multi-browser / long-running agent workflows (VectorStack Studio).
Happy to hop on a call or provide the personal skill as a starting point for the default.