Hey, thanks for the feature request. Point by point.
For Cloud Agents, skills from the repo already work. Put the skill in .cursor/skills/ or agents/skills and commit it, Cloud Agents will pick it up. Directory details are in the docs: Agent Skills | Cursor Docs. This covers your custom MCP case that needs a companion skill. Keep the skill in the repo next to the code and it ships with the agent, no manual install needed for each user.
If the model doesn’t pull the skill in automatically, reference it explicitly in your message, for example, “use the fix-flaky-tests skill”. The backend loads skills onto the VM on every step, so the agent can access them even if they don’t show up in the slash menu.
There isn’t a separate button to “roll out a skill to the whole team from the dashboard” like there is for cloud MCP right now. The closest managed option is Team Marketplaces: Plugins | Cursor Docs. You wrap the skill as a plugin and mark it as Required, then it gets installed for everyone automatically. But that’s Teams or Enterprise only, so for an individual account the repo approach above is usually more practical.
I’ve logged the request for a native managed rollout of skills for Cloud Agents. Let me know how it goes with .cursor/skills/.
Hey Dean,
To add some more context we’re using ‘home’ on the cloud agent for our BI / analytical needs. Everyone needs access to it and there is no repo.
Canvas has been great btw and this is our way to build on top of it.
Sorry, I keep saying cloud agent. It’s the local agent in the ‘home’ section. We just need a shared skill and then we can use the shared global rule in cursor to always use that skill when the mcp is used.
Thanks for the clarification, that changes things. Without a repo, the advice about putting .cursor/skills/ in the project won’t work.
For a local agent, you can keep home skills in the global folder ~/.cursor/skills/ on your machine. Then the skill is available in every project even without a repo, and you can hook it up to a global rule so it gets pulled in when you use the right MCP. That solves your case on a single machine.
What you can’t do natively yet is share that kind of custom skill with a team without a repo, similar to how cloud MCPs or team rules/commands are shared. The closest managed option is to wrap the skill as a plugin in the Team Marketplace and mark it as Required so it installs for everyone automatically. But that’s only available on Teams/Enterprise, so it won’t work for an individual account.
If there’s an update, I’ll reply in the thread.
Glad you liked Canvas, by the way.
AH OK!
I was unaware of this feature! We’re on a team account (I have a personal and a company account. Company account is team)
Huge unlock right now. Thanks man.