convez.ai
MCP Server
Capacium

capacium

Capacium/capacium

Ver no GitHub
BomPluginScore · de 0 a 100

Capability Packaging System – package, distribute, and manage AI agent capabilities (skills, bundles, tools, prompts, templates, workflows)

Instalação

$npx convez-ai Capacium/capacium

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
1
Forks
0
Acompanhando
0
Saúde
75%
Último commit
há 22 horas
Versão
v1.1.10
Issues abertas
0
Contribuidores
3

README

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

Capacium

CI CodeQL Release License Python Tests

Capability-native packaging for the AI agent era.

One capability package, any agent framework.

Capacium defines a standard manifest format (capability.yaml), a CLI (cap) for package management, and a trust model based on SHA-256 fingerprinting and Ed25519 signing. Framework adapters bridge the gap between the package format and where capabilities actually run — OpenCode, Claude Code, Gemini CLI, Cursor, and Continue.dev. Includes native MCP (Model Context Protocol) Server support.

Works fully offline from local paths. The Exchange layer (separate repo) adds remote registry discovery with taxonomy, trust states, and crawler-based capability discovery.

Installation

1. Python Global (Recommended)

You can install Capacium globally in an isolated environment using pipx.

pipx install git+https://github.com/Capacium/capacium.git@v0.14.2

# Or with optional signing and YAML support:
pipx install "capacium[yaml,signing] @ git+https://github.com/Capacium/capacium.git@v0.14.2"

(Note: PyPI publishing pip install capacium is pending organization approval and currently unavailable).

2. Standalone Binaries

If you don't use Python, you can download standalone executables directly from the GitHub Releases page. Extract the archive and place cap in your $PATH.

3. Docker (GHCR)

Run Capacium safely in a container with your directories mounted:

docker run --rm -v ~/.capacium:/root/.capacium -v $(pwd):/workspace ghcr.io/capacium/cap:0.14.2

4. macOS / Linux (Homebrew)

brew install capacium/tap/capacium

Quickstart

# Install a capability
cap install code-reviewer --source ./my-skill

# Create a new capability (interactive)
cap init

# Create a new capability (non-interactive)
cap init --name my-skill --kind skill --version 0.1.0

# Package for distribution
cap package

# Publish to the Exchange registry
cap publish ./dist/my-skill-0.1.0.tar.gz

# List installed capabilities
cap list

# Verify integrity
cap verify --all

# Diagnose missing host runtimes for installed MCP capabilities
cap doctor

# List runtimes Capacium knows about (uv, node, python, docker, …)
cap runtimes list

# Print the install command for a runtime (does NOT execute it)
cap runtimes install uv

# Search the exchange
cap search code-review

# Start the marketplace web UI
cap marketplace

# Generate signing keys
cap key generate mykey

# Sign a capability
cap sign my-skill --key mykey

Publishing Your Skills in 5 Minutes

Got an agent skill, prompt, or MCP server? Publish it on Capacium.

# 1. Create the manifest
cap init
# → name: my-skill
# → kind: skill
# → version: 0.1.0
# → description: Does amazing things

# 2. Package it
cap package
# ✓ Created dist/local-my-skill-0.1.0.tar.gz

# 3. Publish to Exchange
export CAPACIUM_API_TOKEN="cp_..."
cap publish ./dist/local-my-skill-0.1.0.tar.gz
# ✓ Published my-skill v0.1.0

# Users can now install it:
# cap install my-org/my-skill

More in Publishing — CI integration, versioning, signing, and registry setup.

Documentation

GuideDescription
Getting StartedInstallation, quickstart, examples
CLI ReferenceComplete command reference
Manifest Formatcapability.yaml reference
Signing & KeysEd25519 signing and verification
MarketplaceWeb UI and registry server
Bundle SupportMulti-capability bundles
Lock FilesDependency pinning
Framework AdaptersCross-framework installation
RuntimesHost runtime resolver, cap doctor, cap runtimes
PublishingFull lifecycle: dev → CI → Exchange publish
RegistryLocal and remote registry
API SpecRemote registry protocol

Capability Kinds

KindDescriptionExample
skillAgent skill/promptCode review, doc generator
bundleCollection of sub-capabilitiesDev toolkit, skill suite
toolFunction/tool definitionWeb search, calculator
promptReusable prompt templateSystem prompts, instructions
templateProject/code templateSkill scaffold, adapter template
workflowMulti-step agent workflowCI pipeline, data chain
mcp-serverMCP ServerMCP filesystem, db-connector
connector-packTool/Service integrationSlack, GitHub, Jira connector pack

Features

  • Agent-agnostic — Same package works across OpenCode, Claude Code, Gemini CLI, Cursor, Continue.dev
  • First-class MCP Support — Deploy and discover MCP servers as native capabilities.
  • Eight capability kinds — Skills, bundles, tools, prompts, templates, workflows, mcp-servers, connectors.
  • Manifest-first — Standard capability.yaml with metadata, dependencies, and framework targets
  • Trust & Governance — SHA-256 fingerprinting and Ed25519 signing for integrity verification.
  • Registry-optional — Works fully offline; remote registry adds discovery and distribution.
  • Lock files — capability.lock pins exact versions and fingerprints for reproducible installs.
  • Zero external deps (core) — Uses only Python stdlib (argparse, sqlite3, hashlib, urllib)

Comparison

CapabilityDirect copy/scriptFramework-specificCapacium
Cross-framework formatNoNoYes
Manifest standardNoPartialYes
Fingerprint verificationNoNoYes
Cryptographic signingNoNoYes
Dependency resolutionManualNoYes
Offline operationYesPartialYes
Registry discoveryNoVendor lock-inOptional

License

Apache-2.0. See LICENSE.

Ver o original no GitHub

Bom para

Relacionados