add-mouse-profile

Generate standardized MouseMaster profile JSON and default preset for new mice.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating support for new mouse models in MouseMaster by generating standardized, ready-to-use profile definitions and presets.

Core Features & Use Cases

  • Gather essential mouse details (model name, vendor, vendor ID, product IDs, button count) to form a new profile.
  • Generate a canonical profile JSON and a default preset that maps common actions to the new device.
  • Update documentation to reflect the newly supported mouse, and ensure IDs are unique and consistent.

Quick Start

Provide the new mouse details and let the skill generate the profile JSON and default preset.

Frequently Asked Questions about add-mouse-profile

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

FAQPage Schema
How do I add a new mouse profile to MouseMaster?

A mouse profile requires model name, vendor, vendor ID, product IDs, and button count. The skill uses these details to generate a standardized profile JSON and a default preset that maps common actions to the new device.

What is a mouse profile JSON definition and when do I need one?

A mouse profile JSON definition is a standardized schema capturing vendor details, hardware IDs, and button configurations for a specific mouse. You need one when expanding hardware support to new mice in MouseMaster to ensure deterministic behavior.

Can I generate a default preset when creating a new mouse profile?

Yes, generating a default preset alongside the new mouse profile is supported. The skill creates a default preset that maps common actions to the new device while ensuring all IDs align with the generated profile_id.

What's the best way to structure file paths for mouse hardware support profiles?

The best way to structure file paths for mouse hardware support is to follow the consistent file path structure enforced by the profile generation process. This ensures the profile JSON and preset schema remain standardized across all supported mice.

Does MouseMaster require unique product IDs for each mouse profile?

Yes, MouseMaster requires unique product IDs for each mouse profile to ensure deterministic behavior. The skill enforces ID consistency by aligning all generated preset IDs with the newly generated profile_id.

Why does my mouse profile need a default preset?

Your mouse profile needs a default preset to map common actions to the new device out of the box. This ensures the newly supported mouse is immediately usable with standard configurations without manual setup.