nebius-infra

Provision Nebius cloud resources and manage IAM authentication for physical-AI workflows.

17|8|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/nebius/nebius-physical-ai --skill nebius-infra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nebius-infra
Source: https://github.com/nebius/nebius-physical-ai/tree/main/skills/tools/nebius-infra
Command: npx skills add https://github.com/nebius/nebius-physical-ai --skill nebius-infra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of managing Nebius runtime environments, ensuring that object storage, container registries, and GPU clusters are correctly provisioned and authenticated for physical-AI workloads.

Core Features & Use Cases

  • Runtime Configuration: Standardizes the setup of local configuration and credential files for Nebius services.
  • Resource Provisioning: Ensures required S3 buckets and Kubernetes resources exist via an additive, non-destructive setup process.
  • Authentication Management: Provides a robust, reusable mechanism for refreshing short-lived Nebius IAM tokens to prevent registry pull failures.

Quick Start

Use the nebius-infra skill to provision the required project resources and verify the current environment configuration.

Frequently Asked Questions about nebius-infra

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

FAQPage Schema
How do I provision Kubernetes clusters and object storage for physical-AI workflows?

Provisioning Kubernetes clusters and object storage for physical-AI workflows is handled by standardizing configuration and ensuring required S3 buckets and compute resources exist via an additive, non-destructive setup process. This validates the environment for distributed compute nodes.

Why does my container registry pull fail with an expired Nebius IAM token?

An expired Nebius IAM token causes container registry pull failures across distributed compute nodes, which this skill resolves by providing a robust, reusable mechanism for refreshing short-lived credentials to maintain persistent registry access.

What is the best way to automate environment validation for GPU routing in Nebius?

Automating environment validation for GPU routing in Nebius requires a configuration mechanism that verifies local setup and ensures secure credential handling for physical-AI workloads across distributed compute nodes.

Does provisioning Nebius cloud infrastructure modify or destroy existing Kubernetes resources?

Provisioning Nebius cloud infrastructure does not destroy existing Kubernetes resources, because the setup process is additive and non-destructive, ensuring required S3 buckets and compute nodes exist without altering current configurations.

Can I use Nebius infrastructure configuration to set up persistent registry access across distributed compute nodes?

Setting up persistent registry access across distributed compute nodes is supported by managing Nebius infrastructure configuration, which facilitates container registries and handles short-lived IAM token authentication to prevent pull failures.