Agent Skill Sync
Sync agent skills from private or public GitHub repositories or a custom registry into your workspace. Enabled items are written under .cursor/rules (single-file rules) and .cursor/skills (skill packages). The Skill Manager gives you progressive browse, catalog search, and one-click enable or disable.
Works with VS Code 1.85+ and Cursor.
Getting started
- Install Agent Skill Sync from the marketplace (publisher KeskaLabsAB).
- Open the Skills activity bar view (or use Skill Sync: Manage AI Skills from the Command Palette).
- Sign in to GitHub when prompted if you use a private repository.
- Choose your source: connect
owner/repo for GitHub, or switch to custom registry mode and set the registry URL in settings.
- On the Manage tab, turn on the skills you want. Use Sync or wait for background sync so files appear under
.cursor/rules and .cursor/skills.
Screenshots
Browse the repository tree. Folders load on demand from GitHub.
Open folders to inspect files before you enable a skill.
Search the catalog by name, description, and category.
Filter the list and toggle skills on or off with one click.
What you can do
- Connect a private or public GitHub repo that hosts Cursor rules and/or skill packages.
- Use two kinds of content in one repo:
- Cursor rules — standalone
.mdc, .md, .yaml, or .yml files (synced as rules under .cursor/rules).
- Skill packages — a folder with a
SKILL.md manifest (agentskills.io open standard); the whole folder syncs to .cursor/skills/<name>/ when enabled.
- Browse the repo tree on demand without loading everything at once.
- Search the full catalog (name, description, category) after it is indexed.
- Use Manage to see what is enabled in this workspace and toggle skills quickly.
- Optionally use a custom registry with category-based listing.
- Sign in with GitHub for private repos (scopes include reading repositories you can access).
How a GitHub skills repo is laid out
The extension looks for skills under the first folder that exists, in this order: repository root (for dedicated skills repos), then skills, .skills, rules, .cursor/rules.
Example:
your-skills-repo/
├── api-documentation/ ← skill package
│ ├── SKILL.md ← required (see agentskills.io)
│ └── …
├── commit-message-style.mdc ← Cursor rule
└── security-code-review.md ← Cursor rule
Skill packages need a SKILL.md with YAML frontmatter, for example:
---
name: api-documentation
description: Templates and prompts for clear REST API docs.
metadata:
version: "1.0"
category: Documentation
---
Instructions and links for the agent go here.
The name in the manifest should match the folder name (lowercase). Supporting files in that folder are included when the skill is enabled.
Keyboard shortcut
| OS |
Default |
| Windows / Linux |
Ctrl+Alt+S |
| macOS |
Cmd+Alt+S |
Focuses the Skill Manager sidebar. Change it under Keyboard Shortcuts — search for Skill Sync: Focus Sidebar.
Settings
| Setting |
Purpose |
skillSync.sourceMode |
github-repo (default) or custom-registry |
skillSync.sourceRepository |
GitHub repo as owner/repo |
skillSync.registryUrl |
Base URL when using a custom registry |
skillSync.categories |
Category names for registry mode |
skillSync.optedInSkills |
Names of skills currently enabled for sync |
Open Settings and search for Agent Skill Sync to edit these, or use Preferences: Open User Settings (JSON).
Privacy
GitHub calls use your signed-in account. Skill files are fetched only for skills you enable and are written under .cursor/rules and .cursor/skills in the current workspace. Nothing is uploaded for analytics by this extension. For GitHub’s own policies, see GitHub documentation.
License
MIT — see LICENSE.
Publisher: KeskaLabsAB · Repository & issues · Sponsor
