Robodk Addin
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
Install
npx skills add RoboDK/RoboDK-Agent-Skills --skill robodk-addingit 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-addin ~/.claude/skills/robodk-addinPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Building RoboDK Add-ins A RoboDK Add-in (an "App") is a folder that RoboDK turns into UI. Drop it in RoboDK's `Addins/` directory (RoboDK scans `Addins/` and `Apps/` as two separate roots — `Addins/` for a `manifest.xml`-based Add-in, the older `Apps/` for a [Classic App](references/appconfig.md) with no `manifest.xml`; put it in the wrong one and RoboDK loads it in the wrong mode) and every root-level Python script becomes a button in its own menu and toolbar; `AppConfig.ini` controls how each one appears and behaves. Zip the folder and it becomes an `.rdkp` package anyone can install. The whole system rests on a few conventions rather than a framework, so most problems are convention problems: a script in the wrong place, a `Checkable` flag that disagrees with the script body, a missing `runmain()`. Work through the structure below and use `scripts/robodk_addin.py check` to catch the rest. ## Anatomy
Details
- Skill name
robodk-addin- Repository
- RoboDK/RoboDK-Agent-Skills
- Path
skills/robodk-addin/SKILL.md- License
- MIT
- Repo updated
- 6 October 2026
FAQ
What does the Robodk Addin skill do?
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
How do I install the Robodk Addin skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add RoboDK/RoboDK-Agent-Skills --skill robodk-addin. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Robodk Addin popular?
It lives in RoboDK/RoboDK-Agent-Skills, which has 9 GitHub stars and 0 forks.
Related skills
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 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
Robodk Shape Builder
9RoboDK/RoboDK-Agent-Skills
Build parametric RoboDK visual components — primitives (box, sphere, cone), fixtures (table, pedestal, fence), and mechanisms (conveyor, linear rail, T-bot/H-bot gantry, 1/2/3-axis turntable/positioner) — using RoboDK's own bundled Components Add-in library instead of hand-rolled mesh geometry. Use whenever a station needs one of these shapes; prefer this over generating raw triangle meshes for anything it covers.
Solid Reviewer
9lvcoi/solidJSkills
Review SolidJS diffs for correctness, reactivity safety, SSR/hydration risk, and maintainability with deterministic severity ordering. Use when auditing PRs or producing final review findings.
Storyblok Build Frontend
9storyblok/agent-plugin
Use when generating frontend components for Storyblok blocks — writing, registering and validating the framework code that renders a space's content. E.g. "generate components for my blocks", "build an Astro + Storyblok landing page".
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.