A Claude Code plugin marketplace aggregating ether-moon's plugin collection. Each plugin lives in its own repository; this marketplace is a thin index that lets you discover and install all of them from a single entry point.
claude plugin marketplace add ether-moon/ether-plugins| Plugin | Description | Source |
|---|---|---|
skill-set |
Comprehensive productivity skills and development tools for Claude Code — git workflow automation, code context understanding, peer LLM consulting, PR review feedback. | ether-moon/skill-set |
agent-atelier |
Autonomous product development loop — AI agent team that cycles through spec, implement, validate, and self-correct. | ether-moon/agent-atelier |
knowledge-distillery |
A knowledge distillation system that delivers only verified knowledge to AI coding agents. 3-layer architecture with convention-based air gap. | ether-moon/knowledge-distillery |
hotwire-frontend-skills |
7 skills (1 gateway + 6 specialists) for building Rails frontend with Hotwire — Turbo Drive, Turbo Frames, Turbo Streams, Stimulus, view transitions, forms, media, and native bridge. | ether-moon/hotwire-frontend-skills |
herb-lsp-plugin |
Plugin to support herb-lsp in Claude Code. | ether-moon/herb-lsp-plugin |
backlog-md-workflow |
Backlog.md task management workflow — setup, operating conventions, and guided task authoring. | ether-moon/backlog-md-workflow |
claude plugin install skill-set@ether-plugins
claude plugin install agent-atelier@ether-plugins
claude plugin install knowledge-distillery@ether-plugins
claude plugin install hotwire-frontend-skills@ether-plugins
claude plugin install herb-lsp-plugin@ether-plugins
claude plugin install backlog-md-workflow@ether-pluginsIf you only want the skills (not the full plugin payload of commands/agents/hooks), or you want to use them with non-Claude-Code agents like Cursor or Codex, use vercel-labs/skills. Each source repo's .claude-plugin/marketplace.json is auto-discovered, so the CLI finds nested skills under plugins/<name>/skills/ without extra configuration.
Preview available skills before installing:
npx skills add ether-moon/skill-set --listInstall every skill from a repo:
npx skills add ether-moon/skill-set --skill '*'Install a specific skill:
npx skills add ether-moon/skill-set --skill bumping-versionInstall globally instead of into the current project:
npx skills add -g ether-moon/skill-set --skill managing-git-workflowSwap ether-moon/skill-set for any of the source repos listed in the Plugins table: knowledge-distillery, hotwire-frontend-skills, herb-lsp-plugin, backlog-md-workflow. (agent-atelier is Claude Code-specific and isn't designed to run under npx skills; install it via claude plugin install instead.)
Install every skill from every agent-portable repo in one shot:
plugins=(
skill-set
knowledge-distillery
hotwire-frontend-skills
herb-lsp-plugin
backlog-md-workflow
)
for r in "${plugins[@]}"; do
npx skills add ether-moon/$r --skill '*' -y
doneAdd -g to install globally, and drop -y if you want to confirm each repo interactively.
Each entry in .claude-plugin/marketplace.json uses the git-subdir source type to reference the plugin directory inside its source repository, tracking the main branch:
{
"source": {
"source": "git-subdir",
"url": "https://github.com/ether-moon/<plugin>.git",
"path": "plugins/<plugin>",
"ref": "main"
}
}This means:
- Plugin code stays in its own repository. No duplication, full git history preserved per plugin.
- Each plugin releases on its own schedule. Updates to a plugin's
mainbranch are picked up automatically byclaude plugin marketplace update. - The hub repo stays tiny. It only contains
marketplace.jsonand this README; no plugin code lives here.
Each plugin's source repository registers this hub in its own .claude/settings.json for in-repo development:
{
"extraKnownMarketplaces": {
"ether-plugins": {
"source": { "source": "github", "repo": "ether-moon/ether-plugins" }
}
},
"enabledPlugins": {
"<plugin-name>@ether-plugins": true,
"skill-set@ether-plugins": true
}
}A developer opening any plugin repo with Claude Code gets the plugin itself plus the shared skill-set tooling (e.g., bumping-version). A brand-new plugin must be added to this hub's marketplace.json before in-repo dogfooding can resolve.
Issues and pull requests for individual plugins should go to the plugin's source repository (linked in the table above), not this marketplace repo.
This repo accepts:
- Marketplace metadata fixes (descriptions, ordering)
- New plugin additions
- Documentation improvements
Each plugin's source repository also ships its own marketplace.json for direct, single-plugin installation. Existing users who installed a plugin via its source repo's marketplace remain unaffected. New users are encouraged to use this hub for unified discovery.