Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

build-and-push-image

Estrelas15

Forks8

Atualizado17 de julho de 2026 às 19:23

Use when building, tagging, validating, or pushing NPA workbench container images for Nebius registry-backed workflows.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

nebius

nebius/nebius-physical-ai

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	build-and-push-image
description	Use when building, tagging, validating, or pushing NPA workbench container images for Nebius registry-backed workflows.

Build And Push Image

When To Use

Use this skill when a task changes Dockerfiles, image manifests, registry tags, or workflow image references for NPA workbench tools.

Procedure

Resolve runtime registry settings with npa configure or npa.clients.config.resolve_container_registry or npa configure.
Build from the checked-in Dockerfile for the tool; do not invent a detached image source outside the repo.
Tag images with the configured registry prefix and a version that matches the tool manifest or release plan.
Inspect the image or manifest before pushing.
Update image manifests, workflow YAML, and skill guidance together when a command starts depending on the new image.

Three-Tier Contract

CLI: use docker buildx build, tool-specific deploy --container-image, and command help from the affected workbench tool.
SDK: resolve registry and project settings through npa.clients.config instead of hardcoded env reads.
YAML: workflow image_id values should come from variables or manifests, especially SONIC's npa/src/npa/deploy/sonic_image_manifest.json.

Packaging Contract

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.

Gotchas

Do not commit concrete registry IDs or private image digests from a live account unless the repo already treats that value as public.
Nebius registry auth expires; a push or pull failure may require a refreshed token rather than an image change.
For GPU-specific images, verify the target GPU family before changing defaults.

Verify

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.

Mais deste repositório

mesmo repositório

dataset

nebius/nebius-physical-ai

Use when ingesting, validating, curating, or querying production sensor data as a versioned dataset-of-record, or wiring the dataset-ingest-curate workflow.

2026-07-2415

scenario-gen

nebius/nebius-physical-ai

Use when generating adversarial scenarios via RL, ranking mined failures of a policy-under-test, or wiring the adversarial-scenario-hardening workflow.

2026-07-2415

cosmos3-codebase-nav

nebius/nebius-physical-ai

Use when navigating the Cosmos3 integration in NPA or locating upstream Cosmos3 framework files, defaults, scripts, configs, recipes, and docs.

2026-07-2415

cosmos3-env-troubleshoot

nebius/nebius-physical-ai

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.

2026-07-2415

cosmos3-setup

nebius/nebius-physical-ai

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.

2026-07-2415

physical-ai-context

nebius/nebius-physical-ai

Use for Claude Code reviews that need robotics, simulation, GPU-routing, sim-to-real, or BDD100K pipeline domain context.

2026-07-2415

Build And Push Image

When To Use

Use this skill when a task changes Dockerfiles, image manifests, registry tags, or workflow image references for NPA workbench tools.

Procedure

Resolve runtime registry settings with npa configure or npa.clients.config.resolve_container_registry or npa configure.

Build from the checked-in Dockerfile for the tool; do not invent a detached image source outside the repo.

Tag images with the configured registry prefix and a version that matches the tool manifest or release plan.

Inspect the image or manifest before pushing.

Update image manifests, workflow YAML, and skill guidance together when a command starts depending on the new image.

Three-Tier Contract

CLI: use docker buildx build, tool-specific deploy --container-image, and command help from the affected workbench tool.

SDK: resolve registry and project settings through npa.clients.config instead of hardcoded env reads.

YAML: workflow image_id values should come from variables or manifests, especially SONIC's npa/src/npa/deploy/sonic_image_manifest.json.

Packaging Contract

Gotchas

Do not commit concrete registry IDs or private image digests from a live account unless the repo already treats that value as public.

Nebius registry auth expires; a push or pull failure may require a refreshed token rather than an image change.

For GPU-specific images, verify the target GPU family before changing defaults.

Verify

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.