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 22 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+10added
Lines−10removed
From line
2
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 2, old and new numbered
/
from line 2
22
33> Fix every finding before you submit a plugin to the Claude plugin directory: what the developer portal's validation and scan check, and what each result means.
44
5Before the [Claude plugin directory](/docs/directory/publish) lists your plugin, the developer portal checks the plugin's files at two points. Validation runs in the plugin submission form at [claude.ai/directory/manage](https://claude.ai/directory/manage) when you select the **Validate** button. A scan runs after you submit, on each new commit that the directory picks up from the branch or tag that it follows. The scan checks the plugin's files again and runs a security scan.
5Before the [Claude plugin directory](/docs/directory/publish.md) lists your plugin, the developer portal checks the plugin's files at two points. Validation runs in the plugin submission form at [claude.ai/directory/manage](https://claude.ai/directory/manage) when you select the **Validate** button. A scan runs after you submit, on each new commit that the directory picks up from the branch or tag that it follows. The scan checks the plugin's files again and runs a security scan.
66
7Use this checklist to fix problems before you [submit your plugin](/docs/plugins/submit) from the developer portal on claude.ai. The checklist covers the automated checks only, and every plugin in the directory also has to follow the [Anthropic Software Directory Policy](https://support.claude.com/en/articles/13145358-anthropic-software-directory-policy). Start by [running the checks](#run-the-checks-before-you-submit) and [reading a validation result](#read-a-validation-result). Then use the tables in [what validation and the scan check](#review-what-validation-and-the-scan-check) to fix each finding, and [prepare for the security scan](#prepare-for-the-security-scan) that runs after you submit.
7Use this checklist to fix problems before you [submit your plugin](/docs/plugins/submit.md) from the developer portal on claude.ai. The checklist covers the automated checks only, and every plugin in the directory also has to follow the [Anthropic Software Directory Policy](https://support.claude.com/en/articles/13145358-anthropic-software-directory-policy). Start by [running the checks](#run-the-checks-before-you-submit) and [reading a validation result](#read-a-validation-result). Then use the tables in [what validation and the scan check](#review-what-validation-and-the-scan-check) to fix each finding, and [prepare for the security scan](#prepare-for-the-security-scan) that runs after you submit.
88
99## Run the checks before you submit
1010
from line 14
14142. [Validate in the developer portal](#validate-in-the-developer-portal), which runs every directory check in the tables on this page
15153. [Read the result](#read-a-validation-result), fix every finding that the report marks **Blocking**, and then submit
1616
17The portal is open to the people who [can submit](/docs/directory/publish#confirm-you-can-submit-to-the-directory). If you can't submit, ask someone who can to run **Validate**.
17The portal is open to the people who [can submit](/docs/directory/publish.md#confirm-you-can-submit-to-the-directory). If you can't submit, ask someone who can to run **Validate**.
1818
1919### Check the plugin on your machine (optional)
2020
from line 42
4242
4343**3. Enter the repository**
4444
45On the **Source** step, enter the repository. [Submit your plugin](/docs/plugins/submit#submit-a-plugin) describes each field.
45On the **Source** step, enter the repository. [Submit your plugin](/docs/plugins/submit.md#submit-a-plugin) describes each field.
4646
4747**4. Validate**
4848
from line 63
6363
6464Some problems with the repository stop validation before there is a report. The submission form then shows one error, such as **Couldn’t validate that repository**, and no findings. The tables in [what validation and the scan check](#review-what-validation-and-the-scan-check) mark those checks as "Validation stops".
6565
66[Submit your plugin](/docs/plugins/submit#after-you-submit-a-plugin) explains how review and publishing proceed after you submit.
66[Submit your plugin](/docs/plugins/submit.md#after-you-submit-a-plugin) explains how review and publishing proceed after you submit.
6767
6868## Review what validation and the scan check
6969
from line 168
168168
169169The security scan looks for behavior that a plugin doesn't disclose, such as sending data elsewhere, running hidden code, or changing Claude's permission settings.
170170
171A first submission that fails the security scan is rejected, and a later version that fails can't go live. A new version that the scan flags can be held for a reviewer. The **Versions** tab on the plugin's page in the developer portal shows **Didn’t pass the security scan**, or the category of the finding, such as **Sends data to an undisclosed destination**. [Submit your plugin](/docs/plugins/submit#fix-a-failed-version) explains what to do when a version doesn't pass.
171A first submission that fails the security scan is rejected, and a later version that fails can't go live. A new version that the scan flags can be held for a reviewer. The **Versions** tab on the plugin's page in the developer portal shows **Didn’t pass the security scan**, or the category of the finding, such as **Sends data to an undisclosed destination**. [Submit your plugin](/docs/plugins/submit.md#fix-a-failed-version) explains what to do when a version doesn't pass.
172172
173173To prepare, make the plugin's behavior visible in its README and its source:
174174
from line 181
181181
182182**1. Compare output with and without the plugin**
183183
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.
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.md#measure-whether-the-skill-improves-the-output) covers one skill at a time.
185185
186186**2. Load the plugin on each surface**
187187
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.
188Load the plugin on each surface your users will use, as [Test the plugin on each surface](/docs/plugins/build.md#test-the-plugin-on-each-surface) describes.
189189
190190## Next steps
191191
192* [Submit your plugin](/docs/plugins/submit): enter the repository in the developer portal, follow the review, and publish
193* [Publish to the directory](/docs/directory/publish): confirm your plan and role can submit, and see what Anthropic's review involves
192* [Submit your plugin](/docs/plugins/submit.md): enter the repository in the developer portal, follow the review, and publish
193* [Publish to the directory](/docs/directory/publish.md): confirm your plan and role can submit, and see what Anthropic's review involves
194194
No line in this hunk matches that.