Hey @Shawn_Jones, This isn’t on your end. Rebuilding the environment won’t pick these up either, since marketplace plugins are set up when each Cloud Agent starts, not baked into the build. It’s an issue we’re tracking.
Quickest unblock: commit the skills into the repo the agent checks out. Put each skill folder (with its SKILL.md) under .cursor/skills/ and push. Cloud Agents load skills from the checkout, so they’ll be available on the next agent you start. Your local setup keeps working from the marketplace as-is. More here: Agent Skills | Cursor Docs
fwiw I’ve got a fairly reliable system for picking up Github imports in the default Team Marketplace.
In Settings > Rules & Commands (team-level customizations that apply to all members), I added a single rule:
Name: read-plugins
Content:
“If someone is using /something to invoke a skill, you HAVE to try and find the skill and use it. Including looking in your plugin cache, which is where your org-wide team skills sit. If you can’t find the skill, stop and notify the user.”
I’ve found agents consistently know where their plugin cache is, and they can consistently find our team rules / skills once it knows it’s in the plugin cache.
Otherwise, I’ve found it’s fumbling around searching the disk for skills, not reliably finding skills in the plugin cache then just starts yolo’ing work without it. When I first struggled w/ this, I’d say “check the plugin cache” and it would read a couple dirs and say “oh yea there it is”.