ai-plugin-marketplace/tools

Monorepo publishing the @ai-plugin-marketplace/* toolkit (consumed by the template repository) — and, dogfooding that toolkit, itself an AI plugin marketplace.

Install the agent plugin

This repo ships one plugin, marketplace-authoring, that equips your coding agent to turn any software repo into an AI plugin marketplace with this toolkit. Install it into your assistant through its native mechanism:

Assistant	Install
Claude Code	/plugin marketplace add ai-plugin-marketplace/tools
Cursor	Dashboard → Settings → Plugins → Import → https://github.com/ai-plugin-marketplace/tools
Codex	codex plugin marketplace add ai-plugin-marketplace/tools
Gemini CLI	gemini extensions install https://github.com/ai-plugin-marketplace/tools
Kiro	Powers panel → "Add power from GitHub" → repo URL

Or, cross-tool via the universal plugins CLI (it installs the native plugin where the tool supports it):

npx plugins add ai-plugin-marketplace/tools

Then ask your agent to "add AI plugin marketplace support to this repo" and the skill walks it through the rest.

Packages

Package	Purpose
@ai-plugin-marketplace/core	Build pipeline, validation, scaffolding. Programmatic API.
@ai-plugin-marketplace/cli	aipm binary. Thin wrapper around core.

Plugin authors depend only on @ai-plugin-marketplace/cli. The consumer flow:

# Generate a new plugins repo from the CLI (one-time)
aipm init my-plugins
cd my-plugins

# Add a plugin
aipm scaffold my-plugin

# Upgrade the toolkit — no plugin source changes required for minor/patch releases
pnpm up @ai-plugin-marketplace/cli

Embedding a marketplace in an existing repo

The flow above creates a dedicated marketplace repo. You can also turn a repo whose primary purpose is shipping software (a CLI, a library) into a marketplace for the agent plugins that drive it, so the software and its skills ship together. Add an optional aipm.repo.ts to relocate the plugins/dist roots off any names your repo already uses:

// aipm.repo.ts (repo root)
import { defineRepoConfig } from '@ai-plugin-marketplace/core';

export default defineRepoConfig({ pluginsRoot: 'agent-plugins', distDir: 'agent-plugins/dist' });

aipm scaffold / build / validate then operate against the relocated root. Full step-by-step: Embedding a marketplace in an existing software repo.

Architecture

The definitive architecture specification lives at docs/specs/architecture.md. Read it before making non-trivial changes to package boundaries, the public API, the per-target module structure, or the versioning contract.

Local development

pnpm install
pnpm run check    # typecheck + lint + knip + syncpack + format + api-report + test (per-package, Nx-cached)
pnpm run build    # tsc + API Extractor rollup

Releasing

Versioned and published with Changesets. The packages are ready for the 0.1.0 release; the only missing piece is npm credentials. See RELEASING.md.

Status

0.1.0 ready to publish (pending npm credentials). See docs/specs/architecture.md for the architecture and §13 for the phased plan.

License

MIT