Robodk Post Processor Builder
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
Install
npx skills add RoboDK/RoboDK-Agent-Skills --skill robodk-post-processor-buildergit 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-post-processor-builder ~/.claude/skills/robodk-post-processor-builderPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# RoboDK Post Processors
A post processor is the translation layer between RoboDK's simulation and a physical
controller. Get it wrong and a real robot executes wrong motion — so favour reading the
target controller's actual syntax over guessing, and verify by regenerating a program and
diffing it (see **Verify**, below).
## The pipeline
```
RoboDK program
│ RoboDK flattens the program into an ordered list of API calls
▼
PostProg<Name>.py ← "intermediate file": plain Python, imports your post,
│ instantiates RobotPost(), calls methods in execution order,
│ ends with r.ProgSave(folder, progname, ...)
▼
<YourPost>.py ← the post processor: each method appends controller
│ source lines to self.PROG
▼
Prog.<PROG_EXT> ← the controller program that gets loaded onto the robot
```
Two consequences worth internalising:
1. **The post is a transcriber, not a planner.** RoboDK has already solved the kinematics.
Every motion call arrives with joint values already computed, and usually the cartesian
pose too. Never re-solve kinematics, re-order motion, or "improve" the trajectory.
2. **The intermediate file is a complete, runnable test harness.** If the user has one
(`PostProg*.py`), you can replay it against a modified post and diff the output against
a known-good controller program. This turns post editing from guesswork into aDetails
- Skill name
robodk-post-processor-builder- Repository
- RoboDK/RoboDK-Agent-Skills
- Path
skills/robodk-post-processor-builder/SKILL.md- License
- MIT
- Repo updated
- 6 October 2026
FAQ
What does the Robodk Post Processor Builder skill do?
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
How do I install the Robodk Post Processor Builder skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add RoboDK/RoboDK-Agent-Skills --skill robodk-post-processor-builder. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Robodk Post Processor Builder 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 API
9RoboDK/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.
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 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
Finding Unknowns
9sidneyswift/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.
Spec Goals
9sidneyswift/skills
Use when someone asks 'help me write a /goal', 'turn this into a goal', 'draft a goal for Codex', 'spec this for /goal', 'is this a good goal', or 'sharpen this objective'. Turns a defined, durable objective into a ready-to-paste Codex `/goal` with a measurable outcome, verification surface, constraints, boundaries, iteration policy, and blocked-stop condition. If the outcome, evidence, constraints, or approach still contains load-bearing unknowns, use flex-finding-unknowns first. Do NOT use this skill to execute the work.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.