Skip to content

Add Grok plugin manifest (.grok-plugin/plugin.json)#138

Draft
justinemach wants to merge 1 commit into
mainfrom
grok-plugin-manifest
Draft

Add Grok plugin manifest (.grok-plugin/plugin.json)#138
justinemach wants to merge 1 commit into
mainfrom
grok-plugin-manifest

Conversation

@justinemach

Copy link
Copy Markdown

What

Adds a root .grok-plugin/plugin.json so browserbase/skills can be listed as the official browse plugin in Grok Build (xai-org/plugin-marketplace).

Why

xAI's marketplace is one central repo. To list a third-party plugin, you add a catalog entry there with a remote url source that clones the plugin repo and reads .grok-plugin/plugin.json from its root, then auto-discovers skills/. This repo had no such manifest, so this adds it (neon-style; no Codex interface block; no MCP — the skills drive the browse CLI).

Pairs with

The companion catalog entry in xai-org/plugin-marketplace (separate cross-org PR) points its url source at this repo pinned to the SHA that includes this commit.

Notes

  • Draft — part of the marketplace batch for @shrey150 to review before we ping Andrew (xAI).

🤖 Generated with Claude Code

xAI's plugin marketplace (xai-org/plugin-marketplace) clones a plugin via a
remote `url` source and reads .grok-plugin/plugin.json from the repo root, then
auto-discovers skills/. This adds that manifest so browserbase/skills can be
listed as the official `browse` plugin in Grok Build. Neon-style manifest (no
Codex `interface` block). No MCP server — the skills drive the `browse` CLI.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@justinemach justinemach requested a review from shrey150 June 17, 2026 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant