Getting Started

Two in-progress plugins ship with a -beta suffix (tune-repo-beta, systemic-fix-beta) — install them the same way; see the README’s beta section for their graduation path.

Two ways to install

There are two installers. Pick one for each plugin, not both.

Way 1: Claude Code plugin Way 2: npx skills

Command

/plugin install <name>@alexmskills

npx skills add alexmond/alexmskills

Works in

Claude Code (and Codex, see Codex)

Claude Code, Cursor, Codex and the other agents the skills CLI supports

What you get

Everything: skills, hooks, agents, slash commands, scripts and mods

The skill folders only

Updates

/plugin marketplace update alexmskills

npx skills update

Use way 1 in Claude Code. It is the only way that installs the whole plugin. Use way 2 for another agent, or when you only want the skill text.

Way 1: Claude Code plugin

Add the marketplace once:

/plugin marketplace add alexmond/alexmskills

Then install what you want. Copy any of these:

/plugin install evolving-claude-md@alexmskills
/plugin install memory-hygiene@alexmskills
/plugin install dev-crew@alexmskills
/plugin install brainstorm-panel@alexmskills
/plugin install learn-on-failure@alexmskills
/plugin install roles@alexmskills
/plugin install prompt-coach@alexmskills
/plugin install screenshot-sweep@alexmskills
/plugin install skill-linter@alexmskills
/plugin install implement-issue@alexmskills
/plugin install maven-quality@alexmskills
/plugin install security-audit@alexmskills
/plugin install mindmap-prompt@alexmskills
/plugin install screenshot-tour@alexmskills
/plugin install progress-channel@alexmskills
/plugin install context-bar@alexmskills
/plugin install usage-bar@alexmskills
/plugin install ticket-triage@alexmskills
/plugin install review-agents@alexmskills
/plugin install research-sweep@alexmskills
/plugin install spring-batch@alexmskills
/plugin install conductor@alexmskills
/plugin install tune-repo-beta@alexmskills
/plugin install systemic-fix-beta@alexmskills

Or browse with /plugin (the Discover tab). After a new release, refresh the catalog:

/plugin marketplace update alexmskills

Way 2: npx skills

This needs Node.js. Run it in a terminal, not inside Claude Code.

npx skills add alexmond/alexmskills --list                      # see what is there
npx skills add alexmond/alexmskills --skill brainstorm-panel    # install one skill
npx skills add alexmond/alexmskills --skill codestyle jacoco    # install several
npx skills add alexmond/alexmskills                             # pick from a menu

Useful options:

  • -g installs for your user. Without it the skill goes into the current project.

  • -a claude-code picks the agent and skips the question. -a '*' installs for every agent.

  • -y skips the confirmation prompts.

Later: npx skills list shows what is installed, npx skills update pulls new versions and npx skills remove <skill> removes one.

What this way leaves out

The skills CLI copies each skill’s own folder and nothing else. A plugin’s hooks, agents, slash commands, shared scripts and mods are not copied. So the plugins fall into three groups.

Group Plugins

Works the same. The plugin is only skills.

brainstorm-panel, conductor, implement-issue, maven-quality (skills codestyle, jacoco, pmd, precommit), research-sweep, screenshot-sweep, screenshot-tour, security-audit, spring-batch, systemic-fix-beta (skill systemic-fix), tune-repo-beta (skill tune-repo)

Incomplete. The skill text arrives, but the part that does the work does not. Use way 1.

dev-crew, evolving-claude-md, learn-on-failure, memory-hygiene, mindmap-prompt, progress-channel, prompt-coach, review-agents, roles, skill-linter, ticket-triage

Not available. These are mods and have no skill. Use way 1.

context-bar, usage-bar

Each plugin’s page says which group it is in and what is missing.

The skills CLI names skills, not plugins. The two beta plugins install as tune-repo and systemic-fix, and maven-quality and roles each install as several skills.

Do not install the same plugin both ways. Claude Code would then list its skill twice.

Try a plugin without installing

Load a plugin straight from a checkout — useful for evaluating or developing:

claude --plugin-dir ./plugins/dev-crew

Quick start by plugin

Plugin Say…

evolving-claude-md

"make CLAUDE.md evolve" — its hooks (audit, lint, re-audit) register automatically once enabled.

dev-crew

"run the crew on this feature" — review the roster, then it relays architect → dev → qa → deployer.

brainstorm-panel

"get a team on this and make it better" — it proposes a panel + style for your sign-off, then runs.

learn-on-failure

nothing — install it and it captures a learning whenever a task needs more than one attempt.

Installing from a local directory marketplace is not supported by the Claude Code CLI (it expects a GitHub/git source). To evaluate a local checkout, use claude --plugin-dir as shown above.