BB 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.
Operate physical hardware (cameras, sensors, lamps, arms, lab equipment) through Model Hardware Standard adapters — mhsdiscover (what devices exist)…
As a process B 67/100 · Nearly there — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 67/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (qwen-mm-plugins-mhs) differs from the folder (skill)
- 100Tools and files. No external tools needed
- 100Steps. 25 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 2054 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 443: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.