convez.ai
SkillAutomaçãoAvançado
basidiocarp

Lamella – Sistema Portável de Recursos para Ambientes de IA

basidiocarp/lamella

Empacota skills e plugins uma vez, distribui para múltiplas plataformas de IA

Ver no GitHub
InicialPluginScore · de 0 a 100

Lamella é um sistema de empacotamento de skills, hooks e plugins que mantém conteúdo em um único formato e constrói saídas para múltiplas plataformas (Claude Code e Codex). Resolve o problema de drift e duplicação de código-agente entre ambientes ao exportar recursos validados e manifestados para diferentes hosts.

Instalação

$npx convez-ai basidiocarp/lamella

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
50%
Último commit
há 5 meses
Versão
v0.10.0
Issues abertas
5
Contribuidores
1

Casos de uso

  • Criar marketplaces de plugins portáveis entre Claude Code e Codex
  • Organizar e validar repositories de skills reutilizáveis
  • Distribuir presets de automação e hooks sem duplicação de código

Veredito

Lamella é uma infraestrutura de empacotamento sofisticada para o ecossistema Basidiocarp, voltada para equipes que constroem marketplaces de plugins e precisam sincronizar skills entre múltiplas plataformas de IA. Exige compreensão do arquétipo de projeto e CLI tooling, mas resolve um problema real de fragmentação em ambientes de agentes distribuídos.

README

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

Lamella

Portable resource system for AI coding environments. Builds Claude Code plugin marketplaces and exports the same skill inventory into installable Codex artifacts.

Named after fungal lamellae, the gills beneath the cap that organize and expose the structures responsible for spore release.

Part of the Basidiocarp ecosystem.


The Problem

Useful coding-agent content often gets trapped inside one host format. Skills, hooks, commands, and subagents end up duplicated, drift apart across tools, or become hard to package and validate consistently.

The Solution

Lamella keeps content in one resource system and builds it into multiple host surfaces. Claude builds follow the official Claude Code plugin format, Codex builds export installable skills and agent files, and the manifest layer keeps those outputs ordered and reproducible.


The Ecosystem

ToolPurpose
lamellaSkills, hooks, plugins, and host packaging
capWeb dashboard for the ecosystem
cortinaLifecycle signal capture and session attribution
hyphaePersistent agent memory
myceliumToken-optimized command output
rhizomeCode intelligence via tree-sitter and LSP
sporeShared transport and editor primitives
stipeEcosystem installer and manager
volvaExecution-host runtime layer

Boundary: lamella owns packaged content and host exports. It does not own session memory, shell filtering, code parsing, or lifecycle classification.

Source of truth: author in resources/ and manifests/. Treat dist/ as generated output and rebuild it instead of editing it by hand.


Quick Start

# Claude marketplace build and install
./lamella validate
./lamella validate skills
./lamella validate skill-packages
./lamella scaffold skill meta/my-new-skill --description "Guides ..."
./lamella build-marketplace
./lamella install core python typescript
./lamella install --preset stipe-package-repair
./lamella list

# Codex export and install
./lamella build-codex
./lamella install-codex --all

The install flow resolves manifest dependencies before it builds or installs anything.

Those install commands are Lamella's packaging entrypoints, not the ecosystem's runtime repair surface. Host setup, reinstall policy, and repair behavior belong to stipe, even when stipe calls Lamella by name.

Named install surfaces live in resources/presets/*.toml. The stipe-package-repair preset is the Lamella-owned repair surface that Stipe can call directly with ./lamella install --preset stipe-package-repair without inventing its own package-selection rules.

When Lamella packages statusline presets or customization bundles, it should target Septa's resolved-status-customization-v1 contract instead of owning a host-specific status config format. Lamella is the preset and bundle consumer, not the status-resolution authority.


How It Works

resources/ + manifests/      Lamella                    Host outputs
────────────────────────     ───────                    ────────────
skills, hooks, commands ─►   validators           ─►    dist/claude marketplace
shared subagents        ─►   builders             ─►    dist/codex exports
plugin manifests        ─►   dependency graph     ─►    installable artifacts
  1. Author resources: keep source content in resources/ with manifest metadata in manifests/.
  2. Validate content: check paths, dependencies, references, and host compatibility.
  3. Build host outputs: generate Claude plugins and Codex exports from the same source tree.
  4. Install artifacts: install selected Claude plugins or Codex exports in dependency order.
  5. Publish marketplaces: emit marketplace metadata for local or hosted consumption.

Packaging Surface

SurfaceOutputUse case
Claude Codedist/claude/ marketplace and pluginsLocal or hosted Claude plugin installs
Codexdist/codex/ skills and agent filesInstallable Codex exports under ~/.codex/

Inventory

CategoryCount
Claude plugins52
Skills across plugins301
Layered umbrella plugins7

What Lamella Owns

  • Resource packaging for skills, hooks, commands, and subagents
  • Manifest-driven dependency resolution
  • Claude marketplace generation
  • Codex export generation and installation
  • Validation of content and generated output

What Lamella Does Not Own

  • Long-term memory and training data: handled by hyphae
  • Code intelligence: handled by rhizome
  • Lifecycle capture: handled by cortina
  • Install and host repair policy: handled by stipe
  • Runtime mutation of host state after packaging decisions are made

Key Features

  • Single source, multiple hosts: builds Claude and Codex artifacts from one resource tree.
  • Manifest dependencies: ensure installs happen in the right order.
  • Hosted marketplace support: can publish a GitHub Pages-backed Claude marketplace.
  • Layered plugin model: supports umbrella plugins and focused sub-plugins.
  • Validation pipeline: checks resources, manifests, and generated output before release.

Architecture

lamella/
├── resources/   source skills, hooks, commands, subagents, rules
├── manifests/   Claude and Codex packaging manifests
├── builders/    build and install scripts
├── scripts/     validation and packaging helpers
├── docs/        authoring, reference, migration, and roadmap docs
└── dist/        generated outputs
./lamella validate
./lamella build-marketplace
./lamella build-codex
./lamella install <plugin...>
./lamella install-codex <name...>
make validate

Documentation

Development

make validate
./lamella build-marketplace
./lamella build-codex

License

MIT

Ver o original no GitHub

Bom para

Relacionados