skilldock

What you will run into

What this tool solves: skill files are scattered across multiple directories for Claude Code / Cursor / Codex, and copying them by hand is easy to mess up. SkillDock is a desktop app that installs, organizes and git-syncs skills for these tools — it scans skill directories, installs skills from Git repos/skills.sh/ClawHub, syncs to multiple tools in one click, and tracks upstream updates and local changes. When to use it:

• You maintain skills across several Agents and want one management entry;
• You want to install skills from Git repos and keep them updatable;
• You want to preview upstream update diffs before applying.

When not to use it: a pure Linux/headless environment — this entry only has Windows/macOS assets, no Linux build (not run in this environment). Notes: desktop GUI entry (Windows 10+ / macOS); this doc is based on release metadata + official README audit, commands and expected results are honestly labeled by source.

Path: Quick fix (30s, one command) -> Step by step (skimmable) -> How to confirm it works (success criteria). In a hurry? Jump to Quick fix.

Why this happens

How it works: the installer (Windows setup.exe / macOS dmg) installs a desktop app. On first launch it automatically scans the skill directories of Claude Code/Cursor/Codex/Windsurf etc., groups skills into managed/unmanaged/conflicted; installs skills from a Git URL/skills.sh/ClawHub; syncs to the selected tools in one click; previews diffs before Git updates. Key concepts:

• Skill directory scanning: auto-discovers each tool's skill locations;
• Multi-tool sync: one copy of a skill distributed to multiple Agents;
• Git updates: tracks upstream + local changes, preview then apply.

Where it writes: ~/.config/SkillDock / ~/.skilldock (app config); writes to each tool's skill directory when syncing.

Step by step

Step 1: Install the app (Windows / macOS, pick one)

Why: Windows uses the setup.exe install wizard; macOS drags the dmg into Applications. Mainland GitHub direct is slow, downloads go through the gh-proxy prefix. Note: this entry only has Windows/macOS assets, no Linux build.

curl -sL -o SkillDock_x64-setup.exe https://gh-proxy.com/https://github.com/wanghuan9/skilldock/releases/download/v1.0.15/SkillDock_1.0.15_x64-setup.exe
./SkillDock_x64-setup.exe

Expected output: install wizard (default: next to finish) macOS branch:

curl -sL -o SkillDock.dmg https://gh-proxy.com/https://github.com/wanghuan9/skilldock/releases/download/v1.0.15/SkillDock_1.0.15_aarch64.dmg
open SkillDock.dmg

Expected output: drag into Applications After install, confirm:

• the app launches and enters the main UI;
• it auto-scans the local skill directories of each tool.

Stuck? How to recover:

• download slow → confirm the gh-proxy prefix; retry on another network;
• app won't open → confirm the OS version (Windows 10+ / macOS) and asset match (x64 vs aarch64).

Step 2: Install a skill from a Git repo (GUI)

Why: Skills → Install → paste the Git URL; the skill is added and can optionally sync to the target tool.

# GUI: Skills → Install → paste the Git URL

Expected output: skill added, optionally synced to the target tool After install, confirm:

• the skill shows in the managed list.

Stuck? How to recover:

• can't install → confirm the repo URL and network; whether the skill format matches the app's requirements (documented in the official README/docs).

Step 3: One-click multi-tool sync + Git update (GUI)

Why: in the skill detail, tick the target tools and Sync to distribute; before a Git update, preview the diff (upstream update vs local changes), then Update/Push after confirming.

# GUI: skill detail → tick Claude Code/Codex/Cursor → Sync

Expected output: skill distributed to the selected tools (no hand-copying files)

# GUI: skill list → review upstream updates/local changes → preview → Update/Push

Expected output: diff preview before updating, apply after confirming Stuck? How to recover:

• sync overwrites hand-edited skills → multi-tool sync writes each tool's skill directory, back up before syncing;
• behavior changes after Git update → read the diff preview carefully before applying.

How to confirm it works

Step 1: Confirm the app launches and scans skills

Why: the app launches into the main UI and auto-scans the local tool skill directories, which means the install and read path both work.

# GUI: open SkillDock, confirm the main UI and the scanned skill list

Expected output: app main UI + list of local tool skill directories Stuck? How to recover:

• app won't open → confirm the OS version (Windows 10+ / macOS) and asset match (x64 vs aarch64);
• no skills scanned → confirm the target tool's skill directory exists (SkillDock reads each tool's standard skill directory).

Step 2: Confirm skill install and sync

Why: installing a skill from a Git repo makes it appear in the managed list, and after Sync to the target tool the corresponding files appear in that tool's skill directory — the skill management path is confirmed.

# GUI: Skills → Install → paste the Git URL → tick the target tool → Sync

Expected output: skill added + distributed to the selected tool directories Stuck? How to recover:

• can't install → confirm the repo URL and network; whether the skill format matches the app's requirements (documented in the official README/docs);
• sync overwrites hand-edited skills → back up before syncing (sync writes each tool's skill directory).

Other environments

• Platform: only Windows (setup.exe) and macOS (dmg) assets, no Linux build; pick x64 / aarch64 by platform.
• Write surface: app config ~/.config/SkillDock / ~/.skilldock; writes to each tool's skill directory when syncing (shared write surface, back up before syncing).
• Desktop app form: no CLI, no background service; no conflict matrix pairs for co-install (GUI runs independently).

Daily usage

Startup and entry

Desktop app, launch from Start menu/Applications.

Common operations

Operation 1: Scan each tool's skill directories

# GUI: open the app → auto-scan Claude Code/Cursor/Codex/Windsurf etc. skill directories

Expected output: grouped list of managed/unmanaged/conflicted entries Operation 2: Install a skill (Git repo / skills.sh / ClawHub)

# GUI: Skills → Install → paste the Git URL

Expected output: skill added, optionally synced to the target tool Operation 3: One-click multi-tool sync

# GUI: skill detail → tick Claude Code/Codex/Cursor → Sync

Expected output: skill distributed to the selected tools (no hand-copying files) Operation 4: Git update (track upstream + local changes)

# GUI: skill list → review upstream updates/local changes → preview → Update/Push

Expected output: diff preview before updating, apply after confirming

Data and directories

• App config: ~/.config/SkillDock / ~/.skilldock;
• Writes to each tool's skill directory when syncing (Claude Code/Cursor/Codex etc.).

Uninstall & cleanup

note: platform uninstaller + config cleanup; managed shared config is not restored

# Windows: Settings → Apps → uninstall SkillDock; macOS: drag to Trash
rm -rf ~/.config/SkillDock ~/.skilldock 2>/dev/null || true
ls ~/.config/SkillDock ~/.skilldock 2>/dev/null | grep -q . && echo '残留: SkillDock 配置仍在' || echo 'skilldock removed: OK'

Expected output: skilldock removed: OK

Dependency warnings

• Version: [1.0.15, 1.0.15] locked (collection structure confirmed version).
• Environment: Windows 10+ / macOS (no Linux asset); x64 / aarch64 assets by platform.
• Network: GitHub direct is slow — must use the gh-proxy prefix (verified path).
• Write surface: app config ~/.config/SkillDock / ~/.skilldock; writes to each tool's skill directory when syncing (shared write surface, back up before syncing).
• Co-install: no conflict matrix pairs (desktop app form).

FAQ

• Q: Is there a Linux version? A: No. This entry only has Windows/macOS assets.
• Q: Will sync overwrite my hand-edited skills? A: Git updates have a diff preview (upstream vs local changes); but multi-tool sync writes each tool's skill directory — back up before syncing.
• Q: Use it with skillspector? A: Different forms (desktop management vs security scanning), no shared write-surface conflict; security advice: after installing skills, run skillspector to scan before enabling.
• Q: Where to report problems? A: install/uninstall issues on this marketplace go through the entry feedback channel; project issues go to the author's repository.