Feature request for product/service
Cursor Web
Describe the request
Why is there no official .cursor/skills/create-automation or /create-automation flow for defining Cursor Web Automations from inside the repo?
Why can’t Cursor Web read repo-defined automation specs from something like .cursor/automations and let me “Run automation from file” in the web interface?
Context: I create and refine automation instructions in my code repo first, then manually copy them into the Cursor Web Automations UI. This works, but it makes automations harder to version, review, reuse, and share with teammates.
Suggested workflow:
.cursor/
- skills/
-
- create-automation/ SKILL.md
- automations/
-
- weekly-dependency-check/AUTOMATION.md
Desired behaviour:
Cursor provides an official /create-automation or .cursor/skills/create-automation skill.
The skill helps generate valid Cursor Web Automation specs.
Cursor Web can detect .cursor/automations/*.
In the Web UI, I can choose “Run automation from file” or “Create automation from file”.
Cursor keeps the web automation linked to the repo file, or at least shows when the file and web version diverge.
This would fit naturally with existing .cursor/skills and .cursor/rules patterns. Automations are powerful, but currently feel too detached from the repository configuration layer.
