A plugin package must include a valid manifest and every resource that its capabilities reference.
Use
Keep each skill's SKILL.md and resources together. If the plugin includes MCP services, declare their configuration in
Explain runtime dependencies, account requirements, service permissions, and supported clients and versions based on actual testing. Obtain personal credentials through configuration or authorization; do not include passwords, API Keys, or tokens in the package.
Update the version for each submission and keep it consistent across the manifest, package, instructions, and self-test report. Include the resources needed to run the plugin; exclude unrelated files and local credentials. Follow the upload page's current size limits.
Create a plugin · Debug and package · Publish a plugin
Manifest and structure
Use .qoder-plugin/plugin.json for the plugin manifest. Keep the plugin name and version identifiable and use the configuration format supported by the target client. Do not add an unnecessary outer folder when creating the ZIP.
Skills and services
Keep each skill's SKILL.md and resources together. If the plugin includes MCP services, declare their configuration in mcp.json and reference it from the manifest as required by the supported format. Verify every service separately.