nebius

Build and inspect Nebius cloud infrastructure using Python SDK patterns and scoped inspector scripts.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill nebius-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nebius
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/nebius
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill nebius-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires nebius, boto3, grpcio, protobuf, PyYAML, cryptography, PyJWT, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Designing, provisioning, and auditing Nebius cloud infrastructure requires navigating many services (compute, storage, networking, IAM, Kubernetes) with strict safety rules around credentials, quotas, and mutations. This Skill provides vetted Python SDK patterns, read-only inspector scripts, and category references so infrastructure work follows official service contracts without unsafe writes or incomplete inventory claims. ## Core Features & Use Cases - Read-only infrastructure inspection: Six scripts/inspect_*.py commands report compute, Kubernetes, storage, VPC topology/routes, and quota state with a common {scope, data, complete, errors} JSON envelope and explicit exit codes. - Reusable SDK assets: Importable assets/ modules for SDK runtime, request builders, IAM workflows, and bucket management with bounded pagination, operation waiting, and reconciliation-safe error handling. - Category guidance: References covering compute, storage, networking, observability, IAM, API/SDK usage, MK8s GPU setup, quotas, and active diagnostics, each with official source links and review dates. - Use Case: Ask the agent to inspect a project's quota headroom and VPC route tables before provisioning a GPU node group; it runs the scoped inspectors, reports incomplete collections honestly, and only mutates resources after explicit authorization. ## Quick Start Ask the agent to inspect the Nebius compute and quota state for your project ID using the nebius skill, then plan an authorized GPU node group deployment.

Frequently Asked Questions about nebius

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

FAQPage Schema
How do I inspect Nebius project infrastructure with Python?

Run the bundled inspector scripts such as inspect_compute.py, inspect_vpc_topology.py, or inspect_quotas.py with an explicit --project-id and optional --profile. Each emits a JSON envelope with scope, data, complete flag, and sanitized errors, exiting 0 only on complete collection.

How do I check Nebius quota before provisioning GPUs?

Use inspect_quotas.py with a tenant or project ID to get effective available quota per name and region, merging tenant and project allowances. The tool treats unknown usage as unresolved rather than zero and never equates quota with actual capacity.

Does the nebius skill support managed Kubernetes GPU setup?

Yes, references cover MK8s compatibility matrices, drivers_preset selection, GPU Operator and Network Operator ownership, and GPUDirect RDMA validation. It requires live compatibility and preset checks before configuring InfiniBand fabrics or proof pods.

Can the skill create or modify Nebius resources automatically?

No mutation happens implicitly; inspectors are read-only and asset builders only construct typed requests. Writes require explicit user authorization, submit once with retained operation IDs, and reconcile ambiguous outcomes before any retry.

What Python version and SDK does the nebius skill require?

Python 3.10 or newer is required, with the offline validation baseline pinned to Python 3.12 and nebius==0.6.7. Helpers never install dependencies, log in, or repair credentials on their own.

When should I use Terraform instead of this skill's SDK assets?

Use Terraform when you need declarative resource lifecycle and state management, since Terraform owns apply and state for declarative resources. The SDK assets are callable examples for imperative inspection and authorized one-off operations, not an orchestrator.