convez.ai
SkillAutomaçãoAvançado
alexmond

alexmskills – Marketplace de Skills Autoaprendentes para Claude

alexmond/alexmskills

Plugins autoaprendentes e orquestrados que evoluem com seu código

Ver no GitHub
InicialPluginScore · de 0 a 100

Um marketplace curado de plugins reutilizáveis e autoaprendentes para Claude Code, cada um com versionamento independente. Oferece skills que evoluem com seu repositório ao longo do tempo, como painéis de brainstorm, crews de entrega orquestrados, auditorias de segurança e logs de decisão vivos.

Instalação

$npx convez-ai alexmond/alexmskills

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
10
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 2 semanas
Versão
—
Issues abertas
3
Contribuidores
1

Casos de uso

  • Automatizar workflows de desenvolvimento com crews especializados (arquiteto → dev → QA → deployer)
  • Manter registros vivos de decisões e aprendizados que se auto-refinam via CLAUDE.md
  • Auditar segurança OWASP e qualidade Maven/Java em CI/CD
  • Executar pesquisa distribuída com painéis de especialistas que aprendem suas necessidades

Veredito

Ecosystem robusto e bem arquitetado para quem quer orquestração inteligente e autoaprendizagem em workflows de código. Exige compreensão profunda de agentes Claude e estrutura de repos, mas entrega valor real em escala.

README

A tradução para o português deste README ainda está na fila.

alexmskills

Validate Marketplace License: MIT Docs

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.

Catalog

PluginCategoryVersionWhat it does
evolving-claude-mdself-learning1.0.0Turns CLAUDE.md into a living Decisions & Learnings log that prunes, graduates, and archives itself via three hooks.
dev-crewself-learning1.1.0A self-evolving delivery crew that composes a task-fit roster (like a panel, but to ship a target) and runs it as a gated relay with machine-enforced phase gates + an escalation ladder; each role a subagent on its own tier. (architect → dev → qa → deployer is one example lineup.)
brainstorm-panelself-learning1.1.0Assembles a task-fit panel of role-specialized agents (skeptic always seated), picks a coordination style, and runs a generate-critique-refine loop with an evolving seat registry.
learn-on-failureself-learning1.0.0Auto-saves a durable learning to project memory whenever a task takes more than one fix cycle.
rolesself-learning1.0.0A per-repo repository of evolving roles (.claude/roles/) usable solo via /roles:as, as dev-crew roles, brainstorm-panel seats, and research-sweep coverage roles; ships seed personas + a graduation-audit hook.
implement-issueworkflow1.0.0Drives a GitHub issue from branch → implement → verify → PR with a guided workflow.
maven-qualityworkflow1.0.0Format, static-analysis, coverage, and pre-commit skills for Maven/Java projects (codestyle, precommit, jacoco).
security-auditworkflow1.0.0Scans a codebase for OWASP-style vulnerabilities (injection, path traversal, unsafe reflection/deserialization, secrets).
review-agentsreview1.0.0Read-only specialist subagents for code review, test running, and dependency/CVE auditing on lighter model tiers.
research-sweepresearch1.0.0Fans out independent research agents across distinct angles, then synthesizes and adversarially verifies.

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.

PluginRole in the systemVerb
rolesthe shared substrate — evolving roles + solo invocation (/roles:as <role>)—
dev-crewcomposes a roster and runs it as a gated delivery relaydeliver
brainstorm-panelconvenes a multi-perspective panel that critiques and convergesdecide
research-sweepfans out parallel coverage roles then synthesizes + adversarially verifiesdiscover

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 dev-crew@alexmskills
/plugin install brainstorm-panel@alexmskills
/plugin install learn-on-failure@alexmskills
/plugin install roles@alexmskills
/plugin install implement-issue@alexmskills
/plugin install maven-quality@alexmskills
/plugin install security-audit@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.

Channels

Two marketplace channels ship from this one repo:

  • stable — alexmskills (.claude-plugin/marketplace.json): released, versioned plugins.
  • beta — alexmskills-beta (beta/): unreleased / in-progress plugins. Opt in with a git-subdir source (see beta/README.md), then /plugin install <name>@alexmskills-beta.
make new-beta NAME=my-skill     # scaffold an unreleased plugin in the beta channel
make promote PLUGIN=my-skill    # move it into the stable catalog when it's ready

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

CommandPurpose
make validateValidate both channels + every plugin manifest (jq-based, no extra deps). Runs in CI.
make listPrint the catalog (name, version, description).
make bump PLUGIN=<name> VERSION=<x.y.z>Bump a plugin's version in both manifests.
make new-beta NAME=<name>Scaffold a new plugin in the beta channel.
make promote PLUGIN=<name>Move a beta plugin into the stable catalog.
claude plugin tag --dry-run plugins/<name>Validate a plugin's plugin.json agrees with its marketplace entry.
claude plugin tag --push plugins/<name>Cut a <name>--v<version> release tag.

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

Ver o original no GitHub

Bom para

Relacionados