registry-catalog

Generates and validates container registry catalog indexes and Kubernetes install manifests for GitOps deployment.

11|9|Updated May 25, 2026
One-click install
npx skills add https://github.com/projectbluefin/lab --skill registry-catalog-projectbluefin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: registry-catalog
Source: https://github.com/projectbluefin/lab/tree/main/docs/skills/registry-catalog
Command: npx skills add https://github.com/projectbluefin/lab --skill registry-catalog-projectbluefin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining a browsable catalog of container images and turning a selected app into validated, deployable Kubernetes manifests requires manual translation of registry metadata, volume/port mappings, and GitOps PR workflows. This Skill codifies that entire pipeline for the lab's transparent registry catalog. ## Core Features & Use Cases - Catalog index generation: Poll provider APIs (linuxserver.io, NVIDIA NGC) to regenerate docs/data/catalog/<provider>.json following the catalog index schema. - Install-time translation: Convert upstream LSIO config (env vars, volumes, ports, security capabilities) into Kubernetes Deployments, PVCs, and ClusterIP Services with lab conventions like local-path storage. - Offline validation and GitOps PR flow: Validate rendered manifests against resource-quota and registry-allowlist rules, then commit to a branch and open a PR via the GitHub REST API. - Use Case: Run argo submit --from workflowtemplate/catalog-install-lsio -p app=jellyfin -p mode=gitops to render, validate, and open a PR that ArgoCD deploys into a catalog-jellyfin namespace. ## Quick Start Ask the assistant to render and validate a catalog app install by running the LSIO install translator for jellyfin and then submitting the gitops-mode Argo workflow.

Frequently Asked Questions about registry-catalog

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

FAQPage Schema
How do I add a new container catalog provider like NGC or DockerHub?▼

Add the provider section to the catalog index schema doc, create a collect_<provider>_catalog.py poller script, generate docs/data/catalog/<provider>.json, and optionally add a provider-specific translator. New providers only need name, description, image_ref, and config_pointer populated.

How do I install a linuxserver.io app through the GitOps workflow?▼

Submit the catalog-install-lsio WorkflowTemplate with the app name and mode=gitops using argo submit. The workflow renders manifests, runs offline validation, commits to a bot branch, and opens a PR via the GitHub REST API for ArgoCD to deploy.

What does the catalog manifest validation check before deployment?▼

The offline validator requires apiVersion, kind, and metadata.name, enforces cpu/memory/ephemeral-storage requests and limits on every container, forbids hostPath volumes, requires local-path storageClassName on PVCs, and restricts images to allowlisted registries.

Why does the catalog install workflow fail to open a PR with gh CLI?▼

The lab-runner image has no gh CLI and no tar, so gh pr create fails. PRs must be opened with curl and python3 against the GitHub REST API instead.

Can I use the NGC per-org containers endpoint for the NVIDIA catalog?▼

No, the /v2/orgs/nvidia/containers endpoint returns 401 without an API key. Use the public unauthenticated search endpoint /v2/search/catalog/resources/CONTAINER and filter results to orgName nvidia.