Repository access: Only select repositories → pick that one repo
Under Repository permissions, find Contents
Change the Contents dropdown from No access → Read and write
Leave other permissions on No access (Metadata stays Read-only automatically)
Paste the token when SkillBridge asks (stored in OS-backed Secret Storage)
Push from the machine that has your skills
On other machines: configure the same owner/repo + a PAT for that repo, then Pull
Repository rules
Empty repo (or only GitHub defaults like README/LICENSE): accepted and initialized by SkillBridge
Already synced by SkillBridge: accepted (detected via managed README marker). This is how a second computer works even though the repo is no longer empty
Any other non-empty repo: rejected, so SkillBridge never overwrites unrelated projects
Settings
Setting
Default
Description
skillBridge.skillsPaths
["~/.cursor/skills", "~/.agents/skills"]
Local skills folders to sync
skillBridge.githubRepository
(empty)
Target GitHub repo (owner/repo)
On GitHub, folders are kept separate:
skills/cursor/ ← ~/.cursor/skills
skills/agents/ ← ~/.agents/skills (including installs from npx skills add)
That way another machine restores each skill into the same kind of folder.
Commands
SkillBridge: Open Menu
SkillBridge: Configure GitHub Repository
SkillBridge: Update GitHub Token
SkillBridge: Push Skills
SkillBridge: Pull Skills
SkillBridge: Check Sync Status
Publishing
Store release steps (Marketplace + Open VSX + GitHub secrets): PUBLISHING.md.