URDF robot description authoring and validation
Author and validate URDF robot descriptions — frame semantics, inertials, mesh references, cadgen validator
- What
- Author and validate URDF robot descriptions — frame semantics, inertials, mesh references, cadgen validator
- Cost
- Free
- Needs
- Python with pip; the skill's requirements.txt installed with the active interpreter; Chromium via Playwright for snapshots; existing dimensioned drawings, measured values or CAD data for the robot (never guess spatial transforms)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @earthtojake's URDF skill: treat robot descriptions as constrained kinematic modeling, not XML writing. Author the `.urdf` directly as the source of truth (no Python generation pipeline), open with a design ledger as a comment block (frames, joints, geometry, units, assumptions), get joint-origin/link-frame/joint-axis semantics exactly right, compute — never freehand — inertia tensors and derived numbers (closed-form formulas for primitives, throwaway helper scripts for mesh-derived values), validate every created or modified file with `cadgen urdf validate` (XML structure, tree topology, joint semantics including limits/mimic/dynamics, geometry, mesh references, materials, inertial physics; `--strict` and `--json` modes), snapshot robots to PNG for a joint-by-joint viewer sweep, and hand completed work to `$cad-viewer` when installed. Setup: pip install the skill's requirements.txt with the active interpreter; Chromium via Playwright for snapshots; `cadgen doctor` verifies the installed cadgen matches the skill's pin. Honest caveats: robots are authored in metres; link meshes must be present — an unhydrated Git LFS pointer fails validation; validation is a guardrail, not spatial proof — the ledger and viewer sweep exist for that; use the SRDF skill for MoveIt2 semantics and the CAD skill for STEP/STL outputs; listed here with credit to its creator; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: Python with pip; the skill's requirements.txt installed with the active interpreter; Chromium via Playwright for snapshots; existing dimensioned drawings, measured values or CAD data for the robot (never guess spatial transforms) Install "URDF robot description authoring and validation" for me. Treat URDF as constrained kinematic modeling: author the .urdf directly as the source of truth, open with a design ledger (frames, joints, geometry, units, assumptions), get joint-origin/link-frame/axis semantics exactly right, compute inertia tensors and derived numbers (never freehand), validate every file with cadgen urdf validate (structure, topology, joint semantics, geometry, meshes, materials, inertial physics), snapshot robots to PNG for a joint-by-joint viewer sweep, and hand completed work to $cad-viewer when installed. Repository: https://github.com/earthtojake/text-to-cad/blob/main/skills/urdf/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "urdf". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. pip install the skill's requirements.txt, install Chromium via Playwright, hydrate Git LFS mesh pointers, prepare the robot's dimensions and assumptions ledger). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.