Grasping Direct Ik logo

Grasping Direct Ik

Organization
graph-robots
grasping-direct-ik

Direct IK align-then-descend grasping. The gripper pre-rotates to the grasp orientation at a safe height ABOVE the target before descending straight down, avoiding the twist-while-closing failure mode of a blended rotate+descend. The grasp rotation is rebuilt so the hand's declared closing axis (robot.describe_gripper, composed by robot.grasp_frame) closes across the target's short horizontal axis, and the hover clearance is the hand's own (robot.describe_workspace) unless the workflow pins it. Use when no trajectory planner (curobo) is deployed or the scene is uncluttered enough that a straight-line approach is safe.

Overview

Publishergraph-robots
Repositoryopen-robot-skills
Skill namegrasping-direct-ik
Stars
58
Forks
8
Bundled files
5
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.

  • 5 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 Grasping Direct Ik 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/grasping-direct-ik
  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/grasping-direct-ik .claude/skills/grasping-direct-ik
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Grasping Direct Ik 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 Grasping Direct Ik 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 Grasping Direct Ik 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.

grasping-direct-ik

Direct-IK grasp: rotate the gripper to grasp orientation at a safe height above the target, then descend straight down, then close. No trajectory planner — works on platforms where CuRobo is not deployed, or in uncluttered scenes where planning is overkill.

Nothing here is written for one hand. The grasp rotation is composed by the connector's robot.grasp_frame from the hand's measured approach and closing axes, the fingertip floor and the hover clearance come from robot.describe_gripper / robot.describe_workspace, so the same subgraph grasps the same way on a hand that closes along tool-local x and on one that closes along tool-local y.

When to use

  • The curobo tool bundle is not deployed (no collision-aware planner available).
  • The scene is uncluttered enough that a straight-line approach is safe.

When NOT to use

  • Cluttered scenes where the arm must thread between obstacles. Prefer grasping-with-planner if available.

Recommended subgraph state flow

The subgraph state machine the agent generates should look like (7 states):

text
open → compute_grasp → refine_grasp → compute_align → rotate_align → descend → close → grasped

(grasped is the success-marker noop from sg.add_exit("grasped"), with an edge to END.)

State details:

  1. open — type: tool, tool: "robot.open_gripper", inputs: { settle_steps: 40 }.

  2. compute_grasp — type: tool, tool: "geometry.top_down_grasp_candidates", inputs: { obb: Ref("in.target_obb") }.

  3. refine_grasp — type: script, file scripts/<sg>/refine_top_down_grasp.py (from this bundle's canonical_scripts). Inputs: grasp_pose = Ref("compute_grasp.candidates.poses.0"), target_obb = Ref("in.target_obb"). Returns grasp_pose: the candidate with its rotation rebuilt so this hand's closing axis lies across the OBB's short horizontal axis (robot.describe_gripper + robot.grasp_frame(approach=-z, close_heading_deg)), and its Z raised to the fingertip floor (support_z + finger.reach_m + finger.clearance_m) when the hand states its finger envelope. Keep this state: the candidate fan is world-aligned and a thin object's centred grasp jams the jaws on the table without the floor.

  4. compute_align — type: script, file scripts/<sg>/compute_align_pose.py. Inputs: grasp_pose = Ref("refine_grasp.grasp_pose"), target_obb = Ref("in.target_obb"), optionally clearance (a literal in metres). Returns align_pose at the grasp XY and rotation, with z = max(obb_top, grasp_z) + clearance. Omit clearance (or pass 0) and the script asks robot.describe_workspace for align_clearance_m — the hand's own envelope above the fingertips. Pin it (e.g. 0.12) when the held object is what needs the room, such as a long tool that will hang below the fingertips on the way up.

  5. rotate_align — type: tool, tool: "robot.go_to_pose", inputs: { pose: Ref("compute_align.align_pose") }.

  6. descend — type: tool, tool: "robot.go_to_pose", inputs: { pose: Ref("refine_grasp.grasp_pose") } — the same pose compute_align was given, so hover and grasp share one rotation.

  7. close — type: tool, tool: "robot.close_gripper", inputs: { settle_steps: 60 }. Edge directly from close to the grasped success marker; the subgraph's on_error: "failed" catches any raise from earlier steps. Whether the gripper actually closed on the object is checked by the target_held postcondition checkpoint (see ## Checkpoints), NOT by a re-check-and-raise node (none such exists).

    json
    "edges": [ ..., ["close", "grasped"], ["grasped", "END"] ],
    "conditional_edges": {},
    "exit": { "router_field": null, "success_values": ["grasped"] },
    "on_error": "failed"

    The lift onto a safe carry height is handled by the next transporting-objects subgraph (its waypoint_move script lifts before lateral motion); do NOT add a lift step here.

scripts/<sg>/plan_to_pose.py is the optional planned variant of a single leg: it calls curobo.plan_to_pose from the observation's joint state to a target pose and returns the trajectory (raising PlanningFailed when the planner refuses) for a platform that deploys CuRobo as a fast single-pose IK fallback without the goalset grasp planner.

Hard rules

  1. Use geometry.top_down_grasp_candidates (returns candidates: {poses: list[Se3Pose]}), not geometry.top_down_grasp_from_obb (single bare pose). The refine and align-pose constructions assume compute_grasp.candidates.poses.0 exists.
  2. The align_pose descends straight down with the gripper pre-rotated. Do NOT skip the compute_align + rotate_align states — a direct robot.go_to_pose to the grasp pose blends rotation and descent and twists the gripper against the object.
  3. descend uses the pose compute_align was given (refine_grasp.grasp_pose). Never descend to the raw candidate after hovering at the refined rotation.

Required end states

End stateMeaning
graspedGripper has closed on the object after the descend. Route to next subgraph (typically transporting-objects).
failedAny grasp-attempt failure: planning failure or trajectory execution error (a raise to on_error). Coordinator routes to abort. Lives only in on_error — never declare a failed node.

See also

  • references/design_align_then_descend.md — why pre-rotate-then-descend beats blended rotate+descend.
  • scripts/refine_top_down_grasp.py — the close-axis rotation and fingertip floor, read off the live hand.
  • scripts/compute_align_pose.py — the canonical align-pose construction.
  • scripts/plan_to_pose.py — the optional CuRobo single-pose leg.

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 Grasping Direct Ik AI skill do?

Direct IK align-then-descend grasping. The gripper pre-rotates to the grasp orientation at a safe height ABOVE the target before descending straight down, avoiding the twist-while-closing failure mode of a blended rotate+descend. The grasp rotation is rebuilt so the hand's declared closing axis (robot.describe_gripper, composed by robot.grasp_frame) closes across the target's short horizontal axis, and the hover clearance is the hand's own (robot.describe_workspace) unless the workflow pins it. Use when no trajectory planner (curobo) is deployed or the scene is uncluttered enough that a str...

Why use Grasping Direct Ik on TypingMind?

Because you install it once and use it with any model. Grasping Direct Ik 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 Grasping Direct Ik in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/graph-robots/open-robot-skills/tree/main/skills/grasping-direct-ik. 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 Grasping Direct Ik?

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 Grasping Direct Ik?

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

Is the Grasping Direct Ik 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 👇