rekep-robot-onboarding

Integrates a new ReKep robot backend into PhyAgentOS by analyzing the SDK and updating adapters, factories, docs, runtime wiring, deployment steps with preflight/dry-run checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Integrates a new ReKep robot backend into PhyAgentOS by analyzing the user-provided SDK and updating the adapter, factory wiring, and documentation, finishing with deployment and startup guidance.

Core Features & Use Cases

  • Keep robot runtime work inside the external ReKep plugin repository, not the PhyAgentOS core.
  • Read the SDK dropped into the plugin runtime and adapt it for PhyAgentOS.
  • Implement or update the adapter, factory wiring, docs, and usage guide, with safe validation before motion.
  • Support dry-run or preflight checks prior to real hardware execution.

Quick Start

Resolve the ReKep plugin checkout, locate and inspect the SDK, and implement or update the adapter, factory, docs, and deployment steps.

Frequently Asked Questions about rekep-robot-onboarding

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

FAQPage Schema
How do I onboard a new ReKep robot backend into PhyAgentOS?

To onboard a ReKep robot into PhyAgentOS, the system analyzes your provided SDK to update adapters, factory wiring, and documentation, finishing with guided deployment and startup instructions.

How does runtime wiring work when integrating an SDK with a robot plugin?

Runtime wiring connects your SDK by updating adapter factories and runtime files inside the ReKep plugin repository, ensuring syntax checks pass before completing the robot integration.

Can I run preflight checks before executing real hardware motion on a newly onboarded robot?

Yes, the onboarding process supports dry-run and preflight checks to safely validate adapter wiring and runtime configurations prior to real hardware execution.

Do I need to modify PhyAgentOS core files to add a new robot adapter?

No, robot runtime work is kept inside the external ReKep plugin repository, not the PhyAgentOS core, keeping your adapter factory and deployment updates isolated.

What is the best way to deploy a robot SDK adapter after updating the factory wiring?

Deployment follows safe validation by resolving the ReKep plugin checkout, running syntax checks on updated runtime files, and delivering startup guidance with preflight verification.

Why does my ReKep robot integration fail during adapter factory creation?

Integration failures during adapter creation often stem from invalid SDK placement, unresolved plugin checkout targets, or syntax errors in the updated runtime files.