Skip to main content
A skill is plain Python that drives your robot through GRID’s APIs. You develop it against a live robot in a generated notebook — no environment setup, because the CLI provisions the Python environment for you.

1. Open a dev session

Pick your robot, then choose Create a new skill. The CLI opens a VS Code workspace with a generated notebook whose first cell already holds the live connection:

2. Find out what your robot can do

connect() returns a RemoteRobot. Its attributes are the robot’s own methods, discovered live when you connect — so the fastest way to see the surface is to ask it:
Those methods come from the Robot interface, which is the same whether the robot is physical or simulated. A quadruped gets Quadruped, an arm gets Arm, and every robot gets the shared Robot methods like getState() and getImage().

3. Drive it

State, motion, and camera all work directly from notebook cells:
Motion cells move the robot physically. Make sure it has clearance, and run robot.shutdown() when you’re done — it releases the session cleanly.
Sensors, arms, and end effectors nest as attributes, so you can reach into a subcomponent the same way:

4. Add perception

Anything you capture can go straight to a hosted Cortex model. This finds a water bottle in the robot’s camera frame:
From there it’s ordinary Python — loop over frames, check a score threshold, and command the robot when you see what you’re looking for:

Where next