Plugin pre-submission checklist changedplugins/pre-submission-checklist
Nearest release: v2.1.288, published under an hour before 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 2 Oct 2026 19:01 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+21added
Lines−25removed
From line
32
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits7to this page, all time
The whole hunk
from line 32, old and new numbered
/
from line 32
3232
3333The portal's **Validate** button runs every check in this page's tables against your repository and gives you a report before you submit anything.
3434
35<Steps>
36 <Step title="Start a submission">
37 Open the [developer portal](https://claude.ai/directory/manage) and select **Submit new**.
38 </Step>
35**1. Start a submission**
3936
40 <Step title="Choose Plugin bundle">
41 When the portal asks **What would you like to submit?**, select **Plugin bundle**.
42 </Step>
37Open the [developer portal](https://claude.ai/directory/manage) and select **Submit new**.
4338
44 <Step title="Enter the repository">
45 On the **Source** step, enter the repository. [Submit your plugin](/docs/plugins/submit#submit-a-plugin) describes each field.
46 </Step>
39**2. Choose Plugin bundle**
4740
48 <Step title="Validate">
49 Select **Validate**. The report lists each finding with its result and, for many findings, a fix.
50 </Step>
41When the portal asks **What would you like to submit?**, select **Plugin bundle**.
5142
52 <Step title="Fix blocking findings and validate again">
53 The report covers only the commit that validation read, so it doesn't change when you push a fix. Push the fix, then select **Re-validate** on the **Source** step of the same form. When the new report has no findings with the **Blocks** result, continue through the form to submit the plugin.
54 </Step>
55</Steps>
43**3. Enter the repository**
5644
45On the **Source** step, enter the repository. [Submit your plugin](/docs/plugins/submit#submit-a-plugin) describes each field.
46
47**4. Validate**
48
49Select **Validate**. The report lists each finding with its result and, for many findings, a fix.
50
51**5. Fix blocking findings and validate again**
52
53The report covers only the commit that validation read, so it doesn't change when you push a fix. Push the fix, then select **Re-validate** on the **Source** step of the same form. When the new report has no findings with the **Blocks** result, continue through the form to submit the plugin.
54
5755### Read a validation result
5856
5957Validation produces a report in the submission form, and the scan's results appear on the plugin's page in the developer portal. Each finding has one of these results:
from line 179
181179
182180Validation and the scan check how the plugin is built. They don't check whether the plugin helps the people who install it. Before you submit, test the plugin's output and how it loads on the surfaces your users will use:
183181
184<Steps>
185 <Step title="Compare output with and without the plugin">
186 Run the plugin's skills on real prompts and compare the output with what Claude produces without the plugin. [`claude plugin eval`](https://code.claude.com/docs/en/plugin-evals) runs that comparison for the whole plugin in Claude Code, and [Measure whether the skill improves the output](/docs/skills/how-to#measure-whether-the-skill-improves-the-output) covers one skill at a time.
187 </Step>
182**1. Compare output with and without the plugin**
188183
189 <Step title="Load the plugin on each surface">
190 Load the plugin on each surface your users will use, as [Test the plugin on each surface](/docs/plugins/build#test-the-plugin-on-each-surface) describes.
191 </Step>
192</Steps>
184Run the plugin's skills on real prompts and compare the output with what Claude produces without the plugin. [`claude plugin eval`](https://code.claude.com/docs/en/plugin-evals) runs that comparison for the whole plugin in Claude Code, and [Measure whether the skill improves the output](/docs/skills/how-to#measure-whether-the-skill-improves-the-output) covers one skill at a time.
185
186**2. Load the plugin on each surface**
187
188Load the plugin on each surface your users will use, as [Test the plugin on each surface](/docs/plugins/build#test-the-plugin-on-each-surface) describes.
193189
194190## Next steps
195191
No line in this hunk matches that.