oci-standards

Standardizes OCI container image building, labeling, health probing, and Dockerfile hygiene for CI/CD workflows.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill oci-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oci-standards
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/pm-dev-oci/skills/oci-standards
Command: npx skills add https://github.com/cuioss/plan-marshall --skill oci-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

General OCI container standards covering image building, Dockerfile best practices, multi-platform builds, and distroless health probes

Core Features & Use Cases

  • Image Building Best Practices: Minimal base images, multi-stage builds, pinned versions, and proper Dockerfile hygiene
  • Distroless Health Probes: Guidance on health/mgmt interfaces and Kubernetes probes for distroless containers
  • Multi-Platform & Labeling: Support for multi-arch builds, manifest lists, and OCI image labels/annotations

Quick Start

Begin by reviewing the image-building and distroless health-probes references to implement OCI standards in your container workflows.

Frequently Asked Questions about oci-standards

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

FAQPage Schema
What are the best practices for building minimal OCI container images?

OCI container standards recommend using minimal base images, multi-stage builds, and pinned versions in your Dockerfile. This approach ensures reliable images by reducing attack surface and standardizing image-building hygiene.

How do I configure Kubernetes health probes for distroless containers?

Configuring health probes for distroless containers requires exposing health or management interfaces without a shell. OCI standards provide guidance on setting up Kubernetes probes and health endpoints for distroless images to maintain reliable orchestration.

What is the best way to set up multi-platform container builds?

Multi-platform container builds are standardized by generating manifest lists and applying OCI image labels. This ensures images support multiple architectures and follow modern Dockerfile hygiene for scalable CI/CD adoption.

Do I need OCI labels and annotations for my container images?

OCI labels and annotations are necessary for standardizing container metadata. Applying them during image building ensures your images carry proper reference metadata, enabling scalable adoption and progressive reference loading in CI/CD.

When should I use distroless base images in my Dockerfile?

Distroless base images are ideal when you need minimal containers without unnecessary OS components. OCI standards outline using them to reduce image size and attack surface, while providing specific guidance for configuring health probes.