workbench-tool

Standardize containerized FastAPI services with mandatory health and execution endpoints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the fragmentation of tool development by providing a unified architecture for containerized FastAPI services, ensuring consistent deployment and communication patterns across the Nebius Physical AI ecosystem.

Core Features & Use Cases

  • Unified Architecture: Enforces a standard FastAPI service structure for all workbench tools, ensuring consistent API, CLI, and SDK access.
  • Standardized Data Flow: Mandates S3-based communication between tools using consistent input/output path flags to prevent pipeline integration failures.
  • Use Case: When developing a new simulation or training tool, use this pattern to ensure your service exposes the required health, status, and execution endpoints, making it immediately compatible with the broader NPA workflow orchestration.

Quick Start

Use the workbench-tool skill to validate the deployment configuration and endpoint structure for a new containerized service.

Frequently Asked Questions about workbench-tool

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

FAQPage Schema
How do I standardize a FastAPI service for containerized deployment?

Use this Skill to enforce a standard FastAPI service structure for containerized deployment, ensuring consistent API, CLI, and SDK access across the Nebius Physical AI workbench ecosystem.

What is S3-based data flow in containerized API orchestration?

S3-based data flow mandates communication between containerized tools using consistent input and output path flags, which prevents pipeline integration failures during workflow orchestration.

How do I add health and execution endpoints to a FastAPI workbench tool?

Apply this Skill's architecture to expose mandatory health, status, and execution endpoints, making your new simulation or training tool immediately compatible with workflow orchestration.

Can I use custom CLI argument names for Nebius Physical AI workflow compatibility?

No, workflow compatibility requires strict adherence to specific CLI argument naming conventions, ensuring standardized data flow and consistent integration across the Nebius Physical AI workbench.

Why does my containerized FastAPI service fail Nebius Physical AI pipeline integration?

Integration fails when services lack mandatory health and execution endpoints or deviate from strict S3-based data flow patterns and required CLI argument naming conventions.

Does the workbench-tool skill validate deployment configurations for new services?

Yes, the workbench-tool skill validates the deployment configuration and endpoint structure for new containerized FastAPI services to ensure they meet Nebius Physical AI standards.