Perceiving Deformable Linear Objects logo

Perceiving Deformable Linear Objects

Organization
graph-robots
perceiving-deformable-linear-objects

Read a cable's ordered 3D centreline from one RGB-D frame and keep it current across a task — seed it from an unobstructed survey, re-fit it cold whenever the whole rod is in view, and fall back to tracking the carried prior only when the fresh fit comes back short. Use when a manipulation loop needs the current shape of a deformable linear object (a cable, rope, or hose) once per step rather than every frame, from a fixed third-person camera.

Overview

Publishergraph-robots
Repositoryopen-robot-skills
Skill nameperceiving-deformable-linear-objects
Stars
58
Forks
8
Bundled files
1
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by graph-robots on GitHub. Read the source before you install it.

Installation

Install the Perceiving Deformable Linear Objects AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/graph-robots/open-robot-skills/tree/main/skills/perceiving-deformable-linear-objects
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/graph-robots/open-robot-skills.git /tmp/open-robot-skills
mkdir -p .claude/skills
cp -r /tmp/open-robot-skills/skills/perceiving-deformable-linear-objects .claude/skills/perceiving-deformable-linear-objects
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Perceiving Deformable Linear Objects in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Perceiving Deformable Linear Objects on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Perceiving Deformable Linear Objects is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

perceiving-deformable-linear-objects

Read the cable's centreline once per step, and carry it through the loop as text.

Why this is its own skill

A rigid object is perceived once and then transformed; a cable has no pose, only a shape, and the shape changes every time a crossing moves it. The thing a routing loop needs is therefore an ordered 3D centreline — 42 nodes in arc-length order, not a bounding box and not a principal axis — and a rule for when to trust a fresh reading of it over the one it already has. That rule is the skill: a cold fit has no history and is the better estimate whenever the whole rod is in frame; a tracker is the better estimate only when it is not. Which case a frame is in is measurable (length against the prior) and the script routes on it.

Measured over eight arm poses from a bench camera pitched 55 degrees off the vertical, scored against the rod's own bodies:

estimatemedianp90max
cold fit per frame6.7 mm8.4 mm9.3 mm
tracked from the prior9.0 mm9.7 mm9.9 mm

The tracker is the worse estimate when nothing is hidden, and monotonically so across passes (7.6, 8.6, 9.2, 9.6, 9.6, 9.9 mm): each pass drags the prior along instead of carrying a hidden stretch through. It is still the right fallback, because the cold fit's own failure is sharp rather than gradual — a skeleton broken by the arm merges to one fragment, measured at 338 mm of a 488 mm rod (0.69), while honest fits ran 0.99–1.06 of the truth. The whole_rod gate (0.80) sits between those two populations.

When to use

  • A loop needs the current shape of a cable, rope, or hose once per station or per step, and the shape only changes when the robot moves it.
  • A fixed third-person RGB-D camera can be placed where it sees the whole object. Measured: an eye-in-hand camera frames a fifth of the cable at best, and an A/B over three episodes came out identical (0.667 mean) — the move it costs buys nothing. Pitch the camera off the vertical: overhead, the hand covered the rod exactly when the rod was moving (28 of 42 nodes visible, 60 mm RMS); at 55 degrees it sees 41 of 42 and fits at 6.7 mm.

When NOT to use

  • Every-frame tracking during a motion. This skill spends one detector call and one fit per read; call it between motions, not inside one.
  • Rigid, linear parts (a shaft, a handle) — fit an axis with geometry.fit_linear_feature instead.

State flow

text
prior == "" or index == 0 ──► seed from scene.rod ──► found (seeded)
           │ no seed
           ▼
prior == "" ──► cold fit every mask candidate, take the THINNEST ──► found (initialised) | lost
           │ prior present
           ▼
for camera in (chosen, track_camera, init_camera):
    cold fit ──► length ≥ whole_rod × len(prior)? ──► found (refit)
    else track prior onto the frame ──► ≥ min_visible nodes seen? ──► found (tracked)
nothing improved ──► found (held; rod == prior)
  1. Seeded. On the first pass (index == 0) — or whenever there is no prior — the survey's rod (the scene JSON's rod key, from perceiving-routing-fixtures) is returned as the model. The model must be born from an unobstructed view of the whole object, and that view exists exactly once per episode, before the first move; re-fitting after the hand has parked over the first station read 381 mm of a 500 mm rod.
  2. Initialised. With no prior and no seed, the bench camera is read, up to mask_candidates masks are fitted, and the thinnest plausible one wins. The top-scoring mask is not always the cable: on a grey bench with white arms a prompt sometimes returns the rod merged with an arm, scored confidently — measured on a 700 mm rod as 963 and 983 mm seeds on two of six episodes, both of which failed. Radius (mask area over centreline length) separates them where score cannot; max_rod_radius (12 mm) is the ceiling.
  3. Refit. The look's camera is tried first, then track_camera, then init_camera. A fresh fit whose arclength reaches whole_rod of the prior's is taken as is.
  4. Tracked. A short fit hands the frame to curve.track_centerline, which moves the prior's nodes by what the frame says about each and carries the unanswered ones on the displacement field of their visible neighbours. The update is believed only when at least min_visible nodes (6, about 70 mm of a 500 mm rod) had real correspondence — a tracker that accepted every frame would walk the model onto whatever happened to be visible.
  5. Held. Nothing improved on the prior; it is handed back unchanged.

Inputs

  • prior — the centreline the loop carries, as JSON text; empty on a cold start. The graph binds it to the latest rod written upstream (the survey's on the first pass, this skill's own afterwards).
  • scene — the survey JSON from perceiving-routing-fixtures; only its rod is read here.
  • camera — the camera the look chose for this pass (empty: the bench camera).
  • index — the pass number; 0 is the pass before the first move.
  • Bench constants as parameters with the measured defaults: init_camera and track_camera ("cable"), rod_query ("thin white cable"), rod_score (0.20), whole_rod (0.80), min_visible (6), max_rod_radius (0.012), curve_nodes (42), mask_candidates (4).

Outputs

  • rod — the centreline as JSON text: the points of a Centerline, an ordered list of [x, y, z] metres at 0.01 mm precision. It is passed as text so it round-trips through a loop unchanged (json.loads gives the list; a JSON Centerline object with a points key is also accepted on the way in). On held and lost it is the prior that was given ("null" when there was none), so a pass never binds a worse model than it had.
  • arclength_m, source (seeded | initialised | refit | tracked | held | no-camera | no-mask | no-fit), camera (which view carried this update), visible (nodes with real correspondence; the node count for a fit).

The router field is route. A node that raises binds no outputs, so the next reader of rod falls back to whatever was written before it.

Required end states

End stateMeaning
foundrod carries a centreline (see source for how it was earned).
lostNo model could be born and there was no prior to hold.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Perceiving Deformable Linear Objects AI skill do?

Read a cable's ordered 3D centreline from one RGB-D frame and keep it current across a task — seed it from an unobstructed survey, re-fit it cold whenever the whole rod is in view, and fall back to tracking the carried prior only when the fresh fit comes back short. Use when a manipulation loop needs the current shape of a deformable linear object (a cable, rope, or hose) once per step rather than every frame, from a fixed third-person camera.

Why use Perceiving Deformable Linear Objects on TypingMind?

Because you install it once and use it with any model. Perceiving Deformable Linear Objects is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Perceiving Deformable Linear Objects in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/graph-robots/open-robot-skills/tree/main/skills/perceiving-deformable-linear-objects. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Perceiving Deformable Linear Objects?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Perceiving Deformable Linear Objects?

As many as you like. As long as a model supports skills, you can use Perceiving Deformable Linear Objects with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Perceiving Deformable Linear Objects AI skill free?

Yes. It is published on GitHub by graph-robots under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇