Robodk Driver Builder

Write, port, or debug a RoboDK robot driver — the standalone console program (Python script or compiled executable) that lets RoboDK move a real robot live over its own stdin/stdout protocol ("Online Programming"), as opposed to a post processor generating an offline program file. Use when asked to "write/add a driver for <robot>", "port this driver to another language", "the robot driver doesn't respond to <command>", "support live/online programming for a new robot", or when handed an existing driver file to fix or extend. Distinct from robodk-real-robot-control, which operates an already-wo

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add RoboDK/RoboDK-Agent-Skills --skill robodk-driver-builder
Manual install
git clone --depth 1 https://github.com/RoboDK/RoboDK-Agent-Skills.git /tmp/RoboDK-Agent-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/RoboDK-Agent-Skills/skills/robodk-driver-builder ~/.claude/skills/robodk-driver-builder

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# RoboDK Driver Builder

A robot driver is the piece that makes "Online Programming" possible: RoboDK launches it as a
child process and drives it over stdin/stdout using a small, fixed text protocol, and the driver
translates that into whatever the real robot controller actually speaks. This skill is about
**writing, porting, or debugging that program** — not about operating one against real hardware
(that's `robodk-real-robot-control`, with its own mandatory confirmation protocol) and not about
generating an offline program file (that's a post processor — `robodk-post-processor-builder`).

Full protocol reference, verified against four real shipped drivers in different
languages/styles (a Python SDK wrapper, a hand-rolled Python socket protocol, a compiled C++/Qt
driver, and a Python driver forwarding to the controller's own native command protocol):
**`references/driver-protocol.md`**. Read it before writing or auditing a driver — the
command/response line formats and the two-loop architecture are where correctness (and
therefore safety, once this runs against real hardware) actually lives.

## When to use this vs. the neighboring skills

- **This skill**: authoring a new driver, porting an existing one to another language, adding a
  command a driver doesn't yet handle, fixing a driver that misbehaves against RoboDK or against
  the standalone console test.
- **`robodk-real-robot-control`**: the driver already exists and works — now someone wants to actually
Read the full skill on GitHub

Details

Skill name
robodk-driver-builder
Path
skills/robodk-driver-builder/SKILL.md
License
MIT
Repo updated
6 October 2026

FAQ

What does the Robodk Driver Builder skill do?

Write, port, or debug a RoboDK robot driver — the standalone console program (Python script or compiled executable) that lets RoboDK move a real robot live over its own stdin/stdout protocol ("Online Programming"), as opposed to a post processor generating an offline program file. Use when asked to "write/add a driver for <robot>", "port this driver to another language", "the robot driver doesn't respond to <command>", "support live/online programming for a new robot", or when handed an existing driver file to fix or extend. Distinct from robodk-real-robot-control, which operates an already-wo

How do I install the Robodk Driver Builder skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add RoboDK/RoboDK-Agent-Skills --skill robodk-driver-builder. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Robodk Driver Builder popular?

It lives in RoboDK/RoboDK-Agent-Skills, which has 9 GitHub stars and 0 forks.

Related skills

Robodk Addin

9

RoboDK/RoboDK-Agent-Skills

Create, edit, validate, package, inspect and extract RoboDK Add-ins (also called RoboDK Apps) — a folder of Python action scripts plus AppConfig.ini that adds menus, toolbar buttons, context-menu entries and settings dialogs to RoboDK, distributed as an .rdkp package. Use this skill whenever the user mentions RoboDK add-ins, RoboDK apps, .rdkp files, AppConfig.ini, the AppLoader or Add-in Manager, roboapps/AppSettings, or wants to add a button, menu, toolbar action, right-click action or custom UI to RoboDK, package/unpack an .rdkp, inspect an existing Add-in, or automate a RoboDK workflow tha

Frontend & Design

Robodk API

9

RoboDK/RoboDK-Agent-Skills

Reference for writing, porting, or debugging application code against the RoboDK API — the Robolink/Item/Mat SDK for driving RoboDK from Python, TypeScript, C++, C#, MATLAB, C, or Visual Basic. Use when a user wants to write a script that connects to RoboDK, reads/writes item poses and joints, runs MoveJ/MoveL/MoveC, builds targets/frames/tools/programs, converts between Euler/pose conventions, or ports RoboDK API code from one language to another.

Software Development

Robodk Post Processor Builder

9

RoboDK/RoboDK-Agent-Skills

Read, write, debug, and extend RoboDK post processors — the Python files defining a `RobotPost` class (MoveJ/MoveL/MoveC/setFrame/setTool/setSpeed/setZoneData/setDO/waitDI/RunCode/RunMessage/ProgSave...) that translate a RoboDK simulation program into a real robot controller program. Use this skill whenever the user mentions RoboDK, post processors, "the post", a Posts folder, or generating/fixing robot controller code in any dialect (KRL .src, RAPID .mod, Fanuc .ls, Motoman .jbi, Siasun .spf, URScript, Kawasaki .as, G-code) — including indirect asks like "my robot program comes out wrong", "a

Software Development

Robodk Real Robot Control

9

RoboDK/RoboDK-Agent-Skills

The ONLY skill in this repo allowed to move a real, physical robot — via robot.Connect() and RUNMODE_RUN_ROBOT/PROGRAM_RUN_ON_ROBOT, using RoboDK's robot drivers (Online Programming). Every other RoboDK skill here is simulation-only by design; redirect here the moment a request is unambiguously about the real robot moving, not the simulated one — phrasings like "move the real robot", "run this on the actual/physical robot", "connect to the robot and jog it", "online programming", "drive the robot live". Do not use for anything that stays in simulation, for generating a program to transfer late

Software Development

Revolut X Public Market Data

9

revolut-engineering/revolut-agent-skills

Revolut X public market data — public order book (5 price levels) and latest 100 trades across all pairs. No authentication required. Use when the user wants a quick price check or recent trade data and has not configured API keys, or asks about public market data.

Software Development

Finding Unknowns

9

sidneyswift/skills

Surface the gaps between what a task description says and what the work actually requires, before writing code. Use before implementing anything ambiguous, large, or unfamiliar; when the user asks "what am I missing", wants options or design directions, needs a mock or plan to react to, wants to be interviewed about a spec, is porting from a reference implementation, or gives a vague creative request they lack vocabulary for. Make sure to use this skill whenever the map (prompt/spec) might not match the territory (codebase/real requirements) — even if the user does not say "unknowns.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.