Global Plugins & Skills

Plugins add behavior to Amp, such as a tool or an agent mode. Skills give Amp instructions and files for a specific kind of task.

Amp stores personal and workspace plugins and skills in Git repositories. Amp calls them global because they are not tied to one project or machine. Amp loads them wherever you use it.

Choose a Scope

Scope	Who It Is For	Where It Works	Best Use
Personal	You	Everywhere you use Amp	Trying extensions before you share them
Workspace	Everyone in the workspace	Everywhere workspace members use Amp	Stable extensions shared with the whole team

Start with a personal plugin or skill. Once it works the way you want, share it or ask a workspace admin to publish it for everyone.

Personal plugins in Amp settings

Find Shared Plugins and Skills

Ask Amp to find plugins and skills that people in your workspace have shared:

Does anyone on my team share a skill for writing release notes?

Has anyone got a tmux plugin?

Amp can show you the shared item and its source before you import it. Plugins run code in your environment, so only import plugins you trust.

Import for Personal Use

For most shared items, add the plugin to your personal plugins or the skill to your personal skills. Paste its share URL into an Amp thread and say where to put it:

Import this shared plugin into my personal plugins: <shared-plugin-url>

For example, this imports an agent mode plugin from the Modes & Models collection:

Import https://ampcode.com/@amp/plugins/grok-46-mode.ts into my personal plugins.

Use the same form for a skill:

Import this shared skill into my personal skills: <shared-skill-url>

Amp copies the item into your personal repository and records where it came from so it can be updated later. Review the change, then let Amp commit and push it. The push publishes the import.

The Modes & Models page also shows commands such as amp plugins add --auto-update @amp/grok-46-mode. That command installs the plugin on the current machine. A hosted personal import is the recommended choice when you want the plugin everywhere you use Amp.

Create and Test Your Own

You do not need to clone or edit the repository yourself. Describe what you want in a thread:

Create a personal plugin that runs our formatter on every file the agent edits.

Create a personal skill for writing my release notes.

You can also ask Amp to add a project skill to your personal skills:

Import the browser-testing skill from this repo into my personal skills so I can use it on all my projects.

Amp opens the right repository and makes the change. It commits the result and asks before pushing. A push publishes the item. New threads load it automatically. Ask Amp to reload plugins or skills if you want to test it in the current thread.

Read Plugins to build tools, commands, hooks, and agent modes. Read Skills to define reusable instructions and resources.

You can share a personal plugin or skill without publishing it for everyone:

Open Personal Settings, then open Plugins or Skills.
Select the item and choose Share.
Make it available to your workspace.
Copy its share URL.

Send the URL directly or paste it into Slack. Teammates can inspect the shared page, import the item into their personal plugins or skills, and change their copy without changing yours.

Publish for Everyone

Workspace plugins and skills load for every workspace member. Workspace admins manage them. Test a large change in your personal plugins or skills before publishing it to the workspace.

An admin can ask Amp to copy a tested shared item into the matching workspace repository:

Copy Thorsten's plain-writing plugin into our workspace plugins.

Copy the shared release-notes skill into our workspace skills: <shared-skill-url>

Amp prepares a reviewable change in the workspace repository and asks before pushing it. The push publishes the change for the workspace.

Workspace skills in Amp settings

Update an Imported Item

Imported items do not overwrite your changes without asking. Ask Amp to check imports and prepare updates:

Check if any of my imported plugins are out of date.

Check if any of my imported skills are out of date.

You can also update one imported item from a checkout of its repository:

amp plugins update <name>
amp skill update <name>

Review, commit, and push the update to publish it.

Work With the Repositories Directly

Ask Amp to manage hosted plugins and skills unless you need direct Git access. These commands list the repositories available to you and whether you can write to them:

amp plugins repositories
amp skills repositories

Clone a repository with its short name:

amp clone user-plugins
amp clone user-skills
amp clone workspace-plugins
amp clone workspace-skills

Each repository is versioned with Git. Changes become active after you commit and push them. Repository owners can require signed commits in the repository’s advanced settings.

Project and Machine-Local Alternatives

Not every extension needs to be hosted globally:

Location	Use It When
`.amp/plugins/`	A plugin belongs to one project and should travel with its code
`.agents/skills/`	A skill belongs to one project and should travel with its code
`~/.config/amp/plugins/`	A plugin should run only on the current machine
`~/.config/agents/skills/`	A skill should run only on the current machine

amp plugins add <url> installs a machine-local system plugin by default. Its --target workspace option means the current project’s .amp/plugins/ directory, not the hosted Workspace Plugins repository. Use an Amp prompt or the repository workflow above to publish a hosted workspace plugin.