Create a plugin with Claude changedplugins/create-with-claude
Nearest release: v2.1.283, published under an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 25 Sep 2026 18:00 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+42added
Lines−50removed
From line
6
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits3to this page, all time
The whole hunk
from line 6, old and new numbered
/
from line 6
66
77A plugin you create this way is for you. It lives on your account, and on a Team or Enterprise plan you can [share it](/docs/plugins/share) with specific people or your whole organization from its page in Customize. It isn't a directory listing; if you later want that, see [Submit a plugin you created with Claude](#submit-a-plugin-you-created-with-claude) at the end of this page.
88
9<Note>
10 * If you'd rather write the files yourself, see [Plugin structure and testing](/docs/plugins/build)
11 * If you want to make a plugin available to everyone in your organization, see [Publish a plugin to your organization](/docs/plugins/share#publish-a-plugin-to-your-organization)
12</Note>
9> [!NOTE]
10>
11> * If you'd rather write the files yourself, see [Plugin structure and testing](/docs/plugins/build)
12> * If you want to make a plugin available to everyone in your organization, see [Publish a plugin to your organization](/docs/plugins/share#publish-a-plugin-to-your-organization)
1313
1414To begin, [start a new plugin from the Add menu](#start-from-the-add-menu), [describe it to Claude and save it](#describe-and-save-the-plugin), then [review the plugin Claude made](#review-what-claude-made).
1515
from line 21
2121
2222To start a new plugin:
2323
24<Steps>
25 <Step title="Open the Add menu">
26 Go to [**Customize > Plugins**](https://claude.ai/customize/plugins) in claude.ai or the desktop app and select **Add**.
27 </Step>
24**1. Open the Add menu**
2825
29 <Step title="Choose how to create it">
30 Choose one of these:
26Go to [**Customize > Plugins**](https://claude.ai/customize/plugins) in claude.ai or the desktop app and select **Add**.
3127
32 * **Create with Claude**: start a new conversation, or a new Cowork task in the desktop app, with a request to create a plugin already filled in for you to send. Choose this when you can describe the task you want the plugin to handle but don't want to write skill files
33 * **Create a plugin**: fill in a form with the plugin's name and what it helps with, then write its skills, commands, and connectors in an editor. Choose this when you already know what each piece should say
34 </Step>
35</Steps>
28**2. Choose how to create it**
3629
30Choose one of these:
31
32* **Create with Claude**: start a new conversation, or a new Cowork task in the desktop app, with a request to create a plugin already filled in for you to send. Choose this when you can describe the task you want the plugin to handle but don't want to write skill files
33* **Create a plugin**: fill in a form with the plugin's name and what it helps with, then write its skills, commands, and connectors in an editor. Choose this when you already know what each piece should say
34
3735If neither item appears in the **Add** menu, plugin creation isn't available on your account. Your organization can turn it off, and so can your IT department's configuration of the desktop app. [Manage plugins for your organization](/docs/plugins/admin#control-what-members-add-themselves) covers the organization setting.
3836
3937### Describe and save the plugin
from line 38
4038
4139After you choose **Create with Claude**, a conversation opens where you tell Claude what the plugin is for, and Claude assembles it as a `.plugin` file that you save to your account:
4240
43<Steps>
44 <Step title="Describe what the plugin is for">
45 Tell Claude the job the plugin should help with, in the same words you'd use to explain it to a colleague: the task, when it comes up, and what a good result looks like.
46 </Step>
41**1. Describe what the plugin is for**
4742
48 <Step title="Answer Claude's questions">
49 Answer Claude's follow-up questions, such as which of your connectors the plugin should use. You can change any of it later.
50 </Step>
43Tell Claude the job the plugin should help with, in the same words you'd use to explain it to a colleague: the task, when it comes up, and what a good result looks like.
5144
52 <Step title="Save the plugin Claude assembles">
53 Claude writes the skills and commands, includes the connectors you chose, and shows the result as a file card in the conversation. Select **Save plugin** on that card to add it to your account. It's then listed under **Customize > Plugins**, on the **Yours** view.
54 </Step>
55</Steps>
45**2. Answer Claude's questions**
5646
47Answer Claude's follow-up questions, such as which of your connectors the plugin should use. You can change any of it later.
48
49**3. Save the plugin Claude assembles**
50
51Claude writes the skills and commands, includes the connectors you chose, and shows the result as a file card in the conversation. Select **Save plugin** on that card to add it to your account. It's then listed under **Customize > Plugins**, on the **Yours** view.
52
5753### Review what Claude made
5854
5955Check the plugin before you rely on it:
6056
61<Steps>
62 <Step title="Open the plugin">
63 Open **Customize > Plugins** and select the new plugin.
64 </Step>
57**1. Open the plugin**
6558
66 <Step title="Read what it contains">
67 Read the skills, commands, and connectors it contains.
68 </Step>
59Open **Customize > Plugins** and select the new plugin.
6960
70 <Step title="Sign in to its connectors">
71 Sign in to any bundled connector from the plugin's page.
72 </Step>
61**2. Read what it contains**
7362
74 <Step title="Try it on a real request">
75 Start a chat, or a Cowork task in the desktop app, with the kind of request the plugin is for, and check that Claude follows the plugin's skills.
76 </Step>
77</Steps>
63Read the skills, commands, and connectors it contains.
7864
65**3. Sign in to its connectors**
66
67Sign in to any bundled connector from the plugin's page.
68
69**4. Try it on a real request**
70
71Start a chat, or a Cowork task in the desktop app, with the kind of request the plugin is for, and check that Claude follows the plugin's skills.
72
7973## Use, disable, or remove your plugin
8074
8175The plugin is on your account for the organization you created it in, so it's available in your chats, in Cowork, and in Claude Code as a synced plugin.
from line 85
9185
9286Anthropic's directory reads plugins from a GitHub repository, so a plugin that lives only on your account can't be submitted as it is. If you decide you want it listed, get its files from the same conversation and go through the normal submission route:
9387
94<Steps>
95 <Step title="Ask Claude for the plugin as a folder">
96 In the conversation where Claude made the plugin, ask for it "as a plugin folder I can push to GitHub for the directory", download the zip Claude produces, and check that it has `.claude-plugin/plugin.json`, the `skills/` folder, a `README.md`, and a `LICENSE`.
97 </Step>
88**1. Ask Claude for the plugin as a folder**
9889
99 <Step title="Check the manifest and README">
100 Unzip the folder and compare `plugin.json` with [Write the manifest](/docs/plugins/build#write-the-manifest). Claude may include fields the manifest doesn't use and leaves placeholders such as your name for you to fill in. If you have Claude Code installed, run `claude plugin validate` on the folder, as [Check the plugin on your machine](/docs/plugins/pre-submission-checklist#check-the-plugin-on-your-machine-optional) describes.
101 </Step>
90In the conversation where Claude made the plugin, ask for it "as a plugin folder I can push to GitHub for the directory", download the zip Claude produces, and check that it has `.claude-plugin/plugin.json`, the `skills/` folder, a `README.md`, and a `LICENSE`.
10291
103 <Step title="Push and submit">
104 Push the folder to a public GitHub repository, then follow [Submit a plugin](/docs/plugins/submit).
105 </Step>
106</Steps>
92**2. Check the manifest and README**
93
94Unzip the folder and compare `plugin.json` with [Write the manifest](/docs/plugins/build#write-the-manifest). Claude may include fields the manifest doesn't use and leaves placeholders such as your name for you to fill in. If you have Claude Code installed, run `claude plugin validate` on the folder, as [Check the plugin on your machine](/docs/plugins/pre-submission-checklist#check-the-plugin-on-your-machine-optional) describes.
95
96**3. Push and submit**
97
98Push the folder to a public GitHub repository, then follow [Submit a plugin](/docs/plugins/submit).
10799
108100## Next steps
109101
No line in this hunk matches that.