add-mouse-profile

Create a new mouse profile for a mouse model not yet supported

16 stars

Best use case

add-mouse-profile is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Create a new mouse profile for a mouse model not yet supported

Teams using add-mouse-profile should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/add-mouse-profile/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/documentation/add-mouse-profile/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/add-mouse-profile/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How add-mouse-profile Compares

Feature / Agentadd-mouse-profileStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Create a new mouse profile for a mouse model not yet supported

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Add Mouse Profile Skill

Create a new mouse profile for MouseMaster.

## When to Use

Use this skill when:
- User wants to add support for a new mouse model
- User has button detection results to formalize
- User provides vendor/product IDs for a mouse

## Steps

1. **Gather Information**
   Ask the user for:
   - Mouse name (e.g., "Logitech MX Master 3S")
   - Vendor name
   - Vendor ID (hex, e.g., "0x046D") - optional
   - Product IDs (hex array) - optional
   - Number of buttons

2. **Create Profile ID**
   Generate from name: lowercase, underscores for spaces
   Example: "Logitech MX Master 3S" -> "logitech_mx_master_3s"

3. **Define Buttons**
   For each button, define:
   ```json
   {
     "id": "button_id",
     "name": "Human Name",
     "qtButton": <qt_code>,
     "remappable": true/false,
     "defaultAction": "action_id"  // optional
   }
   ```

   Standard Qt button codes:
   - 1: Left Click (not remappable)
   - 2: Right Click (not remappable)
   - 4: Middle Click
   - 8: Back/Button 4
   - 16: Forward/Button 5
   - 32: Extra Button 1
   - 64: Extra Button 2

4. **Create JSON File**
   Write to: `MouseMaster/Resources/MouseDefinitions/<profile_id>.json`

   ```json
   {
     "id": "<profile_id>",
     "name": "<mouse_name>",
     "vendor": "<vendor>",
     "vendorId": "<vendor_id>",
     "productIds": ["<product_id>"],
     "buttons": [...],
     "features": {
       "horizontalScroll": false,
       "thumbWheel": false,
       "gestureButton": false
     }
   }
   ```

5. **Create Default Preset**
   Write to: `presets/builtin/default_<profile_id>.json`

   ```json
   {
     "id": "default_<profile_id>",
     "name": "<mouse_name> Default",
     "version": "1.0",
     "mouseId": "<profile_id>",
     "mappings": {
       "middle": {"action": "view_reset_3d"},
       "back": {"action": "edit_undo"},
       "forward": {"action": "edit_redo"}
     },
     "contextMappings": {}
   }
   ```

6. **Update Documentation**
   Add to README.md supported mice table:
   ```markdown
   | <Mouse Name> | <Vendor ID> | <Button Count> | Fully Supported |
   ```

## Example Interaction

User: "Add support for Razer DeathAdder V3"

Claude:
1. Creates `logitech_razer_deathadder_v3.json` in MouseDefinitions
2. Creates `default_razer_deathadder_v3.json` in presets/builtin
3. Updates README.md supported mice table
4. Confirms creation with file paths

## Validation

After creating files:
- Verify JSON is valid
- Verify all required fields present
- Verify button IDs are unique
- Verify preset mouseId matches profile id

Related Skills

hinge-profile-optimizer

16
from diegosouzapw/awesome-omni-skill

Comprehensive, research-backed Hinge dating profile optimization. Use when someone wants to improve their Hinge profile, audit an existing profile, write better prompts/captions, select and order photos strategically, or understand why they're not getting quality matches. This is the thorough process (60-90 mins) - discovery interview, game theory analysis, photo strategy, copy creation, settings optimization, and implementation support. Based on 45+ peer-reviewed sources on dating app behavior.

global-methylation-profile

16
from diegosouzapw/awesome-omni-skill

This skill performs genome-wide DNA methylation profiling. It supports single-sample and multi-sample workflows to compute methylation density distributions, genomic feature distribution of the methylation profile, and sample-level clustering/PCA. Use it when you want to systematically characterize global methylation patterns from WGBS or similar per-CpG methylation call files.

routing-profiles

16
from diegosouzapw/awesome-omni-skill

Change the Routing Solution routing profiles/vehicle types. To be used as part of customize-main skill

agentuity-cli-profile-use

16
from diegosouzapw/awesome-omni-skill

Switch to a different configuration profile

agentuity-cli-profile-show

16
from diegosouzapw/awesome-omni-skill

Show the configuration of a profile

agentuity-cli-profile-list

16
from diegosouzapw/awesome-omni-skill

List all available profiles

agentuity-cli-profile-delete

16
from diegosouzapw/awesome-omni-skill

Delete a configuration profile

godot-profile-performance

16
from diegosouzapw/awesome-omni-skill

Detects performance bottlenecks in Godot projects including expensive _process functions, get_node() calls in loops, instantiations in _process, and provides optimization suggestions with Godot profiler integration

bgo

10
from diegosouzapw/awesome-omni-skill

Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.

Coding & Development

ai-search-technical-auditor

16
from diegosouzapw/awesome-omni-skill

Audit front-end code for AI search readiness. Use when reviewing HTML structure, meta tags, schema markup, and technical elements that affect how AI crawlers understand and index web pages.

ai-output-validator

16
from diegosouzapw/awesome-omni-skill

AI出力の品質を自動検証するスキル。事実確認、論理性、一貫性、幻覚(ハルシネーション)検出、バイアス分析、安全性チェックを実施し、改善提案を提供。

ai-organizer-ui-consolidation

16
from diegosouzapw/awesome-omni-skill

Build a unified, ADHD-friendly web UI that consolidates 70+ CLI tools into a beautiful liquid glass interface for the AI File Organizer. Use when creating the complete frontend application that replaces all terminal interactions with a macOS-inspired dashboard for file organization, search, VEO prompts, and system management.