Distribute to AI tools

Distribution makes a library Skill available to an AI tool on this computer. Desktop controls also call this sync. It differs from device sync, which exchanges library content between computers.

Distribute to a tool

Open the Skill in My Skills.
Check its current targets and status.
Select a detected, enabled tool.
Review the scope and distribution prompt.
Check the target status when the operation finishes.

You can also select tools during installation or apply tool settings to several Skills. First confirm the directory in tool management.

Choose global or project scope

Scope	Target location	Use when
Global	The tool's user-level Skills directory	The tool should use the Skill across projects
Project	A Skills directory inside the selected project	The Skill should be available in that project

Project distribution requires an actual project directory. If you select several projects, each is a separate target. Keep the directories accessible. After moving a project, review the recorded distribution location.

macOS and Linux support project distribution for compatible tools. Windows currently supports global distribution only. Some tools do not support project scope. Entering a custom path does not bypass that limit.

Links and copies

Automatic mode prefers a symbolic link. On Windows, it can fall back to a directory junction, then to a copy. Cursor currently always uses a copy because it does not support these linked Skill directories.

A link points to the central library. A copy is a separate set of files that Skills Hub refreshes during updates. Manual edits in a tool copy do not automatically flow back to the library.

Custom tools can use an explicit sync mode. If permissions or mode support cause a failure, inspect the configuration and error first. Do not delete the central directory that a link points to.

Shared directories and existing files

Some tools share the same Skills directory. Distribution previews identify affected tools. Changing one target can change the content visible to another tool.

When a target already exists, the app checks ownership and content. Conflicting content is not overwritten by default. Identify the files, preserve any changes you need, then use the explicit resolution flow offered by the app.

Remove a target or retry

Removing a tool target removes its distribution while retaining the library record. Disabling the entire Skill attempts to remove tool-side sync while preserving library content and configuration. If cleanup fails, files can remain in tool directories. Inspect the reported locations; disabled status does not confirm that all files were removed.

Retry failed targets from their status controls. A source update failure does not mean that every deployed copy is unusable. A target failure does not mean that library installation failed. Read the specific error and use troubleshooting when needed.