alexmskills

A curated Claude Code plugin marketplace of reusable, self-improving
skills and agents. Each skill is packaged as an independently versioned plugin, so you install and
update exactly what you need.

The emphasis is on self-learning tooling — skills that get better at your repo over time:
a CLAUDE.md that prunes and graduates its own decisions, a delivery crew that re-tiers its roles from
run history, a brainstorm panel that learns which experts your work needs, and a learn-on-failure hook
that captures every multi-cycle debugging detour.

📖 Documentation: https://www.alexmond.org/alexmskills/

Catalog

The Role System

Four of the plugins form one system: a shared substrate of evolving roles (.claude/roles/) and
three orchestrators that compose those roles task-fit and learn over time. One persona — say a
skeptic or an architect — behaves the same whether it's run solo, seated in a crew, on a panel, or in
a sweep, accumulating what it learns along the way.

The three orchestrators chain — research discovers the facts, the panel decides what to do, the
crew delivers it — and they share roles (one skeptic is a panel seat, a crew adversarial check,
and a research verifier). Each is fully usable on its own; co-installed, they share one evolving talent
pool. Full model: the
Role System architecture.

Install

Add the marketplace once:

/plugin marketplace add alexmond/alexmskills

Then install what you want — copy-paste 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 review-agents@alexmskills
/plugin install research-sweep@alexmskills

Or browse interactively with /plugin (Discover tab). After a maintainer pushes an update, refresh
with /plugin marketplace update alexmskills.

Try a plugin without installing

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

Quick start

• evolving-claude-md — open a repo and say "make CLAUDE.md evolve". The plugin ships its own
  hooks (audit on session start, lint on every CLAUDE.md edit, re-audit after compaction) — they
  register automatically once the plugin is enabled.
• dev-crew — "run the crew on this feature". It composes a roster for the task; review it,
  then it relays the roles, stopping at hard gates (QA fail, deploy). architect → dev → qa → deployer
  is the typical code lineup — a data change or a doc gets a different one.
• brainstorm-panel — "get a team on this and make it better". It proposes a panel + a
  coordination style for your sign-off, then runs the loop.
• learn-on-failure — install it and forget it; it captures a learning whenever a task needed
  more than one attempt.

Beta plugins

In-progress / unproven plugins live in the same marketplace as stable ones, distinguished by a
-beta suffix in the name (e.g. tune-repo-beta). No separate channel, no
extra marketplace to opt into — you install them the same way as any other plugin:

/plugin install tune-repo-beta@alexmskills
/plugin install systemic-fix-beta@alexmskills

The suffix is intentional: it makes it obvious at install time and in the enabled-plugins list
that this is a beta plugin. When one earns its stable slot, it graduates — the directory is
renamed, the -beta drops from the name and marketplace entry, and the version bumps:

make graduate PLUGIN=tune-repo-beta       # renames -> tune-repo, updates marketplace
make bump     PLUGIN=tune-repo VERSION=1.0.0

prompt-coach graduated this way from prompt-coach-beta to 1.0.0 on 2026-07-28.

Versioning

Claude Code versions per plugin, not per skill. Each plugin carries a semantic version in its
plugin.json and a matching entry in marketplace.json:

• Bump a version to ship an update — users on a pinned version only receive it when the number
  changes (commits alone don't trigger an update).
• Tightly-coupled skills (e.g. maven-quality's codestyle/precommit/jacoco) share one plugin and
  version together; everything else is its own plugin so it can move independently.

make bump PLUGIN=dev-crew VERSION=1.1.0   # updates plugin.json + marketplace.json together

Record every version bump in CHANGELOG.md.

Maintenance

CI (.github/workflows/validate.yml) validates the marketplace on every push and PR.

Documentation

Full docs are published at alexmond.org/alexmskills
(Antora component under docs/, aggregated by the
alexmond.github.io site build).

Contributing

1. Add a plugin under plugins/<name>/ with a .claude-plugin/plugin.json and a skills/ and/or
   agents/ directory.
2. Register it in .claude-plugin/marketplace.json (under plugins).
3. Run make validate — it must pass.
4. Add a doc page under docs/modules/ROOT/pages/ and link it in nav.adoc.

Provenance & attribution

All plugins in this marketplace are original work by Alex Mondshain, MIT-licensed — authorship is
recorded in each plugin's plugin.json (author) and the repo LICENSE. One third-party
inspiration is credited: the roles plugin's persona set was seeded by a public prompt thread from
@nahidulislam404 on X — the wording here is generalized and rewritten,
but that thread sparked the original set.

License

MIT © Alex Mondshain