Individual skill

claim-agent-ownership

Orchestrator skill for resolving multi-daemon binding contention. Use when you (the orchestrator) detect an `agent.binding.contested` sync event indicating two daemons are racing for the same agent — explicitly rebind ownership to a chosen target daemon so subsequent dispatches route deterministically. Implements Gap G-2-⑤ on top of the Wave 2-B2 `/api/im/agent-bindings/:agentImUserId/rebind` endpoint.

sdk/cloud/catalog/skills/claim-agent-ownership/SKILL.md

Read pinned source

Source commit f83b859a173802a73d978197e92328ab2bf57a6e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 3, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,364
Repository last updated: Oct 22, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-communication Repository topic
agent-memory Repository topic
ai-agents Repository topic
claude Repository topic
cursor Repository topic
docker Repository topic
knowledge-base Repository topic
llm-tools Repository topic
mcp Repository topic
mcp-server Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 12,008 bytes
SKILL.mdcore · 12,008 bytes

Read excerpt


# Claim Agent Ownership

When two daemons (typically Mac Studio at home + a k8s pod) both run `agent.host.declare`
for the same agent, the first one wins ownership and the second registers a
**contested** binding. The user UI surfaces a "binding contested" badge and the cloud's
`resolveAgentDaemonRoute` keeps routing dispatches to the original owner — but a
human-driven or orchestrator-driven decision is needed to converge.

This skill is the **orchestrator's tool for that decision**. It calls the server's
authoritative rebind endpoint, which atomically:

1. flips `im_agent_bindings.boundDaemonId` to the chosen target daemon
2. writes an audit row with `boundBy='user-explicit'` (or `'orchestrator'`)
3. returns the **in-flight task count** on the previous owner so the orchestrator can