When the code finally ran without errors, the real work began. Part 1 of this series covered getting from a blank repository to a working plugin; publishing that plugin to the Anthropic marketplace turned out to be a different problem entirely -- a lot like moving a prototype from a sandbox into a public gallery. The sandbox lets you iterate quickly, but the gallery has a checklist, a review process, and a set of expectations that most developers only discover after their first successful build. This second part of the series covers the practical steps that saved weeks of back-and-forth with reviewers -- and how LoreConvo kept my notes, decisions, and dependencies organized throughout the publishing journey.
From Local Testing to Marketplace Submission
The first version of the plugin lived inside a single repository, driven by a handful of unit tests and a local Claude session. That environment is forgiving: you can reload the same session, tweak a prompt, and rerun the same code without worrying about external constraints. The Anthropic marketplace, however, runs the plugin in a clean container, validates the manifest, and checks that every declared dependency can be resolved from PyPI. The first surprise was the strictness of the manifest schema. Fields that seemed optional in the sandbox -- required_python_version, runtime_dependencies -- must be present and accurate. Missing a single dependency caused the automated validator to reject the entire upload, even though the code executed perfectly on my machine.
