Individual skill
qwen-mm-plugins-mhs
Operate physical hardware (cameras, sensors, lamps, arms, lab equipment) through Model Hardware Standard adapters — mhs_discover (what devices exist), mhs_meta_info (what one device can do and its safety limits), mhs_read (sensor values, camera frames), mhs_write (send a command), mhs_health_check (is it alive), mhs_reset (recover or emergency-stop). Use whenever a task involves reading from or controlling a real device rather than a file.
src/capabilities/mhs/skill/SKILL.md
Source commit 8c2bd5c46b6a00814624202203a30284e4e6b43c
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 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)
- 3,198
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- 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 · 8,756 bytesSKILL.mdcore · 8,756 bytesSKILL.mdcore · 8,756 bytesreferences/adapter_protocol.mddoc · 13,192 bytesreferences/adapter_server.pyruns · 8,926 bytesreferences/mock_adapter.pyruns · 15,470 bytes
Read excerpt
# Qwen-MM-Plugins MHS
You have `qwen-mm-plugins-mhs` MCP tools available. They operate **real hardware**. MHS is to hardware
what MCP is to tools: one fixed six-tool surface, with everything device-specific behind an *adapter*
that the hardware's owner runs. You never learn a per-device API — you ask the device what it can do.
The tool surface does not grow when new hardware appears. A new device shows up in `mhs_discover`
because someone started an adapter for it.
Check the `qwen-mm-plugins-mhs` tools in your tool list for full schemas.
For worked examples, see the [MHS cookbook](https://qwenlm.github.io/qwen-mm-plugins-hub/plugins/mhs/cookbook/).
## The loop