Skillget

claudio

agent
SUMMARY

Portable Claude Code Setup

README.md

claudio

OCI image to make claude code portable; the model is being setup to use through Google Vertex AI API.

Additional functionality is provided through the claudio-skills marketplace.

Build

To build the container run the command:

make oci-build

This builds for the native architecture of the current platform.

You can customize the image name and tag:

IMAGE_REPO=ghcr.io/myorg/claudio IMAGE_TAG=latest make oci-build

By default, the Makefile uses Podman. To use Docker instead:

CONTAINER_MANAGER=docker make oci-build

Available targets:

  • oci-build - Build container image for native architecture
  • oci-rebuild - Remove existing image and rebuild from scratch (no cache)
  • oci-push - Push container image
  • oci-tag - Tag existing image with new tag
  • oci-manifest-build - Create multi-arch manifest from arch-tagged images
  • oci-manifest-push - Push manifest to registry

Claudio Skills Reference

During the image build, claudio clones claudio-skills into /home/claudio/claudio-skills/ and:

  1. Fetches the specified git ref — a branch, tag, or pull request head
  2. Runs tool installers — iterates over claudio-plugin/tools/*/install.sh and executes each one (e.g. jq, kubectl)
  3. Installs Python dependencies — installs packages from claudio-plugin/tools/python/*-requirements.txt
  4. Generates plugin configs — registers skills and tools so Claude can discover them at runtime

The git ref is controlled by two build args:

  • CS_REF_TYPE — one of branch, tag, or pr (default: branch)
  • CS_REF — the branch name, tag name, or PR number (default: main)
# From a branch (default)
CS_REF_TYPE=branch CS_REF=main make oci-build

# From a tag
CS_REF_TYPE=tag CS_REF=v0.1.0 make oci-build

# From a pull request
CS_REF_TYPE=pr CS_REF=9 make oci-build

Testing claudio-skills changes in downstream images

When developing changes to claudio-skills that affect a downstream image (e.g. aipcc-claudio), you can test end-to-end before merging:

  1. Open a PR in claudio-skills (e.g. PR #9)
  2. Build the claudio base image referencing that PR:
    CS_REF_TYPE=pr CS_REF=9 make oci-build
    This produces a local image tagged quay.io/aipcc-cicd/claudio:v1.0.0-dev.
  3. In the downstream repo, point the FROM line at that local image (or tag it to match the expected base tag) and build:
    # In aipcc-claudio
make oci-build
  4. Run the resulting container and verify the changes work as expected.

Usage

The recommended way to run claudio locally is through a wrapper script. It handles volume mounts, user namespace mapping, and environment loading automatically.

Wrapper Script Setup

Create ~/.local/bin/claudio with the following content and make it executable (chmod +x):

#!/bin/bash

# Load environment variables from ~/.config/claudio/.env if it exists
ENV_FILE="${HOME}/.config/claudio/.env"
if [ -f "$ENV_FILE" ]; then
  set -a
  source "$ENV_FILE"
  set +a
fi

podman run -it --rm --userns=keep-id \
  -v ${HOME}/.kube/claudio-reader.kubeconfig:/home/claudio/.kube/config:ro \
  -v ${HOME}/.config/gcloud:/home/claudio/.config/gcloud \
  -v ${PWD}:/home/claudio/workdir \
  -v ${HOME}/.docker/config.json:/home/claudio/.docker/config.json:ro \
  -v ${HOME}/.gitconfig:/home/claudio/.gitconfig:ro \
  -v ${HOME}/.ssh:/home/claudio/.ssh:ro \
  -v ${SSH_AUTH_SOCK}:/tmp/ssh-agent.sock \
  -e SSH_AUTH_SOCK=/tmp/ssh-agent.sock \
  -e GITLAB_TOKEN="${GITLAB_TOKEN}" \
  -e ANTHROPIC_VERTEX_PROJECT_ID="${ANTHROPIC_VERTEX_PROJECT_ID}" \
  -e ANTHROPIC_VERTEX_PROJECT_QUOTA="${ANTHROPIC_VERTEX_PROJECT_QUOTA}" \
  -e SLACK_XOXC_TOKEN="${SLACK_XOXC_TOKEN}" \
  -e SLACK_XOXD_TOKEN="${SLACK_XOXD_TOKEN}" \
  quay.io/aipcc-cicd/claudio:v0.4.1 --allowedTools "Write(*)" "Glob(*)" "Read(*)" "$@"

The gcloud mount shares your host's Google Cloud credentials with the container. This is required because claudio uses Google Vertex AI as its default Claude API provider — ANTHROPIC_VERTEX_PROJECT_ID and ANTHROPIC_VERTEX_PROJECT_QUOTA identify the GCP project, while the gcloud credentials handle authentication. Make sure you're logged in on the host first (gcloud auth application-default login).

The kubeconfig mount expects a dedicated read-only kubeconfig at ~/.kube/claudio-reader.kubeconfig. This keeps claudio's cluster access separate from your default kubeconfig.

The .gitconfig, .ssh, and SSH agent socket mounts are only needed if you want claudio to interact with git repositories over SSH or create SSH-signed commits. If you only work with HTTPS remotes and unsigned commits, these can be omitted.

Store your secrets in ~/.config/claudio/.env:

GITLAB_TOKEN=...
ANTHROPIC_VERTEX_PROJECT_ID=...
ANTHROPIC_VERTEX_PROJECT_QUOTA=...
SLACK_XOXC_TOKEN=xoxc-...
SLACK_XOXD_TOKEN=xoxd-...

Working with Local Projects

The wrapper script mounts ${PWD} to /home/claudio/workdir automatically. Run claudio from the root of your project to work with local files:

cd ~/my-project
claudio

One-time Prompt

claudio -p "do something for me Claudio"

Yorumlar (0)

Sonuc bulunamadi