oci-artifacts

Store and version large files in OCI registries linked to GitHub repositories.

4|1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/boettiger-lab/agent-skills --skill oci-artifacts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oci-artifacts
Source: https://github.com/boettiger-lab/agent-skills/tree/main/oci-artifacts
Command: npx skills add https://github.com/boettiger-lab/agent-skills --skill oci-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Storing and versioning large files like model checkpoints, datasets, and build artifacts alongside a GitHub repository using OCI registries to avoid bloating history and to keep assets in sync with code.

Core Features & Use Cases

  • Content-addressed artifacts with sha256 digests for reproducible provenance and immutability.
  • Metadata-rich push/pull workflows with source linkage and optional signing and SBOMs.
  • Use cases include model checkpoints, test fixtures, compiled binaries, and dataset snapshots that travel with the repository.

Quick Start

Push your first artifact to ghcr.io using the oras push workflow and link it to your repository.

Frequently Asked Questions about oci-artifacts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I store large model checkpoints and datasets in GitHub without bloating repo history?

You can store large files like model checkpoints and datasets in OCI registries to avoid bloating GitHub history. This approach keeps your assets in sync with code using content-addressing and metadata annotations for provenance.

How does content-addressing work when versioning artifacts with oras and ghcr.io?

Content-addressing with oras and ghcr.io uses sha256 digests to pin exact artifact versions, ensuring reproducible provenance and immutability. This mechanism guarantees that the pulled artifact matches the exact version linked to your source repository.

Can I link artifacts pushed to an OCI registry back to my source repository?

Yes, you can link artifacts pushed to an OCI registry back to your source repository using metadata-rich push workflows. This source linkage ties the artifact to the specific code state, ensuring reproducible access to datasets or compiled binaries.

What is the best way to secure and verify reproducible access to OCI artifacts?

The best way to secure and verify reproducible access to OCI artifacts is by combining sha256 digest pinning with optional signing and SBOMs. These metadata-rich workflows ensure that your build artifacts and test fixtures remain immutable and verifiable.

Does the oras push workflow support adding SBOMs to artifact metadata?

Yes, the oras push workflow supports adding SBOMs to artifact metadata. This feature allows you to attach software bills of materials alongside your model checkpoints or dataset snapshots for enhanced security and provenance tracking.

Why should I use OCI registries instead of Git LFS for managing compiled binaries and dataset snapshots?

OCI registries prevent bloating repository history while keeping compiled binaries and dataset snapshots in sync with code. Unlike standard Git storage, OCI registries provide content-addressed sha256 digests, optional signing, and metadata annotations for secure, reproducible artifact management.