qwen-mm-plugins-mhs

Discover, read, and control physical hardware devices through MHS adapters over HTTP.

2.9k|185|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/QwenLM/Qwen-MM-Plugins --skill qwen-mm-plugins-mhs-qwenlm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qwen-mm-plugins-mhs
Source: https://github.com/QwenLM/Qwen-MM-Plugins/tree/main/src/capabilities/mhs/skill
Command: npx skills add https://github.com/QwenLM/Qwen-MM-Plugins --skill qwen-mm-plugins-mhs-qwenlm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires msgpack, and includes references (resource) components.

What problem does it solve? Operating real hardware from an agent normally requires learning a different API per device. This Skill provides one fixed six-tool surface (discover, meta_info, read, write, health_check, reset) that works with any device behind a Model Hardware Standard adapter, with declared safety limits enforced before commands reach the hardware. ## Core Features & Use Cases - Device Discovery and Inspection: List every registered device with mhs_discover, then read per-device capabilities, parameter ranges, units, and confirmation requirements with mhs_meta_info. - Safe Hardware Control: Read sensor values and camera frames with mhs_read, send commands with mhs_write, and enforce hard/soft safety limits plus confirmation gates on consequential writes. - Health and Emergency Stop: Check live device state with mhs_health_check and recover or halt devices with mhs_reset in soft or estop mode. - Use Case: A lab camera and lamp expose MHS adapters on the local network. The agent discovers them, reads a camera frame as an image, adjusts exposure within the declared hard limit, and switches the lamp on only after explicit confirmation. ## Quick Start Ask the agent to discover available MHS devices and read a frame from the camera, then adjust its exposure within the declared limits.

Frequently Asked Questions about qwen-mm-plugins-mhs

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

FAQPage Schema
How do I control hardware devices from an AI agent?

Register each device's MHS adapter in ~/.qwen-mm-plugins/mhs-devices.json, then call mhs_discover to list devices, mhs_meta_info to learn capabilities and limits, and mhs_write to send commands. The agent never needs a per-device API because every adapter exposes the same six-tool surface.

How do I write an MHS adapter for my own device?

Copy references/mock_adapter.py with references/adapter_server.py and replace the read, write, health, and reset methods with real hardware I/O. Validate it with python3 -m qwen_mm_plugins_mhs.verify, then add one entry to the registry file; discovery picks it up immediately.

What safety limits does MHS enforce on hardware writes?

Adapters declare safety_limits per parameter with min, max, and a hard flag. Hard limits refuse the write outright with no override, while soft limits require confirm=true. Capabilities marked requires_confirm also block writes unless the model explicitly confirms.

Can I test MHS tools without real hardware?

Yes. Run references/mock_adapter.py, which serves a simulated camera with exposure and gain limits and a lamp whose power write requires confirmation. Point the registry at http://127.0.0.1:8800 and the full discover-read-write-reset loop works end to end.

What happens when an MHS device does not support reset?

Reset is optional in the protocol. If a device does not implement it, the adapter returns 404, 405, or 501 and the host reports plainly that the device cannot be stopped through the tool, so the user knows immediately.