Export a generated Skill to a local directory, or bind it to a target AI Agent to establish a continuous sync; understand chips, conflict takeover, unbinding, and sync status.

After generating a Skill, you have two ways to land it: export to a directory, or bind it to an AI Agent.

Screenshot placeholder: The export button and AI Agent binding chips inside the Skill preview panel, showing the default state, the takeover confirmation dialog, and the warning-color state.

Export to a Directory

Suitable for:

Saving a copy of the Skill output first
Manually inspecting the file structure
Handing the result over to another environment

When exporting, MCP2Skill lets you choose an output directory and then writes the generated files into it.

Exporting is a one-time write; it does not update automatically when the source changes. If you want the Skill to keep following the source, use binding instead.

Bind to an AI Agent

Suitable for:

You already know exactly where an AI Agent's Skills directory is
You want the Skill to keep following the source, instead of staying frozen at the moment it was generated

A binding is not a one-time file write — it is a continuous subscription. In the Skill preview, click the chip of the target AI Agent to create a binding. MCP2Skill generates the Skill once immediately, and then regenerates the corresponding Skill directory automatically whenever the tool list, workspace members, skill_description, gateway port, remote access toggle, or API Key change.

A few things to know:

If a skill with the same name already exists in the target directory, MCP2Skill first prompts "the binding will take over and overwrite", and writes only after confirmation
Clicking the same chip again unbinds; unbinding shows a confirmation dialog and deletes the generated directory by default
When the chip appears in a warning color, the binding could not be written to disk (sync failed or the Agent directory is unavailable); clicking it retries the sync
The full list of bindings is on the Skills > Bindings page, where you can view by Agent, manually sync, or unbind

Binding vs. Export at a Glance

Aspect	Export to a Directory	Bind to an AI Agent
Write behavior	One-time write to the chosen directory	Continuous subscription; auto-regenerates on source changes
Destination	Any external directory	The configured AI Agent Skills directory
Source changes	Does not follow updates	Auto-regenerates
Cleanup	Manual	Unbinding deletes the directory by default
Management entry	File system	The `Skills > Bindings` page

To understand sources and generation modes first, see Generate Skills.

What Unbinding Does

Unbinding shows a confirmation dialog and deletes the generated directory by default.

With deletion enabled: MCP2Skill removes the binding and deletes the corresponding Skill directory
Without deletion enabled: only the subscription is removed, leaving the directory files in place (it then falls into the "External" group and no longer auto-updates)

If you only want to stop syncing temporarily and keep the existing files, leave deletion unchecked; if you are sure you no longer need it, checking deletion is cleaner.

Managed vs. External

Skills produced by bindings appear in the "Managed" group on the Skills page, carry a source badge, and follow the source for automatic updates. Directories from one-time exports or manual placement belong to the "External" group and are neither regenerated nor cleaned up by the binding engine.

For how to tell them apart and how to delete them, see Manage Installed Skills.

To understand generation and sources first: see Generate Skills
To configure the binding target directory: see General and MCP Settings
To view installed and managed Skills: see Manage Installed Skills
To learn about the gateway mode as a second path: see Connect External AI Clients

After generating a Skill, you have two ways to land it: export to a directory, or bind it to an AI Agent.

Screenshot placeholder: The export button and AI Agent binding chips inside the Skill preview panel, showing the default state, the takeover confirmation dialog, and the warning-color state.

Export to a Directory

Suitable for:

Saving a copy of the Skill output first
Manually inspecting the file structure
Handing the result over to another environment

When exporting, MCP2Skill lets you choose an output directory and then writes the generated files into it.

Exporting is a one-time write; it does not update automatically when the source changes. If you want the Skill to keep following the source, use binding instead.

Bind to an AI Agent

Suitable for:

You already know exactly where an AI Agent's Skills directory is
You want the Skill to keep following the source, instead of staying frozen at the moment it was generated

A few things to know:

If a skill with the same name already exists in the target directory, MCP2Skill first prompts "the binding will take over and overwrite", and writes only after confirmation
Clicking the same chip again unbinds; unbinding shows a confirmation dialog and deletes the generated directory by default
When the chip appears in a warning color, the binding could not be written to disk (sync failed or the Agent directory is unavailable); clicking it retries the sync
The full list of bindings is on the Skills > Bindings page, where you can view by Agent, manually sync, or unbind

Binding vs. Export at a Glance

Aspect	Export to a Directory	Bind to an AI Agent
Write behavior	One-time write to the chosen directory	Continuous subscription; auto-regenerates on source changes
Destination	Any external directory	The configured AI Agent Skills directory
Source changes	Does not follow updates	Auto-regenerates
Cleanup	Manual	Unbinding deletes the directory by default
Management entry	File system	The `Skills > Bindings` page

To understand sources and generation modes first, see Generate Skills.

What Unbinding Does

Unbinding shows a confirmation dialog and deletes the generated directory by default.

With deletion enabled: MCP2Skill removes the binding and deletes the corresponding Skill directory
Without deletion enabled: only the subscription is removed, leaving the directory files in place (it then falls into the "External" group and no longer auto-updates)

If you only want to stop syncing temporarily and keep the existing files, leave deletion unchecked; if you are sure you no longer need it, checking deletion is cleaner.

Managed vs. External

For how to tell them apart and how to delete them, see Manage Installed Skills.

To understand generation and sources first: see Generate Skills
To configure the binding target directory: see General and MCP Settings
To view installed and managed Skills: see Manage Installed Skills
To learn about the gateway mode as a second path: see Connect External AI Clients

Export and Bind Skills

Export to a Directory

Bind to an AI Agent

Binding vs. Export at a Glance

What Unbinding Does

Managed vs. External

Table of Contents

Export and Bind Skills

Export to a Directory

Bind to an AI Agent

Binding vs. Export at a Glance

What Unbinding Does

Managed vs. External

Table of Contents