oci

Standardize container image and OCI artifact build, tag, sign, scan, and publish workflows.

47|11|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/styrene-lab/omegon --skill oci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oci
Source: https://github.com/styrene-lab/omegon/tree/main/skills/oci
Command: npx skills add https://github.com/styrene-lab/omegon --skill oci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from container image and OCI artifact workflows by giving you consistent conventions for building, tagging, signing, scanning, and publishing registry content.

Core Features & Use Cases

  • Container Image Standards: Use Containerfile-first builds, multi-stage patterns, non-root runtime users, and immutable tags for reproducible releases.
  • Registry Operations: Handle authentication and pushes for GHCR, AWS ECR, Docker Hub, Helm OCI charts, SBOMs, signatures, attestations, and arbitrary OCI artifacts.
  • Cross-Platform Delivery: Avoid arm64 and amd64 mismatches, manage buildx multi-arch builds, and apply cache and cleanup practices for CI/CD pipelines.
  • Use Case: A platform engineer can use this Skill to prepare a release image, sign it, scan it for vulnerabilities, and publish both the image and related artifacts to a registry with fewer deployment surprises.

Quick Start

Ask for OCI guidance for your project so the workflow, build, tag, sign, scan, and push steps are aligned with the repository and target registry.

Frequently Asked Questions about oci

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

FAQPage Schema
How do I standardize container image builds and OCI artifact workflows for CI/CD?

Container image and OCI artifact workflows are standardized by enforcing Containerfile-first builds, immutable tagging, multi-architecture handling, and consistent registry login patterns for reproducible releases.

What's the best way to build and sign multi-architecture container images for a registry?

Building and signing multi-architecture container images requires buildx for cross-platform delivery, cosign for signing, and immutable tags to avoid arm64 and amd64 mismatches during registry publishing.

How do I publish Helm charts and SBOMs to an OCI registry like GHCR?

Publishing Helm OCI charts, SBOMs, and attestations to registries like GHCR requires standard registry authentication patterns and treating the artifacts as OCI content alongside your container images.

Do I need a Containerfile to use OCI artifact workflows?

Yes, OCI artifact workflows require Containerfile-based builds to enforce multi-stage patterns, non-root runtime users, and reproducible release conventions for your container images.

Why should I use immutable tags for container images in local development and CI/CD?

Immutable tags for container images prevent deployment surprises by ensuring reproducible releases, avoiding accidental overwrites, and maintaining consistent state across local development and CI/CD pipelines.

Can I scan container images for vulnerabilities before pushing to AWS ECR or Docker Hub?

Yes, security scanning conventions are applied before publishing to registries like AWS ECR or Docker Hub, ensuring container images and related artifacts are checked for vulnerabilities during the build process.