Security fixes are provided for the latest published version of SkillSync.

Please use GitHub's private Report a vulnerability flow for this repository. Do not open a public issue for credentials, private-vault exposure, unsafe path handling, or other security-sensitive findings.

Include:

• the affected SkillSync version;
• the operating system and installation method;
• a minimal reproduction;
• the expected and observed behavior;
• whether user files, Git credentials, or private skill content may be exposed.

SkillSync uses a user-owned private GitHub repository as its control plane. Every authenticated device with write access to that vault can change skill content and device assignments. SkillSync does not provide per-device access control for a shared multi-user vault.

Device-local skill targets and global instruction paths are approved on that device and stored outside the synced vault. Pulled vault state cannot authorize new local filesystem locations.

Skill folders can contain executable instructions or supporting scripts. Users should review third-party skills before adding them to a vault.

SkillSync checks vault files for symlinks, malformed JSON, stale registry entries, reserved ownership markers, and common credential formats before syncing or pushing. It also checks additions in unpushed commits for those credential formats. These checks reduce accidental exposure but cannot recognize every secret. Keep credentials, OAuth state, and session data out of skill folders and instruction profiles.