placement-and-engagement — Claude Code skill: setup and use
The placement-and-engagement Claude Code skill plans and checks object placement, support, containment, and mechanical engagement from visible features. It applies when receiver stability or relative geometry shapes the requested result.
MIT ★ 488 updated 2026-11-15
npx skills add Open-RUA/uni-robot-agent --skill placement-and-engagement -a claude-codeWhat placement-and-engagement does
The skill guides an agent through placing objects and checking whether they rest on supports, fit inside a receiver, or engage with another part. It accounts for orientation, access to the receiving opening, and whether the receiver stays stable during transfer.
For an engagement, it calls for tracking relative progress and checking evidence of the endpoint. A shifted receiver changes the route, so its opening and support need another look before placement continues. Resistance alone does not prove that a part is seated or locked.
What it helps with
- check whether a part rests on its supports
- place a part inside a receiver without bridging its rim
- verify that an inserted part has reached the required position
- revise the placement route after the receiver shifts
Example prompts for the agent
- Place the part on its supports and check that it is no longer held by the gripper.
- Insert this part into the opening, then verify its position after withdrawing the gripper.
- Join these parts and check whether the required engagement is complete.
How to install placement-and-engagement
1Skills CLI (Vercel)
npx skills add Open-RUA/uni-robot-agent --skill placement-and-engagement -a claude-code2Manually: put the files in place
~/.claude/skills/placement-and-engagement/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/placement-and-engagement/
1Skills CLI (Vercel)
npx skills add Open-RUA/uni-robot-agent --skill placement-and-engagement -a codex2Manually: put the files in place
.agents/skills/placement-and-engagement/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Open-RUA/uni-robot-agent --skill placement-and-engagement -a cursor2Manually: put the files in place
.cursor/skills/placement-and-engagement/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Open-RUA/uni-robot-agent uni_robot_agent/resources/skills/general/gripper/placement-and-engagement2Manually: put the files in place
.github/skills/placement-and-engagement/SKILL.md1Skills CLI (Vercel)
npx skills add Open-RUA/uni-robot-agent --skill placement-and-engagement -a gemini-cli2Platform CLI
gemini skills install https://github.com/Open-RUA/uni-robot-agent --path uni_robot_agent/resources/skills/general/gripper/placement-and-engagementManually: put the files in place
.devin/skills/placement-and-engagement/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about placement-and-engagement
How do I install placement-and-engagement in Claude Code?
Run npx skills add Open-RUA/uni-robot-agent --skill placement-and-engagement -a claude-code. The skill file is placed at ~/.claude/skills/placement-and-engagement/SKILL.md.
What does placement-and-engagement do?
It guides an agent in planning and checking object support, containment, nesting, placement, and mechanical engagement using visible features.
How does the skill check whether a part is fully engaged?
It tracks relative progress, such as a changing gap, exposed length, or angle, and checks evidence for the endpoint. Resistance alone is not proof that the part has seated or locked.
Source text
SKILL.md · MIT
--- name: placement-and-engagement description: Plan and verify support, containment, nesting or mechanical engagement from visible object features. Use when receiver stability, access or relative geometry determines the requested relationship. --- # Verify the requested relationship between objects Use `general/SKILL.md` for acquisition, transport and withdrawal. Identify the required support, containment, engagement or alignment. Use `general/gripper/state-verification/SKILL.md` for unresolved relationship evidence and `general/gripper/contact-effect/SKILL.md` to diagnose an entry probe. ## Preserve reference features and access For a goal defined by an initial arrangement, record the destination references before moving those objects. Keep that reference separate from current contact coordinates. Distinguish position, orientation and support requirements; do not add a preferred orientation when the instruction leaves it unconstrained. Choose visible features that distinguish the required orientation. An undirected long axis cannot distinguish opposite ends of an asymmetric part. Image slope alone is not world yaw; use calibrated geometry when numerical correction is needed. Inspect the object after reorientation because it can shift in the grip. ## Preserve the receiver through acquisition and transport Before acquiring the next object, confirm its receiver will remain stable, reachable and accessible through the transfer. Choose from observed behavior and the expected contact, rather than assuming every container needs two hands: - Stable receiver and clear entry: place directly using its existing support. - Sliding, rotation or tipping during contact, or expected contact that requires restraint: consider an available assisting hand or another stable support. - Blocked opening or inaccessible interior: revise the approach, clear an obstructing lid when permitted, or reposition the receiver before loading it. If the working hand already holds a load, assess whether the free hand can prepare the receiver while preserving that hold. Read `general/gripper/supported-contact/SKILL.md` for adjustment or restraint. Holding an inaccessible receiver still does not make the route feasible. Assign the assisting hand's role before pickup and preserve its existing support responsibilities. Do not park it away or leave the receiver on moving support without a viable plan. Use `general/gripper/supported-contact/SKILL.md` to establish restraint without blocking entry; simultaneous motion of both hands is optional. If the receiver moves, pause motion that depends on its old geometry. Recheck its opening, floor, orientation and affected contents, then update the entry and placement route. A held object's accurate world position does not establish its position inside a displaced receiver. Restore a usable destination before continuing. Use `general/gripper/handover/SKILL.md` for hand-to-hand support transfer and `general/gripper/held-object-geometry/SKILL.md` for the load's actual clearance. ## Build support and containment - Keep a stable, reachable base when it already serves the next placement. For a spanning part, establish its supports before adding that load. After release, check that it actually rests on those supports rather than leaning against them or remaining supported by the hand. - For nesting, align the actual receiving opening and the held part's rim or axis. Inspect tilt and edge contact; overlapping silhouettes do not establish that one part seated inside the other. - For containment, check the whole object's position after withdrawal. A part can bridge a rim, protrude through an opening or be drawn back out by a finger. Leave room for subsequent entries and withdrawal before committing placement. ## Establish engagement before advancing Identify the entering feature and the receiving aperture, including their axes or planes. Keep the grasp clear of those features and the receiver stable. Choose alignment precision from their actual clearance. When observed alignment supports a bounded entry probe, test entry instead of repeatedly refining the same coordinates. If an edge catches or motion stalls, retract clear before correcting the mismatch; do not rotate while wedged or push deeper unchanged. For turning after entry, preserve axis alignment, grip and receiver support. Use controlled segments and inspect relative part motion; grasp-site rotation alone does not establish advancement. If regrasping is needed, preserve the assembly's support first. A rotation about the grasp site can sweep an offset contact feature; use the held-object geometry and motion-recovery references when this matters. ## Continue engagement until the required relation is established After initial engagement, choose an observable relative progress measure and an end condition appropriate to the goal. Depending on the mechanism, useful evidence includes remaining gap, exposed length, relative angle, seating surfaces or a visible latch state. Initial entry is not full seating; resistance alone can mean an edge catch, obstruction or misalignment rather than the endpoint. Choose contact checkpoints by a possible change in engagement, support, progress or proximity to the endpoint. A small commanded increment alone does not require remeasuring all geometry. At the checkpoint, inspect relative progress and the end condition using existing images first; obtain new evidence only where needed. - Engagement maintained, progress observed, endpoint not reached: continue the effective operation in controlled segments while support and clearance hold. - Engagement lost: restore alignment and control before further advancement. - No progress: diagnose offset, tilt, slipping grip, obstruction or moving receiver; change the supported hypothesis instead of repeating more force. - Endpoint supported by evidence: release when support permits, withdraw clear and verify the required relation without disturbing it. Hand travel or resistance alone does not prove seating, tightening or locking. For example, while engagement holds and the gap visibly narrows, continue a bounded segment without resegmenting both parts. Shorten it near seating or a changed response; check an ambiguous endpoint. Reuse approaches only where the new parts' geometry is compatible. Do not infer unobserved torque or locking. When withdrawal is required before reorientation, use separate `move` calls and verify withdrawal before turning. A single pose target starts translation and rotation together. Free-space transport may combine them when the observed clearance and load permit it.
© Open-RUA · MIT · Open-RUA/uni-robot-agent