← ClaudeAtlas

hardware-protocol-capturelisted

Use when documenting how a music hardware device is controlled over MIDI (CC, NRPN, SysEx) or USB so a controller, editor or librarian can be built, from official docs and own-device captures.
SpeakingColors/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill SpeakingColors/claude-skills
# Hardware protocol capture Unofficial community skill. Not legal advice. Capture only devices the user owns. ## 0. Rules - The device is the source of truth. Documents can be wrong or outdated; a capture from the real device with the user's firmware is the proof. - Source order: 1) the manufacturer's official documents, 2) captures from the user's own hardware, 3) third-party documents (mark as unverified until checked on hardware). - Every entry in the final document carries a status: verified on hardware, from official doc only, or unverified. - Back up the device's patches and settings before sending anything unknown. Never send firmware, bootloader, flash-write or factory-reset messages until their format is fully understood. - Give one step at a time to non-programmers. Short answers first. ## 1. Find the official documents - Look for a "MIDI Implementation" or "MIDI data format" document for the product on the manufacturer's support page, plus the owner's manual's MIDI implementation chart. Example: KORG publishes the minilogue xd MIDI Implementation as a separate text file (download after accepting a personal, non-commercial licence). Link to such documents; do not copy them into public repos unless their licence allows it. - Check the document's revision and date against the device's firmware version. Firmware updates can change formats. Example: a third-party library for that synth notes that some preset files from newer firmware use 448-byte program blobs, not