mmd-device-library

Create, manage, and publish MIDI Markdown device libraries with metadata and aliases.

2|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/cjgdev/midi-markdown --skill mmd-device-library
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mmd-device-library
Source: https://github.com/cjgdev/midi-markdown/tree/main/.claude/skills/mmd-device-library
Command: npx skills add https://github.com/cjgdev/midi-markdown --skill mmd-device-library

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MIDI device libraries simplify creating, documenting, and reusing device-specific aliases for MIDI Markdown, reducing manual setup and human error.

Core Features & Use Cases

  • Define device metadata, aliases, and documentation in a single library file
  • Import and reuse libraries across projects
  • Test and validate alias definitions to ensure correct MIDI outputs
  • Use case: build a library for a guitar processor and share across your team

Quick Start

Save the library to devices/my_device.mmd and import it with @import "devices/my_device.mmd".

Frequently Asked Questions about mmd-device-library

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

FAQPage Schema
How do I create reusable aliases for MIDI devices?

You can create reusable aliases for MIDI devices by defining device metadata, aliases, and documentation in a single Markdown library file, which reduces manual setup and human error.

How do I import a MIDI device library into my project?

To import a MIDI device library, save the file to a directory like devices/my_device.mmd and reference it in your project using the import syntax @import "devices/my_device.mmd".

What is a MIDI Markdown device library used for?

A MIDI Markdown device library is used to define, document, and reuse device-specific aliases for hardware such as guitar processors, synthesizers, and effects units across multiple projects.

Can I test and validate MIDI alias definitions before publishing?

Yes, you can test and validate alias definitions within the library to ensure they generate the correct MIDI outputs before sharing the library file across your team or projects.

What structure is required for a valid MIDI Markdown device library?

A valid MIDI Markdown device library requires a root SKILL.md file with YAML frontmatter containing the name and description, and optionally recognizes scripts, references, and assets directories.

Do I need any specific dependencies to manage MIDI device libraries?

No specific dependencies are required to manage MIDI device libraries, as the system operates independently to enforce valid skill unit structures and validate alias definitions.