Point metahub at a GitHub repo. We package your artifact for every AI client your users run (Claude Code, Cursor, Antigravity, and 8 more), and give you a live observability dashboard the day you publish. Free.
install targets
repo → live listing
forever, no card
MIT SDK, own your repo
Without metahub, distributing one skill to 11 AI clients means 11 install scripts, 11 README sections, and 11 bug-report channels. With metahub, it's one repo and one CLI command your users already know.
metahub.json in your repomh install skill/your-slug on any clientEvery install ships with the metahub SDK pre-wired. Invocations, latency, model mix, tool calls, handoffs, and errors stream into your portal in real time. No Datadog setup. No PostHog account. No bill.
+24%
-9%
-0.2pp
+183 this week
“Saved me an entire afternoon parsing slide decks. The trigger fires every time and the output is clean.”· @ada
“Drop-in replacement for what I had bolted together. Just works in Cursor too.”· @rin
Sign in with GitHub, paste your repo URL, and pick a kind: skill, mcp, agent, or plugin.
The portal validates your metahub.json, slug uniqueness, README, and kind-specific files. Fix anything red. Re-run.
Pinned to the exact SHA. Live on the catalog. Dashboard starts filling as the first mh install lands.
Iterate by pushing to your repo and re-publishing; existing installs stay pinned until users run mh update. Full publishing guide ↗
One manifest, every AI tool. We generate the per-client install snippets, so you don't write them.
What users install is exactly what you tested. Re-publishing doesn't break existing installs.
Invocations, p95 latency, models, tools, handoffs, errors. Real-time. No setup. No bill.
Star ratings and written reviews, GitHub-verified for signed-in users, so you can trust the signal.
The portal runs kind-specific checks on every publish and surfaces failures back to you before users see them.
Your repo is your repo. The SDK is MIT (@metahub/core): un-publishing leaves you with a working artifact.
For iteration 1, yes: the portal reads your repo as an unauthenticated GitHub user and pins to a SHA. Private repos (via GitHub App webhook) are on the roadmap.
You do. metahub stores the repo URL and the published SHA, nothing else. Take the listing down and the repo keeps working as a standalone GitHub repo.
Publishing is free. Observability is free. The CLI is free. We'll introduce paid tiers later for things like private bundle storage, sealed CRATE skills, and managed delegate keys; none of that is on the path for shipping a public artifact.
Not yet: iteration 1 is free public artifacts only. Monetization is on the roadmap (signed paid bundles, license keys, revenue share). We'll ask publishers before turning anything on.
Push a fix to your repo and re-publish. The new SHA is what new installs get. Existing installs upgrade when users run mh update. You can also pull the listing entirely if you need to.
No. Anonymous installs work. Signed-in users get personalized installs and the ability to leave reviews, which is the signal you actually want as a publisher.
Five minutes from git push to a live listing with an observability dashboard.