linkr-control

Linkr control

Use this skill when Piclaw must interact with a specific machine through a Radxa Linkr KVM and safer direct methods such as SSH, guest agents, or browser automation are unavailable.

See tool contract and safety rules.

Start read-only

Before any input:

1. Resolve the target with profile.list, profile.select, and status.
2. Inspect capabilities and note any unsupported families.
3. Capture a fresh snapshot and read both the image and metadata.
4. Confirm the visible screen matches the authorised task and targetIdentity.

Do not infer authority from a selected profile alone.

Core operating loop

1. Observe — take snapshot and identify OS, active prompt, focus, and ambiguity.
2. Plan — choose the smallest next action that could safely advance the task.
3. Preview — call the mutating action without execute:true first when the next step is nontrivial.
4. Execute — resend with execute:true only when the effect is authorised.
5. Verify — take a new snapshot and confirm the result before continuing.

HTTP or API success only acknowledges delivery. It does not prove the remote application accepted the action.

Actions to prefer

For ordinary interactive control, prefer these actions and fields:

• snapshot
• key.tap with device_id, key
• key.combo with device_id, keys
• key.repeat with device_id, key, count, interval_ms
• text with device_id, text
• mouse.move with device_id, x, y
• mouse.click with device_id, x, y
• mouse.drag with device_id, x, y, to_x, to_y
• mouse.scroll with device_id, wheel_y, wheel_x
• input.batch with device_id, events
• input.release

Use job.start only for bounded local capture or firmware-entry jobs, not as a generic macro recorder.

Exact examples

{"action":"key.tap","device_id":"lab-workstation-a","key":"Tab","execute":true}