> For the complete documentation index, see [llms.txt](https://developer.eagle.cool/plugin-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.eagle.cool/plugin-api/plugin-review/criteria/functionality-and-policy.md).

# Functionality and Policy Compliance

Only plugins that pass the initial scan proceed to human review. Reviewers select tests appropriate to the plugin's type, stated functionality, and risk to confirm that the installed experience matches the store listing.

Not every plugin receives an identical test script. A simple plugin may require only verification of its core flow, while a plugin that modifies large amounts of data, connects to external services, or performs system operations requires deeper contextual review.

## AI-Assisted Development and Developer Responsibility

Developers may use AI tools, but remain responsible for all submitted code, dependencies, and actual behavior. Before submitting, a developer must:

* read and understand AI-generated or AI-modified code instead of checking only that the interface appears to run;
* inspect third-party dependencies, external connections, data transfers, file operations, and system commands;
* remove unrelated, duplicate, unexplained, or unverified code;
* ensure the store listing describes only functionality implemented in the current release;
* install and test the final `.eagleplugin`, not only the project in its development environment;
* be able to explain important behavior, risks, and required permissions.

If the developer cannot explain the core implementation or confirm how user data and files are handled, reviewers may be unable to determine that the plugin is safe to publish. Submissions clearly assembled from AI-generated code without basic inspection or real testing may not pass review.

## Installation and Launch

Review may confirm that:

* the `.eagleplugin` installs correctly;
* the plugin launches from its expected entry point and responds within a reasonable time;
* the release does not depend on the original project, temporary services, or undisclosed settings on the developer's computer;
* unsupported platforms or environments receive a clear message instead of failing silently or damaging data.

## Main Functionality

Core functionality claimed in the store listing must work in the current release. Review may examine:

* selections, input, and settings required to start the core flow;
* every major capability explicitly claimed;
* generated files, data, or visual results;
* whether original Eagle data is preserved, modified, or deleted;
* connectivity, authentication, and results when an external service is required.

An incomplete core flow, placeholder interface, material mismatch with the description, or functionality that cannot be reproduced will block the submission.

## Cancellation, Invalid Input, and Errors

The plugin should handle cancellation, missing selections, invalid input, unavailable services, and insufficient permissions reasonably. Not every edge case needs an elaborate interface, but the plugin must not become unresponsive, damage data, or falsely report success.

Bulk or irreversible changes should be clearly explained and confirmed before execution. Preview, cancellation, or recovery should be provided when practical.

## Effects on Eagle Data and Local Files

Changes to items, tags, folders, local files, or system settings must:

* match the plugin's stated purpose;
* remain limited to what the functionality requires;
* make important effects clear before execution;
* avoid silently modifying unrelated data;
* avoid undisclosed, unrecoverable data loss.

If the plugin creates files, overwrites originals, deletes data, or makes bulk changes, the introduction and interface must describe the behavior consistently and clearly.

## Uninstallation and Cleanup

When applicable, review may check behavior after the plugin is disabled or uninstalled. The plugin must not leave undisclosed background processes running or delete user-created files or Eagle data during uninstallation. If it creates caches, helper programs, or system settings, explain what is retained and how it can be removed.

## Review Conditions and External Services

When the plugin requires an account, paid plan, API token, third-party application, specific file, or server, the developer must provide conditions that allow the core workflow to be reviewed. External services must be available during review.

A clearly disclosed platform, format, or payment limitation is not automatically disqualifying, but reviewers must be able to verify the functionality claimed in the submission.

## Developer Policies

Human review also considers the [Eagle Developer Policies](/plugin-api/plugin-review/developer-policies.md), including content, security, privacy, paid functionality, advertising, user rights, and other applicable requirements.

In particular:

* the plugin and listing must not impersonate Eagle or misrepresent their source;
* functionality, pricing, limitations, and data handling must be accurate;
* the plugin must not harm Eagle or system stability and security;
* payment, subscription, and trial terms must be clear before the user decides;
* content and behavior must comply with applicable law and content policies.

## Common Reasons a Submission Does Not Pass

* The plugin cannot install, launch, or complete functionality promised in the listing.
* The main interface remains a placeholder or claimed functionality is not implemented.
* Cancellation or invalid input causes a crash, unresponsiveness, or data damage.
* User data is deleted, overwritten, or modified in bulk without disclosure.
* Undisclosed background behavior continues after disabling or uninstalling, or user content is deleted.
* Required accounts, tokens, or third-party services are not available for review.
* The developer cannot explain core behavior, external connections, data handling, or file changes.
* The submission contains substantial unexplained, unreviewed, or irrelevant AI-generated code.
* Actual behavior, payment, or data handling conflicts with the store listing.
* The plugin violates security, content, privacy, or user-rights requirements.

Human review does not require every plugin to have the same design or scope. It confirms that the current release safely, reliably, and honestly fulfills the developer's promises to users.