pipergo2-demo

Route PiperGo2 demo intents to rule-based or VLA robot actions.

1.7k|97|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/PhyAgentOS/PhyAgentOS --skill pipergo2-demo-phyagentos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipergo2-demo
Source: https://github.com/PhyAgentOS/PhyAgentOS/tree/main/PhyAgentOS/skills/pipergo2-demo
Command: npx skills add https://github.com/PhyAgentOS/PhyAgentOS --skill pipergo2-demo-phyagentos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deterministic PiperGo2 routing for demo tasks across desk navigation, table visibility inquiries, and red cube pick-and-return scenarios.

Core Features & Use Cases

  • Deterministic routing of PiperGo2 demo intents to appropriate actions for go to desk, what is on the table, and both rule-based and VLA-based pick operations.
  • Supports single-robot and fleet-like setups by selecting the appropriate robot and coordinating actions via the PiperGo2 workflow.
  • Built-in safety and gating to ensure actions are only dispatched when the HAL watchdog is running and when preconditions are met.

Quick Start

Issue a command such as go to desk to verify deterministic PiperGo2 routing.

Frequently Asked Questions about pipergo2-demo

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

FAQPage Schema
How do I route robot intents deterministically for navigation and pick tasks?

To route intents deterministically, map input cues to specific robot actions using strict rules, ensuring either rule-based or VLA approaches for navigation and pick tasks.

Does deterministic robot routing support both single-robot and fleet scenarios?

Deterministic routing supports both single-robot and fleet-like setups, requiring explicit robot selection when multiple robots exist to coordinate actions via the PiperGo2 workflow.

What is the difference between rule-based and VLA routing for pick-and-return tasks?

Rule-based routing (C) and VLA routing (D) are distinguished by input cues, directing the robot to perform pick tasks using either predefined logic or vision-language-action approaches.

Do I need a HAL watchdog running to execute PiperGo2 demo commands?

Yes, a running HAL watchdog is required. Built-in safety gating ensures actions are only dispatched when the watchdog is active and all preconditions are met.

How do I test deterministic routing for a go to desk command?

Issue a command such as go to desk to verify deterministic PiperGo2 routing, which will map the intent directly to the appropriate navigation action.