SKILLEMALL.ai

AC urdf

URDF robot description authoring and validation. Use when creating, editing, inspecting, validating, or debugging `.urdf` files, robot links, joints, limits, inertials, visual/collision geometry, mesh references, frame conventions, or robot-description artifacts. Use the SRDF skill for MoveIt2 semantic groups and IK/path-planning semantics; use the CAD skill for STEP/STL/3MF/DXF/GLB outputs. Open and visually review existing URDF files in CAD Viewer.

earthtojake/text-to-cad Agent Skills author: earthtojake MIT 10 files body ≈ 2 719 tokens Open the sourcegithub.com↗ analyzed 4 h ago

URDF robot description authoring and validation.

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
99
Quality 40%
89
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Concealment en-hide-from-user references/design-ledger.md:84
      Instruction to hide actions from the user (negated — the text forbids it)
      Do not silently copy visual origins into inertial origins. The visual frame, collision frame, link frame, and center of mass can all differ.
      negated

    Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 53/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 3 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
    • 100Steps. 27 steps
    • 100Failures and branches. 2 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2719 tokens
    • low The response is described with custom markup (4 tags): a typed call is more reliable

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +3Description length 454: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 27 items
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (7 of 7)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.