set-mobile-clipboard-image

Place a base64-encoded image on a phone clipboard via the customer_service HTTP bridge.

22|3|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/MadeAgents/TopoClaw --skill set-mobile-clipboard-image
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: set-mobile-clipboard-image
Source: https://github.com/MadeAgents/TopoClaw/tree/main/TopoClaw/topoclaw/skills/set-mobile-clipboard-image
Command: npx skills add https://github.com/MadeAgents/TopoClaw --skill set-mobile-clipboard-image

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests.

What problem does it solve?

This skill solves the need to quickly place an image on a target phone’s clipboard without manually interacting with the phone.

Core Features & Use Cases

  • Cross-device clipboard image writing: Push a base64-encoded image to the phone clipboard via the customer_service mobile-tool HTTP bridge.
  • Targeted by device identity: Uses the target phone IMEI to ensure the clipboard operation targets the correct device.
  • Configurable labeling and timeout: Lets you set a clipboard label and adjust the wait timeout for the mobile tool invocation.
  • Use Case: When a user receives an image generated on TopoDesktop, this skill can transfer it to the user’s phone clipboard so the user can paste it into a chat, note, or app immediately.

Quick Start

Instruct the assistant to set the target phone clipboard image by providing the phone IMEI and the image base64, for example: "Set my phone clipboard image for IMEI <TOPO_IMEI> using image base64 in TOPO_IMAGE_BASE64."

Frequently Asked Questions about set-mobile-clipboard-image

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I push an image to a mobile clipboard from a desktop?

This skill places a base64-encoded image into a phone clipboard by calling the mobile device.set_clipboard_image tool over a customer_service HTTP bridge. It requires the target phone IMEI and the base64 image data.

Can I target a specific Android phone for a clipboard image operation?

Yes, targeting a specific device is supported by providing the TOPO_IMEI identifier. This ensures the mobile-tool HTTP bridge routes the clipboard image operation to the correct phone.

What format does the image need to be in for the mobile clipboard?

The image must be provided as base64-encoded data. You supply this via the TOPO_IMAGE_BASE64 parameter or a supported base64 environment fallback for the mobile-tool invoke request.

Does cross-device clipboard image transfer require a special environment setup?

It requires the requests library and access to the customer_service HTTP bridge endpoint. You also need the target device IMEI and base64 image data to execute the mobile-tool invoke POST request.

Why is my desktop to mobile clipboard image transfer not working?

Desktop to mobile clipboard image transfer may fail if the TOPO_IMEI or TOPO_IMAGE_BASE64 variables are missing, or if the POST request to the mobile-tool invoke bridge times out before returning a result.