test-bindings

Test mouse button bindings in Slicer MouseMaster to verify mappings and diagnose issues.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/benzwick/SlicerMouseMaster --skill test-bindings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-bindings
Source: https://github.com/benzwick/SlicerMouseMaster/tree/main/.claude/skills/test-bindings
Command: npx skills add https://github.com/benzwick/SlicerMouseMaster --skill test-bindings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps users validate and troubleshoot mouse button bindings in the Slicer MouseMaster extension by guiding interactive checks of active state, current presets, and action mappings.

Core Features & Use Cases

  • Verify that bindings trigger as configured for different mice and contexts.
  • Inspect current mouse profile and preset mappings, and switch presets to compare behavior.
  • Step through individual button actions to confirm expected outcomes and locate misconfigurations.

Quick Start

Open the MouseMaster module in Slicer, load a mouse profile, and run the interactive test sequence to verify binding behavior.

Frequently Asked Questions about test-bindings

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

FAQPage Schema
How do I test mouse button bindings in Slicer to verify they trigger correctly?

To test mouse bindings in Slicer, open the MouseMaster module, load an active mouse profile, and run the interactive test sequence to verify that mappings trigger correctly and diagnose binding issues.

What do I need to debug mouse profile mappings and context-sensitive bindings in Slicer?

Debugging mouse profile mappings in Slicer requires the MouseMaster module to be loaded, an active mouse profile, and access to logic methods to inspect presets, mappings, and actions.

How can I check which Slicer mouse preset is active and switch presets to compare behavior?

You can inspect the current mouse profile and preset mappings through the Slicer MouseMaster module, allowing you to switch presets and compare binding behavior across different contexts and mice.

Why does my Slicer mouse binding trigger the wrong action or fail to respond?

Slicer mouse bindings may fail due to misconfigured presets or context-sensitive mappings; stepping through individual button actions interactively helps confirm expected outcomes and locate the exact misconfiguration.

Can I step through individual mouse button actions to locate misconfigurations in Slicer?

Yes, you can step through individual button actions within the Slicer MouseMaster module to confirm expected outcomes and locate binding misconfigurations across different mice and preset configurations.