Store Listing Copy

Requirements for plugin names, descriptions, introductions, changelogs, locales, and material disclosures.

The store listing must help users understand the plugin's purpose, main workflow, and important conditions before installation. Every submitted locale is reviewed separately, and listing claims are checked against the actual plugin.

A strong locale cannot compensate for a blocking issue in another required locale. Each submitted locale must be complete and independently understandable.

Name

The plugin name must be readable, recognizable, and reasonably related to the plugin's identity, purpose, output, or concept.

• Maximum 30 Unicode code points.

• When the language uses whitespace-delimited words, the name must also contain no more than 6 words.

• Brand names, creative names, and functional names are allowed; names are not required to be nouns.

• Descriptive use of Eagle is allowed when it does not imply that Eagle created, owns, or endorses the plugin.

• Misleading, unreadable, unrelated, impersonating, or keyword-stuffed names are not allowed.

English title case is recommended but not required. Lowercase styling, decorative punctuation, or general promotional wording does not independently cause rejection while the name remains readable and honest.

Short Description

The description should directly communicate the core function and user value, adding useful information beyond the name.

• English: maximum 200 Unicode code points.

• Simplified Chinese: maximum 100 Unicode code points.

• Two sentences or fewer is recommended, but sentence count alone is not a rejection rule.

• Avoid slogans, repetition of the name, and unrelated keywords.

• Do not claim functionality the plugin does not implement.

General promotional language such as “fast,” “best,” or “boost productivity” does not independently block a submission. Specific numbers, rankings, market leadership, named comparisons, pricing, privacy claims, supported formats, and compatibility claims require a reasonable factual basis.

Introduction

The introduction must tell users what they are installing and how to complete the main workflow. It should cover:

• the plugin's purpose and implemented core functionality;

• essential steps required to begin using it;

• important inputs, outputs, and whether original data is modified;

• conditions that materially affect installation, access, payment, data handling, or core use.

The following must be disclosed when applicable:

• required third-party sign-in, API keys, paid plans, or companion software;

• required network access or external services;

• transmission of user data, selected files, or file contents to an external service;

• deletion, overwriting, or other destructive or irreversible behavior;

• platform, Eagle-version, or format limitations that determine whether core functionality works;

• any essential step without which the main workflow cannot be completed.

Optional settings, minor limitations, small workflow details, interface-language notes, and speculative future compatibility are normally recommendations. An omission blocks a submission only when it materially misleads users or prevents core use.

Changelog

When the submission form provides or requires a changelog, describe the actual release in user-facing language.

• An initial release may use Initial release. or its natural localized equivalent.

• Updates should describe meaningful features, fixes, or improvements.

• Do not use entries such as Update, Fix, Changes, or Initial Commit by themselves.

• Keep release history separate from the introduction.

Locale and Language Quality

Every submitted locale must be complete and understandable. A listing appears unfinished when it contains:

• placeholder, test, or draft text;

• partially translated fields or paragraphs;

• mixed languages that make the content unreadable;

• errors dense enough to obscure meaning;

• unedited machine translation that materially changes or hides the intended meaning.

Individual spelling, punctuation, grammar, capitalization, or minor formatting issues are normally non-blocking when meaning remains clear.

Content and Links

Listing content must not include hate, harassment, discrimination, explicit sexual content, fraud, encouragement of illegal activity, or baseless attacks on other products.

Links directly related to documentation, support, pricing, privacy, developer information, and required account registration are allowed. Unrelated advertising, spam, excessive affiliate links, misleading downloads, and shortened or obfuscated links that hide their destination may block a submission.

Common Reasons a Submission Does Not Pass

• The name or description exceeds a hard length limit.

• The introduction does not explain the plugin's purpose, workflow, or actual functionality.

• The listing claims functionality not implemented in the current release.

• Required sign-in, payment, external data transfer, or destructive behavior is not disclosed.

• A required locale contains draft text, placeholders, or unusable translation.

• A changelog exists but communicates no actual release information.

Base corrections on behavior that can be verified in the current release. Do not add unsupported functionality or guarantees merely to make the listing more persuasive.