How we check listings
Before a listing goes live, we install it with the real Grok Build CLI and confirm Grok loads its skills, commands, and MCP tools. We don't run every plugin in a live session, and some need your own sign-in or API key to fully work. We recheck when a plugin updates. If a check fails, the listing comes down until it passes.
What the check does
- We install the listing in a throwaway home folder with the Grok Build CLI (grok 1.0.62), using the same command shown on its page:
grok plugin install,grok plugin marketplace add, orgrok mcp add. - We ask Grok what it discovered (
grok inspect): skills, slash commands, subagents, hooks, MCP and language servers. For connectors added withgrok mcp add,grok mcp doctorconfirms the server starts and answers. - A listing passes when it installs and Grok loads something usable from it. If nothing loads, or the install fails, it isn't listed.
What the check doesn't do
- We don't sign in to anyone's service, and we don't run every plugin in a live Grok session. Listings marked Needs sign-in or Needs API key need your own account to do anything useful.
- We don't review a plugin's code. Installing with
--trustlets a plugin's hooks and MCP servers run code on your computer, so read community plugins before you trust them.
The badge
Listings that passed show ✓ Install-checked in Grok Buildchecked on the date of their last check next to the install command.