skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
openvinotoolkit/physicalai83 installs

physicalai-runtime-adding-a-robot-integration

Adds or modifies robot hardware integrations under physicalai.robot. Use when implementing the Robot protocol, SO101 or Trossen WidowX drivers, robot connect helpers, verify.py checks, optional extras so101 or trossen, or tests in tests/unit/robot.

How do I install this agent skill?

npx skills add https://github.com/openvinotoolkit/physicalai --skill physicalai-runtime-adding-a-robot-integration
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides documentation and guidelines for implementing robot hardware integrations. It includes explicit security requirements for developers to validate user inputs and avoid unsafe command execution.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Adding a Robot Integration

Robots satisfy the structural Robot protocol in src/physicalai/robot/interface.py — no base class inheritance required. References: src/physicalai/robot/so101/, src/physicalai/robot/trossen/ (WidowX). Connection helpers: src/physicalai/robot/connect.py; validation: src/physicalai/robot/verify.py.

Workflow

  1. Read references/robot-protocol.md and an existing integration (SO-101 for serial servos, WidowX for arms).
    • Done when: required methods and observation shape are listed.
  2. Implement connect lifecycle: idempotent connect(), disconnect(), is_connected().
  3. Observations: return a type exposing joint_positions, timestamp (time.monotonic()), optional sensor_data / images; implement state property when inference expects more than positions.
  4. Actions: send_action(action, *, goal_time=...) with action shape matching training data conventions; document joint order via joint_names.
  5. Optional extra in pyproject.toml (physicalai[so101], physicalai[trossen]); lazy-import vendor SDKs.
  6. Export public class from physicalai.robot when user-facing.
  7. Tests under tests/unit/robot/ with mocked hardware.
    • Done when: uv run pytest tests/unit/robot -k <name> passes.
  8. Verification CLI/docs — wire verify.py patterns if the robot supports automated checks.

Required checks

  • isinstance(robot, Robot) at runtime (@runtime_checkable protocol).
  • No action sent when disconnected.
  • Joint count and joint_names stay stable across connect/disconnect.
  • Security: validate user-supplied port/path strings; no shell invocation with unsanitized device paths.

References

  • references/robot-protocol.md
  • docs/explanation/robots.md

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/openvinotoolkit/physicalai/physicalai-runtime-adding-a-robot-integration">View physicalai-runtime-adding-a-robot-integration on skillZs</a>