Prepare Plugin

Check your plugin, store listing, and review information before submitting.

Before submitting, make sure the final package meets the Review Criteria and understand the complete Review Process. A well-prepared submission can move to human review sooner and reduce repeated revisions.

Using AI-assisted development does not remove the developer's responsibility. You must understand, inspect, and test the code and dependencies in the final release. Do not submit a plugin assembled from AI-generated code if you cannot explain how it works.

Pre-submission Checklist

Plugin and release configuration

• Use Eagle to package the final release. Do not upload a development directory or another archive format.

• Make sure the plugin root contains a valid manifest.json, and disable developer tools in the release build.

• Install the packaged .eagleplugin and verify that it starts and completes its main functionality.

• See Release Configuration and Reviewability for details.

Store listing

• The name, description, introduction, and changelog must describe only features available in the current release.

• Every submitted locale must be complete and clear, including conditions that materially affect installation, payment, data handling, or core use.

• The icon and covers should clearly represent the plugin and remain recognizable at Plugin Center display sizes.

• See Store Listing Copy and Visual Assets for details.

Security and package contents

• Remove secrets, credentials, development settings, version-control directories, caches, and unnecessary build output.

• Review external connections, data transfers, system commands, and file changes. Make sure they are necessary and properly disclosed to users.

• Confirm that the package contains no malicious, unexplained, or unrelated files.

• See Security and Privacy, Package Contents, and File Safety for details.

Information required for review

If the plugin requires sign-in, an API token, payment, special system settings, an external service, or a third-party application, provide reproducible test steps in the submission notes or a README in the plugin root. If an account is required, provide a working review account.

Do not place real user data, private credentials, or secrets in the package. Provide test credentials through the submission page, then disable or rotate them after review.

Developer policies

Your plugin must also comply with the Eagle Developer Policies, including requirements for content, privacy, security, paid functionality, and user rights.

Next Step

After completing the checklist, package the plugin, then follow the steps to publish it.