Prepare an Anthropic plugin

Produce a concrete package the owner can verify before any submission. This workflow works independently of the rest of Mobile App Builder. Use the current official requirements and blocker playbook; refresh the linked documentation before every release because schemas and directory rules change.

Inspect and plan

1. Locate the actual plugin root and installed/public identity, version, repository, branch and dirty changes. Preserve the established slug and artwork. Inspect prior validation reports and the exact source commit; do not assume a stale default branch, old ZIP or installed cache represents the candidate.
2. Inventory skills, agents, scripts, hooks, connectors and all outbound behavior. Record what runs automatically, what needs a user action, and any provider costs/data access. Do not bundle hosted-service source, signing files or credentials in a skills-only native payload. Removing a required connector changes behavior and needs an explicit product decision.
3. Plan the final native payload and a small owner review pack. Use the reusable review template. Keep unknown publisher facts, compliance-contact verification and legal attestations pending for the owner; never invent them.

Create the listing and branding

4. Set the real stable name, explicit version, display name, supported description, publisher, license and repository in the native manifest. Add the icon and HTTPS documentation, support, privacy and terms links to the plugin manifest only. The marketplace schema has a different field set. Preserve other hosts' original identities and use their separate native packages.
5. Reuse suitable original art. If art is missing or explicitly being replaced, use the host's image-generation capability to create an actual distinctive icon, then inspect it on light and dark backgrounds at small size. Do not copy provider logos or imply affiliation. If generation is unavailable, finish metadata and a concrete art brief, and report the asset as pending. A prompt is not an icon.
6. Prepare a brand guide with original symbol/wordmark usage, palette, typography, legibility, clear space and exports. A square PNG at least 256 pixels and below 5 MiB is this workflow's recommended listing export, not a claimed universal Anthropic dimension requirement. Use the selected artwork as both icon and logo where appropriate; do not add unsupported logo keys to Claude's manifest. Show actual art in the README using Markdown image syntax, with contained paths.
7. Open every actual public URL without private authentication and inspect the promised content. A 200 response, guessed endpoint or unpublished local policy is insufficient. Record date, redirect and content agreement with the candidate. Draft corrected pages locally if needed and retain their publication as a separate gate. Do not create a website or contact channel that the owner did not authorize.

Check the exact native package