Perceiving Next Item logo

Perceiving Next Item

Organization
graph-robots
perceiving-next-item

Loop-head perception for pack-all / clean-all-items tasks. From ONE observation it localizes BOTH the destination container (basket, bin, box) AND the next remaining target item, using the pairwise VLM crop tournament with a container-excluding description so the target is never confused with the basket, then makes a clean found / none decision: an item was found (grasp it) or only the container remains (all items packed — exit the loop to done). Use when a workflow must pick up EVERY object and place each into a container in a loop (pack-all / clean-all-items) and each pass must reliably answer "is there still a graspable item, or are we done?" while also exposing a fresh container OBB for the downstream place. This subgraph is self-contained and takes NO inputs (inputs: {}); the container and item phrases are literal strings written inside the perception nodes, never subgraph parameters — do not declare item_name / container_name / item_description as subgraph inputs.

Overview

Publishergraph-robots
Repositoryopen-robot-skills
Skill nameperceiving-next-item
Stars
58
Forks
8
Bundled files
7
LicenseMIT
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.

  • 7 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 Next Item 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-next-item
  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-next-item .claude/skills/perceiving-next-item
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Perceiving Next Item 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 Next Item 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 Next Item 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-next-item

The repeating head of a pack-all loop. One robot.get_observation feeds two perceptions — the destination container and the next remaining item — and a decide router turns the item verdict into the loop's continue/terminate signal. It is perceiving-objects (the reliable pairwise-tournament perception) composed with (a) a second perception for the container and (b) a clean none exit, so a "pick up every object and place it in the basket" workflow has one subgraph that answers "is there still an item, and where is the basket?" every pass.

Detection uses the same pairwise VLM crop tournament as perceiving-objects (~30% → 97% object-ID over a one-shot Set-of-Marks pick on the LIBERO-PosVar study). The clean loop terminator comes from the item's container-excluding object_description: once only the basket remains, the tournament + verify gate answer "no grocery item", perceive_item returns found=False, and the decide router emits none → the loop exits to done.

When to use

  • The repeating head of a pack-all / clean-all-items loop (transport routes its success edge back here), where each pass must reliably decide "grasp the next item" vs "everything is packed, stop".
  • When the downstream place needs a fresh container OBB every pass (this skill emits container_obb/container_mask/container_cloud alongside the target).

When NOT to use

  • Single pick-and-place (grab ONE named object). Use perceiving-objects (one target, no loop, no container co-perception).
  • You want the container localized once, out of the loop. If the container never moves and you prefer to perceive it a single time before the loop, use a plain perceiving-objects subgraph for the basket + perceiving-objects-oneshot for the looping target. This skill deliberately re-localizes both each pass (robust to a nudged basket, one observation, one clean none).
  • Cluttered scenes with look-alike distractors. Prefer perceiving-objects for the target identity — its pairwise-tournament plus object_description hints disambiguate look-alikes (it lacks the clean loop none, so you would add your own decide).

vs. perceiving-objects-oneshot

oneshot also has a clean not_found loop terminator, but it identifies with a single Set-of-Marks VLM pick (weaker on small/similar items) and perceives only the target (no container). This skill uses the pairwise tournament and co-localizes the container, so both the "is anything left?" decision and the downstream place are more reliable — at the cost of a second perception per pass.

Recommended subgraph state flow

text
observe → exterior_view → perceive_container → filter_obb_container
        → perceive_item → decide ──found──▶ filter_obb_item ──▶ found
                                └──none──▶ none

See examples/canonical_subgraph.json for the exact node/edge/output wiring — emit it verbatim, adapting only the object_name/object_description literals to the task's items and container.

State details:

  1. observe — type: tool, robot.get_observation, inputs: {}.
  2. exterior_view — type: script, scripts/<sg>/exterior_view.py, inputs: {cameras: Ref("observe.cameras")}. Drops the wrist cam so the container OBB is not bloated by the angled eye-in-hand view.
  3. perceive_container — type: script, scripts/<sg>/perceive_dino_vlm.py, inputs: {cameras: Ref("exterior_view.cameras"), object_name: "basket"}.
  4. filter_obb_container — type: tool, geometry.filter_and_compute_obb, inputs: {points: Ref("perceive_container.cloud")}.
  5. perceive_item — type: script, scripts/<sg>/perceive_dino_vlm.py, inputs: {cameras: Ref("observe.cameras"), object_name: "grocery item", object_description: "…never the wicker basket…"} (the exclusion is a HARD rule above). For SUBSET tasks (specific items only), add reject_unverified: True and name exactly the allowed items in the literals — see the subset-scoping HARD rule.
  6. decide — type: router, scripts/<sg>/decide_next_item.py, inputs: {found: Ref("perceive_item.found"), cloud: Ref("perceive_item.cloud"), container_obb: Ref("filter_obb_container.obb")}. Maps found → filter_obb_item, none → none.
  7. filter_obb_item — type: tool, geometry.filter_and_compute_obb, inputs: {points: Ref("perceive_item.cloud")}.

Wiring the exit (HARD)

python
sg.add_exit("found")
sg.add_exit("none")
sg.set_exit(success_values=["found", "none"])   # BOTH are clean exits
sg.set_on_error("perception_failed")

sg.set_outputs(
    target_obb=Ref("filter_obb_item.obb"),
    target_mask=Ref("perceive_item.mask"),
    container_obb=Ref("filter_obb_container.obb"),
    container_mask=Ref("perceive_container.mask"),
    container_cloud=Ref("perceive_container.cloud"),
)

At the top level, route this subgraph's found → grasp, none → done, perception_failed → abort.

Required end states

End stateMeaning
foundA graspable item distinct from the container was localized. Route to a grasp skill.
noneOnly the container remains — all items packed. Route to done (a success, not an abort).
perception_failedUnexpected perception error (not "nothing left" — that is none). Route to abort. Lives only in on_error.

See also

  • scripts/perceive_dino_vlm.py — the pairwise-tournament perception (shared with perceiving-objects).
  • scripts/decide_next_item.py — the unprivileged loop router: per-pass VLM all-packed check (primary stop) + same-target no-progress guard + perception verdict; sim.check_success is telemetry only (GAP_DECIDE_TRUST_ENV=1 opts into trusting it on benchmarks).
  • scripts/exterior_view.py — wrist-cam drop for a clean container OBB.
  • prompts/vlm_pairwise.md — the pairwise-tournament VLM prompt template.

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 Next Item AI skill do?

Loop-head perception for pack-all / clean-all-items tasks. From ONE observation it localizes BOTH the destination container (basket, bin, box) AND the next remaining target item, using the pairwise VLM crop tournament with a container-excluding description so the target is never confused with the basket, then makes a clean found / none decision: an item was found (grasp it) or only the container remains (all items packed — exit the loop to done). Use when a workflow must pick up EVERY object and place each into a container in a loop (pack-all / clean-all-items) and each pass must reliably a...

Why use Perceiving Next Item on TypingMind?

Because you install it once and use it with any model. Perceiving Next Item 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 Next Item in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/graph-robots/open-robot-skills/tree/main/skills/perceiving-next-item. 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 Next Item?

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 Next Item?

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

Is the Perceiving Next Item AI skill free?

Yes. It is published on GitHub by graph-robots under the MIT 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 👇