Both plugins are distributed through a single marketplace catalog at BabylonJSMarket/claude-plugins. The catalog is just a marketplace.json file that points at the npm packages — there's no separate plugin repo to clone.
One-time setup
Inside any Claude Code session:
This registers the catalog. You only run it once per machine.
Installing the plugins
Each /plugin install fetches the npm package, finds the .claude-plugin/ directory inside it, and loads the skills under the plugin's namespace.
After installing, ask what skills are available in any session. You should see at least ecs-framework:ecs-authoring and arcade-ecs:arcade-scaffold. Skills load by description match, so you don't need to type the namespaced names — describing what you want is enough.
Version pinning
/plugin install resolves the npm package's latest tag by default. To pin a specific version:
The plugin version mirrors the npm package version exactly — bumping the package bumps the plugin in the same step.
Updating
When a new version of either package ships, refresh the catalog and reinstall:
marketplace update re-reads the catalog from GitHub (in case new plugins have been added). /plugin install re-resolves the npm tag and picks up the new version.
Local development
Editing skills inside the bjsm monorepo without publishing first:
--plugin-dir takes precedence over any installed copy with the same name, so you can iterate on SKILL.md files in packages/ecs/skills/ or packages/arcade/skills/ and see the change immediately. Run /reload-plugins inside Claude Code to pick up edits without restarting.
Uninstalling
To drop the marketplace catalog entirely: