JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 906
  • Score
    100M100P100Q98988F
  • License MIT

CLI tool for managing Claude Code plugins

Package Exports

  • claude-plugins
  • claude-plugins/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (claude-plugins) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Claude Plugins CLI

Manage Claude Code plugins with a simple command-line interface.

Usage

No installation required - use with npx or bunx:

# Install a plugin
npx claude-plugins install @every/compounding-engineering
bunx claude-plugins install @every/compounding-engineering

# List installed plugins
npx claude-plugins list

# Enable/disable plugins
npx claude-plugins enable plugin-name
npx claude-plugins disable plugin-name

Or install globally:

npm install -g claude-plugins

Discover Plugins

Explore available plugins at claude-plugins.dev

Commands

install <plugin-identifier>

Install a plugin from the registry:

# Scoped plugins
npx claude-plugins install @every/compounding-engineering
npx claude-plugins install @wshobson/claude-code-essentials

# Scoped without @ prefix
npx claude-plugins install every/compounding-engineering

# Unscoped plugins
npx claude-plugins install plugin-name

All plugins must be registered in the central registry.

list

View all installed plugins grouped by marketplace:

npx claude-plugins list

Output shows enabled (✓) and disabled (✗) plugins.

enable <plugin-name>

Re-enable a previously disabled plugin:

npx claude-plugins enable plugin-name

disable <plugin-name>

Disable an installed plugin without removing it:

npx claude-plugins disable plugin-name

The plugin files remain intact and can be re-enabled later.

Development

Run tests

bun test

Build

bun run build

Plugin Resolution

The CLI resolves all plugin identifiers via the central registry API (npm-style):

  1. @namespace/plugin → API lookup at https://api.claude-plugins.dev/api/resolve/namespace/plugin
  2. namespace/plugin → API lookup at https://api.claude-plugins.dev/api/resolve/namespace/plugin
  3. plugin → API lookup at https://api.claude-plugins.dev/api/resolve/plugin

All plugins must be registered in the central registry. The API automatically tracks download statistics.

Registry API: https://www.val.town/x/kamalnrf/claude-plugins-registry

Creating Plugins

A valid Claude plugin must have:

your-plugin/
  .claude-plugin/
    marketplace.json (or plugin.json)
  agents/          (optional)
  commands/        (optional)
  mcpServers/      (optional)

Minimum marketplace.json:

{
  "name": "your-plugin",
  "description": "Plugin description",
  "version": "1.0.0",
  "author": {
    "name": "Your Name"
  }
}

Future Enhancements

  • Search command with API integration (API endpoint exists, CLI command not implemented yet)
  • Plugin update/upgrade command
  • Version pinning
  • Plugin signatures/verification