PBnJ | PMOVES + Pinokio Bridge

Orchestrate PMOVES.AI deployments across Docker, Kubernetes, KVM4, and VPS targets.

6|Updated Aug 26, 2025
One-click install
npx skills add https://github.com/POWERFULMOVES/PMOVES.AI --skill pbnj-pmoves-pinokio-bridge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PBnJ | PMOVES + Pinokio Bridge
Source: https://github.com/POWERFULMOVES/PMOVES.AI/tree/main/pbnj/pinokio/api/pmoves-pbnj
Command: npx skills add https://github.com/POWERFULMOVES/PMOVES.AI --skill pbnj-pmoves-pinokio-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PBnJ PMOVES + Pinokio Bridge provides a single, unified control plane to deploy and manage PMOVES.AI infrastructure across multiple targets with one click.

Core Features & Use Cases

  • Coordinate Local Dev Docker Compose stacks, AI Lab Kubernetes, KVM4 production environments, VPS fleets, and network tooling from a single interface.
  • Provide consistent deployment workflows, health checks, and diagnostic capabilities across Z890, 5090, 4090, KVM4-1/4-2, and KVM2 nodes.
  • Enable rapid provisioning, testing, and troubleshooting for multi-target PMOVES deployments with minimal context switching.

Quick Start

Start by opening the PBnJ UI and selecting a deployment target to begin orchestration.

Frequently Asked Questions about PBnJ | PMOVES + Pinokio Bridge

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

FAQPage Schema
How do I manage multi-target Kubernetes and Docker Compose deployments from a single interface?

You can coordinate multi-target deployments through a unified Pinokio UI that orchestrates Local Dev Docker Compose stacks, AI Lab Kubernetes, and VPS fleets with single-click script-driven actions.

What is the best way to run cluster health checks across different infrastructure nodes?

Cluster health checks across Z890, 5090, 4090, and KVM nodes are executed by selecting a deployment target in the PBnJ UI, which runs infrastructure diagnostics to verify node status.

Can I use Pinokio for end-to-end deployment orchestration across production and dev environments?

Yes, Pinokio acts as a unified control plane for end-to-end deployment orchestration, coordinating workflows across Local Dev Docker Compose, KVM4 production, and AI Lab Kubernetes environments.

How do I deploy models to a VPS fleet without manual context switching between nodes?

Model deployment to a VPS fleet is handled by selecting the VPS target in the unified interface, which orchestrates the provisioning and deployment scripts across KVM2 and other nodes automatically.

Does this bridge support infrastructure diagnostics for both local Docker Compose and Kubernetes clusters?

Yes, the bridge provides consistent infrastructure diagnostics and troubleshooting capabilities for both Local Dev Docker Compose stacks and AI Lab Kubernetes clusters from a single UI.

What are the limitations of using script-driven actions for multi-target infrastructure orchestration?

Orchestration relies on script-driven actions within the Pinokio UI, meaning deployment workflows and diagnostics are constrained to the predefined scripts and supported targets like Z890, 5090, and KVM4 nodes.