Menu
Use when building, tagging, validating, or pushing NPA workbench container images for Nebius registry-backed workflows.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when ingesting, validating, curating, or querying production sensor data as a versioned dataset-of-record, or wiring the dataset-ingest-curate workflow.
Use when generating adversarial scenarios via RL, ranking mined failures of a policy-under-test, or wiring the adversarial-scenario-hardening workflow.
Use when navigating the Cosmos3 integration in NPA or locating upstream Cosmos3 framework files, defaults, scripts, configs, recipes, and docs.
Use when Cosmos3 setup, fetch, inference, CUDA, uv, Docker, Hugging Face, GitHub, NGC, or checkpoint staging fails in NPA or in an upstream Cosmos framework checkout.
Use when setting up Cosmos3 access through NPA, checking source or Hugging Face reachability, staging the public Cosmos3 framework and checkpoint cache, or deciding which NPA workflow to use before inference.
Use for Claude Code reviews that need robotics, simulation, GPU-routing, sim-to-real, or BDD100K pipeline domain context.
| name | build-and-push-image |
| description | Use when building, tagging, validating, or pushing NPA workbench container images for Nebius registry-backed workflows. |
Use this skill when a task changes Dockerfiles, image manifests, registry tags, or workflow image references for NPA workbench tools.
npa configure or
npa.clients.config.resolve_container_registry or npa configure.docker buildx build, tool-specific deploy --container-image, and
command help from the affected workbench tool.npa.clients.config instead of
hardcoded env reads.image_id values should come from variables or manifests,
especially SONIC's npa/src/npa/deploy/sonic_image_manifest.json.Before changing Dockerfiles, read docs/workbench/container-packaging.md and
update npa/docker/workbench/packaging-contract.yaml when adding an image or
changing its tier (service / job / interactive).
Security baseline: non-root final USER, no secrets in layers, digest-pinned
bases where possible, Trivy scan coverage. Service images should expose ports
and prefer a HEALTHCHECK or K8s probe on /health.
npa/.venv/bin/python -m pytest npa/tests/guardrails/test_skills_index.py -q
The smoke test verifies current deploy command help and the image-manifest file paths used by the skill.