plugin-submission skill
✓ VerifiedGovern the discovery, eligibility, and submission of plugins or skills to official directories, marketplaces, and registries.
- GitHub stars
- 13
- Files
- 2
- Last commit
- Nov 9, 2026
- License
- Apache-2.0
- Allowed tools
- —
What does the plugin-submission skill do?
plugin-submission is an agent skill. Govern the discovery, eligibility, and submission of plugins or skills to official directories, marketplaces, and registries.
Summary generated from the skill's SKILL.md.
About the plugin-submission skill
Managing the publication of plugins or skills to official marketplaces and registries is the primary function of this tool. It assists developers and project maintainers in navigating the complex requirements of different directories, GitHub lists, and curated registries. An agent should load this skill when preparing plugin listings, filling out marketplace forms, or drafting pull requests for directory inclusion.
The workflow involves classifying the destination, reading official submission instructions or CONTRIBUTING.md files, and validating eligibility against specific manifest schemas and license requirements. It produces a destination matrix containing policy evidence, eligibility verdicts, and staged payloads for every ready target. The tool relies on current policy documentation and destination-specific validators to ensure compliance.
To prevent errors, the process requires a final human confirmation before any external submission occurs. It strictly adheres to destination policies, meaning it will not attempt to automate forms that require human-authored recommendations or prohibit AI assistance. Every successful submission results in a recorded receipt, while rejections are documented with specific reasons for future action.
What an agent can do with it
- 1Validate plugin eligibilityCheck if a repository meets the specific license, manifest, and documentation standards of a marketplace.
- 2Ensure policy complianceVerify that a submission does not violate rules against automated or AI-assisted entries.
- 3Record submission historyCapture the results and identifiers of every attempt to list a skill in a directory.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the plugin-submission skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the plugin-submission skill in Plugin
/plugin marketplace add jpantsjoha/ai-native-developer-experience /plugin install devex-charter@join-the-team-marketplace
Install the plugin-submission skill in Claude Code
~/.claude/skills/plugin-submission/SKILL.md
$ npx degit jpantsjoha/ai-native-developer-experience/skills/plugin-submission ~/.claude/skills/plugin-submissionInstall the plugin-submission skill in Claude Code (project)
.claude/skills/plugin-submission/SKILL.md
$ npx degit jpantsjoha/ai-native-developer-experience/skills/plugin-submission .claude/skills/plugin-submissionInstall the plugin-submission skill in Codex
~/.agents/skills/plugin-submission/SKILL.md
$ npx degit jpantsjoha/ai-native-developer-experience/skills/plugin-submission ~/.agents/skills/plugin-submissionInstall the plugin-submission skill in Gemini CLI
~/.gemini/skills/plugin-submission/SKILL.md
$ npx degit jpantsjoha/ai-native-developer-experience/skills/plugin-submission ~/.gemini/skills/plugin-submissionInstall the plugin-submission skill in Claude.ai
npx degit jpantsjoha/ai-native-developer-experience/skills/plugin-submission plugin-submission && zip -r plugin-submission.zip plugin-submission # claude.ai → Customize → Skills → + → Create skill → Upload a skill → plugin-submission.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablejpantsjoha/ai-native-developer-experience/skills/plugin-submission is public and reachablegithub.com/jpantsjoha/ai-native-developer-experience/tree/HE ↗Pass
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-09github.com/jpantsjoha/ai-native-developer-experience/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/jpantsjoha/ai-native-developer-experience/blob/HE ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/jpantsjoha/ai-native-developer-experience/blob/HE ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 69 linesgithub.com/jpantsjoha/ai-native-developer-experience/blob/HE ↗Pass
SKILL.md
View on GitHubPlugin Submission
Treat every public listing as an external representation of the project. Submit only an artifact that the destination's current policy accepts, and retain a receipt for every send.
Workflow
- Classify the destination and artifact. Determine whether it accepts a full
plugin, a repository, or one standalone
SKILL.md. Do not describe a multi-skill plugin as one skill, or split a skill bundle without an explicit portable artifact. - Read the current primary policy. Use the destination's official submission
instructions or
CONTRIBUTING.md; record its URL, access requirements, licence and validation rules, and any limits on automated or AI-assisted submissions. - Validate eligibility. Check the public candidate URL, release/tag, licence as
detected by the hosting platform, manifest/schema validity, documentation, and the
destination-specific validator. Treat a mismatch or unmet requirement as
blocked, not as an invitation to bypass it. - Prepare one destination matrix. For each target, record: destination, artifact,
policy evidence, status (
ready,blocked,deferred, orhuman-only), exact payload, and rollback action. Reuse the canonical repository description; minimise personal data and never add an email without explicit permission. - Stage, then confirm. Fill or draft public data only after the operator has approved the destination. Immediately before clicking a submit control, opening a PR, or sending a recommendation, restate the exact target and payload and obtain a final human confirmation. A single confirmation may cover multiple named sends only when the full set and payloads are shown together.
- Send through the permitted route. Use a form, PR, issue, or API only when the policy permits that route. Never act where a policy requires a human-authored recommendation, prohibits AI-assisted submissions, or requires credentials/access the operator has not supplied.
- Verify and record the receipt. Capture the submission URL/identifier and status. If a listing is rejected or stale, record the reason and next eligible action. Roll back a repository contribution by closing its PR/issue when appropriate; external directory records require the destination's own removal/update path.
Submission Gate
Do not send until all applicable checks pass:
- The target policy is current and supports the proposed artifact.
- The public repository and exact release are accessible.
- Project licence intent and platform-detected licence agree.
- Required validation has passed, including the destination's validator where available.
- The project has not overstated supported platforms, usage, security review, or affiliation.
- The operator has given final confirmation for the exact outgoing entries.
Outputs
- A destination matrix with evidence URLs and eligibility verdicts.
- A staged payload for every ready target.
- Submission receipts, or an explicit blocked/deferred reason and owner.
Anti-rationalisation
| Temptation | Gate |
|---|---|
| “It is close enough to call the bundle one skill.” | Submit the artifact type the directory actually accepts, or create a deliberate portable export first. |
| “The README says Apache, so platform metadata does not matter.” | Directories evaluate the public repository; resolve detected-licence mismatches before broad listing. |
| “The user asked to submit, so the final click is implied.” | A final confirmation binds authority to the exact external payload. |
| “A PR is harmless discovery.” | A public PR is a durable representation of the project and must follow the contributor policy. |
| “We can automate a human-only form.” | Human-only and no-AI policies are hard stops. |
Files in this skill
2plugin-submission skill questions
How do I install the plugin-submission skill in Claude Code?
Run npx degit jpantsjoha/ai-native-developer-experience/skills/plugin-submission ~/.claude/skills/plugin-submission. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the plugin-submission skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
Can I automate submissions to platforms that require human-authored recommendations?
No, human-only and no-AI policies are considered hard stops and must not be bypassed.
What should I do if the platform's detected license does not match the project's license?
You must resolve any detected-licence mismatches before proceeding with a broad listing.
When is human confirmation required during the submission process?
A final human confirmation is required immediately before clicking a submit control, opening a PR, or sending a recommendation.