Galaxio Performance Kit

Galaxio engineering workflows packaged as portable agent plugins for Cursor, Claude Code and Codex.

One plugin is authored once. The three agents disagree about manifests, not about skills, so this repository keeps a single skills/ tree per plugin and generates the Cursor, Claude Code and Codex manifests from one source file.

Plugins

Plugin	What it does
galaxio-gatling-pro	Gatling JVM performance testing in Galaxio style — Gatling 3.9.x through 3.15.x, Scala/Java/Kotlin on sbt, Maven or Gradle, Picatinny, HTTP/JDBC/JMS/Kafka/AMQP

Install

Claude Code:

claude plugin marketplace add galax-io/ai-plugins

Codex:

codex plugin marketplace add galax-io/ai-plugins

Cursor has no CLI for third-party marketplaces. Either import this repository as a team marketplace — Dashboard → Plugins → Add Marketplace → Import from Repo — and install from the UI, or copy a plugin directory into ~/.cursor/plugins/local and run Developer: Reload Window.

Then install a plugin by name, for example galaxio-gatling-pro@galaxio-performance-kit.

Update

Installing pins the version. Re-running install does not move an existing install — it reports the plugin as already installed and keeps serving the cached build, however many releases have shipped since. Update it explicitly:

claude plugin marketplace update galaxio-performance-kit

claude plugin update galaxio-gatling-pro@galaxio-performance-kit

The first refreshes the catalog, the second replaces the installed copy. It prints Restart to apply changes — until you restart, the session keeps serving the old skill.

Codex has no plugin update: run codex plugin marketplace upgrade galaxio-performance-kit to refresh the snapshot, then codex plugin remove and codex plugin add the plugin. Cursor updates a team install from the Plugins UI; a local install is the directory you copied into ~/.cursor/plugins/local, so re-copy it and run Developer: Reload Window.

Repository layout

marketplace.meta.json              authored: marketplace identity
plugins/<name>/plugin.meta.json    authored: everything about one plugin
plugins/<name>/skills/<skill>/SKILL.md
schemas/                           JSON Schema for both authored sources
scripts/                           generator and checks
tests/                             the suite and its fixtures — not shipped content
.claude-plugin/marketplace.json    generated
.cursor-plugin/marketplace.json    generated
.agents/plugins/marketplace.json   generated
plugins/<name>/.claude-plugin/plugin.json   generated
plugins/<name>/.cursor-plugin/plugin.json   generated
plugins/<name>/.codex-plugin/plugin.json    generated

Generated files are never edited by hand. npm run check fails when they drift from the authored sources.

Commands

npm run sync

npm run check

npm test

sync regenerates the manifests. check runs the same generator in verify mode plus the portability, link and security checks. test exercises the scripts against the fixtures in tests/fixtures/. All three run on Node built-ins alone.

The plugins under tests/fixtures/ are deliberately broken inputs for the suite, not marketplace content. Nothing there is published, and the checks skip it.

CI also requires the prose gates, so run them before opening a PR. They need npm install first:

npm run format:check && npm run lint:md && npm run spell

Adding a plugin

See CONTRIBUTING.md. The short version: create plugins/<name>/plugin.meta.json, write skills under plugins/<name>/skills/, run npm run sync, run npm run check, and install the result in at least one agent before opening a PR.

Background on the primitives and the three manifest dialects: docs/plugins-vs-skills.md.

License

Apache-2.0. See LICENSE.