Striatum

Striatum

OCI-native CLI for packaging, versioning, and distributing AI artifacts with dependency management, using standard container registries.

Striatum gives skills, prompts, and workflows the same publish/pull/install lifecycle that container images already have, with full dependency resolution across the artifact tree. You author an `artifact.json` manifest, declare dependencies (OCI or Git), pack the files into an OCI image, push to any compliant registry, and install into Claude Code or Cursor with a single command. Striatum resolves transitive dependencies, detects version conflicts, and fetches anything missing from the local cache.

Install

Homebrew (macOS / Linux)

brew tap hbelmiro/striatum https://github.com/hbelmiro/striatum
brew install striatum

Binary releases

Download the latest binary from [GitHub Releases](https://github.com/hbelmiro/striatum/releases).

From source

go install github.com/hbelmiro/striatum/cmd/striatum@latest

Quickstart

# Scaffold a new skill
striatum init --name my-skill --kind Skill --entrypoint SKILL.md

# Edit SKILL.md, then pack and push
striatum pack
striatum push quay.io/my-org/my-skill:1.0.0

# Install into Claude Code
striatum install --target claude quay.io/my-org/my-skill:1.0.0

See [docs/demo.md](docs/demo.md) for a full walkthrough with dependency resolution, Git dependencies, and install/uninstall flows.

Artifact manifest

Every artifact has an `artifact.json` at its root. A minimal manifest looks like this:

{
  "apiVersion": "striatum.dev/v1alpha2",
  "kind": "Skill",
  "metadata": {
    "name": "my-skill",
    "version": "1.0.0"
  },
  "spec": {
    "entrypoint": "SKILL.md",
    "files": ["SKILL.md"]
  }
}

Artifacts can declare OCI and Git dependencies. During `pack` and `pull`, Striatum resolves the full dependency tree, detects version conflicts, and fetches anything missing from the local cache.

{
  "apiVersion": "striatum.