# We shipped a Cursor plugin to make enterprise skills repo useful

**Agent Skill Sync** is a small extension that does one thing well: it pulls skills and rules from a GitHub repo (or a custom registry) and drops them where Cursor (and friends) actually look—`.cursor/rules` and `.cursor/skills`. No copy-paste. No “did everyone update the repo?” .

You can grab it on the Open VSX Registry: [**KeskaLabsAB / agent-skill-sync**](https://open-vsx.org/extension/KeskaLabsAB/agent-skill-sync).

* * *

## What it does (without the brochure voice)

You connect a source—usually `owner/repo` on GitHub. The Skill Manager opens in the sidebar: **Manage** for what’s on in *this* workspace, **Browse** if you want to poke around the tree like a civilized person. There’s also catalog search when you’d rather type “api docs” than click five folders.

Content-wise we support the boring-but-useful stuff:

*   **Single-file rules** (`.mdc`, `.md`, etc.) → synced as Cursor-style rules.
    
*   **Skill packages**—folders with a `SKILL.md` in the [agentskills.io](https://agentskills.io/specification) shape → whole directory lands under `.cursor/skills/<name>/` when you flip it on.
    

So your “skills repo” can be a real repo: versioned, reviewed, boring in a good way.

* * *

## Why we bothered publishing it

Internally we were already curating skills in git—security checklists, PR templates, little opinionated prompts that make agents less chaotic. The missing piece was **getting that into the editor without ceremony**. We got tired of documenting the manual steps for every new machine and every new teammate.

Publishing it was basically: *if we need this, someone else might too*—and Open VSX is a fine home for tooling that isn’t married to a single storefront. Same extension, same idea: **your skills live in source control; the editor just syncs what you opted into.**

* * *

## How to use it (the short path)

1.  **Install** from Open VSX: [agent-skill-sync](https://open-vsx.org/extension/KeskaLabsAB/agent-skill-sync).
    
2.  Open the **Skills** view (or run the command palette entry for managing skills—your muscle memory may vary).
    
3.  **Sign in to GitHub** if the repo is private; we use the normal provider flow, nothing exotic.
    
4.  Point it at your repo (`owner/repo`) or switch to registry mode if that’s your setup.
    
5.  On **Manage**, toggle what you want. Sync runs in the background or when you hit refresh—either way, files show up under `.cursor/rules` and `.cursor/skills` in the workspace you’re in.
    

Keyboard shortcut people: **Ctrl+Alt+S** (Windows/Linux) or **Cmd+Alt+S** (macOS) focuses the sidebar, unless you’ve remapped it to something weirder. We don’t judge.

Settings are the usual `skillSync.*` keys—source mode, repo string, registry URL, categories, opted-in list. If you live in JSON settings, you already know where to click.

* * *

## Fine print, but make it fashion

GitHub traffic uses **your** session. We’re not shipping analytics in the extension to tell you how often you toggled “API documentation.” Skills land in **your** workspace paths; nothing magic happens in our cloud because there isn’t one for this.

If something breaks, open an issue on [**github.com/keska-labs/enterprise-skills**](https://github.com/keska-labs/enterprise-skills). If it doesn’t break, enjoy the part where your agent actually reads the same files as the rest of the team.

* * *

*— Keska Labs*