Summary

Example of the concept: https://gitlab.com/xrow-public/helm-openclaw/-/blob/main/chart/README.md?ref_type=heads#setup-with-a-profile

REF:

• https://learn.microsoft.com/en-us/azure/container-registry/container-registry-manage-artifact
• https://oras.land/
• https://opencontainers.org/

Problem to solve

The OCI standard better standard is a standard for distributing artifacts (Skills, Plugins and Workspace templates) with many problems solved. Also looking at disconnceted setups.

Proposed solution

Example: Load a workspace:

if [[ -v GITLAB_TOKEN && -n ${PROFILE_REGISTRY} ]]; then
  echo ${GITLAB_TOKEN} | oras login ${PROFILE_REGISTRY} -u token --password-stdin
  oras pull --output ${OPENCLAW_STATE_DIR}/workspace ${PROFILE_IMAGE}
fi

Alternatives considered

Other exisiting package formats

Impact

The whole ecosystem

Evidence/examples

https://gitlab.com/xrow-public/helm-openclaw/
https://gitlab.com/xrow-public/helm-openclaw/container_registry

Additional information

This is most likely a BC break but how about:

openclaw registry login registry.gitlab.com -u X -p X
openclaw skills install oci://registry.gitlab.com/xrow-public/helm-openclaw/skills/gitlab-agent:1.44.12
openclaw plugins install oci://registry.gitlab.com/xrow-public/helm-openclaw/plugins/gitlab-agent:1.44.12