Registering Held Objects logo

Registering Held Objects

Organization
graph-robots
registering-held-objects

Reobserves a grasped rigid object from the wrist cameras, estimates its functional feature in the TCP frame, and fits attached collision spheres, retaining the grasp-time transform at low confidence when the object is not seen. Use when a held object must be localized in the hand right after grasping or re-checked at a pre-contact pose before a fixture engagement.

Overview

Publishergraph-robots
Repositoryopen-robot-skills
Skill nameregistering-held-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 Registering Held 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/registering-held-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/registering-held-objects .claude/skills/registering-held-objects
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Registering Held 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 Registering Held 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 Registering Held 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.

registering-held-objects

cameras is a list of CameraFrame -- an Observation's cameras field. It is stated here rather than under required_inputs because the type registry names no bare list of frames.

Use immediately after grasping or again at a pre-contact pose. For pre-contact realignment, pass the prior feature-in-TCP and attachment: wrist views localize the functional feature directly, fit a loop's geometric center and plane rather than the centroid of its visible arc, and retain the collision model. Grasp-time geometry remains an explicit low-confidence fallback (registration_confidence == 0.25); the script does not raise for it, so a graph that must stop on a weak registration routes on the confidence.

How the feature is measured

  • A loop is segmented from functional_feature.description on every pass and its plane and circle centre are fitted. Only the minimum rotation that aligns the prior normal with the fitted normal is applied, so the in-plane roll of the prior (or grasp-time) frame is preserved: a circle has no observable roll and the fit's roll changes between cameras. The coordinate along the normal is the robust midpoint of the observed ring thickness.
  • A tip is segmented from object_description. With direction_marker_description set (a cap, a coloured band, a head) and both masks visible in the same wrist view, the tip is re-derived as the endpoint of the object's principal axis directed toward the marker; with a prior, the prior roll about that axis is preserved. Without a marker the cloud median is compared with the predicted feature centre.
  • With a prior, an observed centre more than 4 cm from the prediction is a mask on the gripper or background and is rejected (confidence 0.25).
  • On the first pass for non-loop features, an observed cloud whose 3D extent is outside 0.55--1.80 of the reference cloud's extent is rejected before it becomes an enormous attachment or clearance waypoint (confidence 0.25).

Grasp transform and attachment

  • grasp_pose (optional) is the commanded grasp TCP pose. When given, the reference cloud and the pre-grasp feature pose are carried by the rigid transform current-TCP · inv(grasp_pose), so the fallback feature-in-hand is inv(grasp_pose) · feature_world rather than inv(current TCP) · feature_world. Pass it whenever registration happens after a lift or a verification move.
  • attachment_source selects the cloud that bounds the collision model when no prior_attached_object is given: "reference" (default) fits the complete pre-grasp cloud, carried as above; "observed" fits the accepted wrist cloud, falling back to the carried reference cloud when the wrist saw nothing usable. object_in_tcp is centred on the same cloud.
  • The attachment is curobo.cloud_to_attachment(surface_radius=0.002, margin=0.002, max_spheres=64): 64 MORPHIT spheres on a watertight convex hull, radii contracted by 2 mm, fitted where cuRobo lives. An attachment_fit_type of surface or voxel goes to geometry.cloud_to_attachment instead, for explicit fitting experiments only.
  • camera_name_filter (default "eye_in_hand") is a substring the camera name must contain; set it to another camera name when a held object is better observed from an overview camera.

Object-specific refinement (CAD registration, per-object landmarks) is not part of this skill; a graph performs it in its own node and passes the result as prior_feature_in_tcp / prior_object_in_tcp.

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 Registering Held Objects AI skill do?

Reobserves a grasped rigid object from the wrist cameras, estimates its functional feature in the TCP frame, and fits attached collision spheres, retaining the grasp-time transform at low confidence when the object is not seen. Use when a held object must be localized in the hand right after grasping or re-checked at a pre-contact pose before a fixture engagement.

Why use Registering Held Objects on TypingMind?

Because you install it once and use it with any model. Registering Held 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 Registering Held Objects in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/graph-robots/open-robot-skills/tree/main/skills/registering-held-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 Registering Held 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 Registering Held Objects?

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

Is the Registering Held 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 👇