Repository navigation
Add the OpenClaw plugin manifest so the bundle can publish to ClawHub - #8
Merged
Merged
Conversation
ClawHub's package publish requires openclaw.plugin.json in the plugin root, even for a bundle plugin whose Claude and Cursor manifests already describe it. Ignore reports/ because clawhub package validate writes its output there.
andreaszig
approved these changes
Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ClawHub's
package publishrefuses a bundle plugin withoutopenclaw.plugin.jsonin the plugin root, even though OpenClaw's own runtime reads our.claude-plugin/plugin.jsonand needs nothing new. Verified against the CLI: without this file the publish stops atError: openclaw.plugin.json required, and with itclawhub package validatereports Plugin Inspector PASS, 0 breakages.The fields match what a comparable hosted-MCP bundle already on ClawHub ships (
@railyai/raily).categoriesandiconare ClawHub catalog fields, documented on their publishing page; the inspector flags both as unknown at P2 because it validates OpenClaw's runtime schema rather than the registry's, and a warning does not block publication. Declaringfinance-paymentsbeats letting their classifier guess, which is what omitting the field does.reports/is ignored becauseclawhub package validatewrites its output into the plugin directory. A dry run before this caught those three files being packaged as plugin content, 42 KB of the 62 KB payload.