How to install from the catalog, how each artifact is checked before it is listed, and what publishing into it actually costs you.
How do I install AI tools across different editors and AI clients?
- Run the metahub installer once, then install anything with a single command: mh install <slug>. The installer also connects the metahub MCP server to every editor it detects, so you can skip the terminal entirely and ask your assistant in plain language instead. The same artifacts work across Claude Code, Cursor, Claude Desktop, VS Code, Zed, Windsurf, Continue, Cline, Goose, Codex CLI, and Antigravity, so you do not need a different install path per editor.
How does metahub check that a tool is safe and works correctly?
- Every artifact runs through Assay, our open-source evaluation framework, before it is listed. Assay executes the tool against behavioral scenarios in a sandbox and scores it on correctness, instruction adherence, safety, and latency, alongside static checks on the repository such as license and documentation. Results are public on each listing, including the checks that failed, so you can judge a tool on evidence rather than on its README.
Where can I find AI skills and plugins that have already been evaluated?
- Browse or search the registry at registry.metahub.ai. Every artifact in the catalog has been evaluated before listing, and each listing links its full public report. You can filter by kind (skill, MCP server, agent, plugin), by category, and by whether the publisher is a verified owner.
Can I publish my own AI skill or agent, and what do I get?
- Yes, and it is free. Sign in with GitHub at developer.metahub.ai, point metahub at a public repository, and it detects the artifacts inside, evaluates them, and publishes them. In return you get a public evaluation report, a listing people can install in one command, and a live dashboard of real usage. Publishing does not transfer any rights: your code stays in your repository under your license.
How is the metahub registry different from a marketplace or an awesome list?
- A directory tells you a tool exists. This catalog tells you whether it works: every artifact is evaluated before listing, pinned to the exact commit that was evaluated, and installable in one command across every supported editor. Listings carry public evidence rather than stars alone, including the checks an artifact failed, and nothing reaches the catalog on a README alone.
Does metahub check for prompt injection or destructive behaviour?
- The evaluation includes a safety dimension: artifacts are exercised against adversarial scenarios and scored on how they respond, and unsafe behaviour lowers the score and is flagged on the public report. It is a meaningful signal, not a security guarantee. Because installs are commit-pinned and the source repository is linked from every listing, you can always read exactly what you are about to run.
What does commit-pinned mean, and why does it matter?
- Every artifact is published at a specific commit SHA, and that is the exact revision you install. It matters because it makes an install reproducible and honest: you get the same code that was evaluated, not whatever the default branch happens to contain today. When a publisher ships a new version, it is evaluated again and the listing moves forward deliberately.
How do I update or uninstall something I installed?
- Run mh update <kind>/<slug> to move a single install to that artifact's latest published commit, or mh update --all to bring every install forward at once. mh outdated lists the installs with a newer version waiting, so you can see what would change before changing it. Removing one is mh uninstall <kind>/<slug>, which also unwires the client configuration the install added rather than leaving it behind, and mh list shows everything you currently have installed.