clawperator-agent-orientation

To route an agent to the correct Clawperator front door, the system confirms host readiness and applies explicit device selection to direct the agent to a single surface among runtime skills, bundled-skills, MCP, or raw CLI.

The best way to onboard an unfamiliar agent is to run readiness checks and select one front door explicitly, ensuring the agent is directed to a single surface like runtime skills, MCP, or raw CLI without misrouting.

You need an agent orientation routing system when your host agent can access Clawperator but is uncertain which surface to use next, requiring routing decisions among runtime skills, bundled-skills, MCP, or raw CLI.

To start the onboarding process, run the doctor to verify readiness, identify devices, select one front door, and proceed with the smallest truthful probe to begin routing the agent to the correct surface.

Yes, the Clawperator orientation process enforces single-surface routing and ends by providing a canonical documentation link for the chosen path to unify the next steps for the agent.

Agents get misrouted when readiness checks are skipped or device selection is not explicit, which is why the orientation process enforces these checks before routing to any single surface.