convez.ai
SkillIntegração & APIsIntermediário
psalkowski

Maestro Marketplace

psalkowski/maestro-marketplace

Marketplace de skills e agents para Claude Code com setup automático

Ver no GitHub
InicialPluginScore · de 0 a 100

Marketplace de plugins para Claude Code com skills reutilizáveis para documentação agnóstica de provider, grafos de conhecimento, workflows de spec e integração com Conductor. Oferece um setup interativo que configura automaticamente o ambiente do projeto sem necessidade de instalações manuais individuais.

Instalação

$npx convez-ai psalkowski/maestro-marketplace

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
0
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 1 mês
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Configurar documentação centralizada de projetos com suporte a múltiplos providers (Obsidian, Notion, Google Drive)
  • Integrar conhecimento do repositório em grafos para navegação de agentes
  • Executar workflows de especificação e planejamento com hands-off para subagentes
  • Integrar Conductor em workspaces com ações pré-configuradas (code review, criar PR, resolver conflitos)

Veredito

Solução bem arquitetada para orquestração de plugins no ecossistema Claude, focada em abstrair complexidade via setup conversacional. Recomendado para equipes que precisam padronizar documentação e fluxos de trabalho em múltiplos repositórios.

README

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

Maestro Marketplace

Claude Code plugins for provider-agnostic docs, knowledge graphs, spec workflows, and Conductor integration. Install maestro and run /maestro:setup to onboard a project — it sets up the rest for you.

Getting started

/plugin marketplace add psalkowski/maestro-marketplace
/plugin install maestro
/maestro:setup

maestro is the front door — it interviews you in plain terms and installs & configures the rest for you, so you don't need to know the other plugins by name. The list below is what it can set up (you can also install any of them individually).

Available Plugins

PluginDescriptionVersion
maestroStart here. /maestro:setup interviews you (docs location, Conductor, knowledge graph, spec workflow) and installs + configures the right plugins in order0.1.1
docs-hubProvider-agnostic project docs: per-repo Docs Root at .docs/vault (symlink to a durable Backing Store), unified ## docs configuration block, built-in filesystem provider, front-door setup with legacy migration0.1.0
docs-obsidianObsidian driver for the docs-hub contract: vault bootstrap, Backing Store linking into .docs/vault, optional MCP add-on with Local REST API port detection0.1.0
conductor-kitConductor integration: discovery-first GUI/terminal-parity action skills (create-pr, code-review, fix-errors, resolve-conflicts, rename-branch, address-cr), grounded in Conductor's real defaults; personal-layer prompt overrides; workspace setup script with docs/graph seeding0.2.0
graphify-kitBattle-tested graphify (knowledge graph) onboarding for any repo: exclusion analysis, agent navigation protocol, Explore override, session sync hooks, worktree seeding, and a graph-health doctor0.5.0
specProvider-agnostic spec workflow (storage via docs-hub): spec:plan single front door (brainstorm + grill + spec, optional lean plan doc, execution-mode decision); spec:execute runs handed-off plans through pinned subagents0.3.0

Installing a plugin individually

/maestro:setup installs what you need, but you can also install any plugin directly:

/plugin marketplace add psalkowski/maestro-marketplace
/plugin install <plugin-name>

How the plugins relate

docs-hub owns the storage contract (Docs Root, config block, filesystem provider). docs-obsidian is the first provider driver; future drivers (Notion, Google Drive) follow the same shape. spec and graphify-kit are consumers — they read/write docs through the Docs Root without knowing the provider. conductor-kit wires it all into Conductor workspaces (worktree seeding, prompt overrides).

Adding a Plugin

Each plugin lives in plugins/<name>/ with the following structure:

plugins/<name>/
  .claude-plugin/
    plugin.json     # plugin manifest
  skills/           # skill definitions
  agents/           # agent definitions
Ver o original no GitHub

Bom para

Relacionados