Robodk API
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.
Install
npx skills add RoboDK/RoboDK-Agent-Skills --skill robodk-apigit 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-api ~/.claude/skills/robodk-apiPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# RoboDK API Reference The RoboDK API is a multi-language SDK for controlling RoboDK: build/inspect stations, move robots in simulation, solve FK/IK, and generate vendor-specific robot programs. It talks to a running RoboDK instance over a TCP socket (default `localhost:20500`, line-based commands). Every supported language — Python, TypeScript, C++, C#, MATLAB, C, Visual Basic — independently re-implements the same wire protocol against the same three abstractions: - **`Robolink`** (`RoboDK` in C++/C#) — the session/connection object; entry point for station-level operations (open/save files, list items, run mode, collisions). - **`Item`** — any node in the station tree: robot, frame, tool, object, target, curve, program, instruction, camera, notes, ... - **`Mat`** — a 4×4 homogeneous transform representing a pose (position + orientation). **There is no code generation or shared source of truth between languages.** Each `/Python`, `/TypeScript`, `/C++`, `/C#`, `/Matlab`, `/C`, `/Visual Basic` folder in this repo hand-rolls the protocol independently. Naming is consistent across almost all of them (see below), but always verify a method/constant against the actual file for the language you're targeting — don't assume parity from the Python source alone. ## Which language, which file | Language | Entry point(s) | Notes | |---|---|---|
Details
- Skill name
robodk-api- Repository
- RoboDK/RoboDK-Agent-Skills
- Path
skills/robodk-api/SKILL.md- License
- MIT
- Repo updated
- 6 October 2026
FAQ
What does the Robodk API skill do?
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.
How do I install the Robodk API skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add RoboDK/RoboDK-Agent-Skills --skill robodk-api. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Robodk API popular?
It lives in RoboDK/RoboDK-Agent-Skills, which has 9 GitHub stars and 0 forks.
Related skills
Robodk Addin
9RoboDK/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
Robodk Driver Builder
9RoboDK/RoboDK-Agent-Skills
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
Robodk Post Processor Builder
9RoboDK/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
Revolut X Public Market Data
9revolut-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.
Revolut X Auth
9revolut-engineering/revolut-agent-skills
Revolut X API authentication setup, Ed25519 keypair generation, and request signing. Use when the user asks to set up Revolut X API access, configure API keys, generate an Ed25519 keypair, sign requests manually, or debug 401/403/409 authentication errors.
Robodk Real Robot Control
9RoboDK/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
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.