patch-database

Query the Max/MSP patch database for patterns, examples, roles, and gotchas.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/CooperNederhood/Ableton-Agent-App --skill patch-database-coopernederhood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patch-database
Source: https://github.com/CooperNederhood/Ableton-Agent-App/tree/main/.github/skills/patch-database
Command: npx skills add https://github.com/CooperNederhood/Ableton-Agent-App --skill patch-database-coopernederhood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building Max/MSP and Max for Live patches often requires knowing which objects to use, how they connect, and what pitfalls to avoid. This Skill provides structured access to a canonical patch knowledge database so you can look up patterns, examples, object roles, and gotchas instead of guessing or manually inspecting .amxd files. ## Core Features & Use Cases - Similarity and Search Queries: Find relevant patches with similar and search commands, then inspect promising results with details. - Gotcha and Role Lookup: Retrieve known pitfalls for specific objects (e.g., gotchas jit.catch~) and understand object roles before wiring connections. - Connection Graph Queries: Explore how objects connect using connects-to, connects-from, find, and chain commands. - Use Case: Before building an audio visualization patch, run similar "visualize audio", review details on the best match, check gotchas for the involved jitter objects, and verify connections with connects-to. ## Quick Start Set the MAX4LIVE_MCP_ROOT environment variable to your local Max4Live-MCP checkout and ask the agent to query the patch database for patches similar to your intended design.

Frequently Asked Questions about patch-database

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

FAQPage Schema
How do I search a Max/MSP patch database for examples?

Run patch_db.py with the `similar` or `search` command followed by a descriptive query, always passing --db with the explicit path to patches.db. Use `details` on a returned patch name to inspect its full information.

How to find gotchas for Max/MSP objects before patching?

Use the `gotchas` command with an object name, such as `gotchas jit.catch~`, or search across all gotchas with `gotchas --search "audio thread"`. Check gotchas before implementation to avoid known pitfalls.

Why does patch_db.py fail to find the database?

patch_db.py resolves its default database path relative to the current working directory, so queries fail when run from other locations. Always pass the database explicitly with --db pointing to the absolute patches.db path.

Can I query how Max/MSP objects connect to each other?

Yes, use `connects-to` and `connects-from` to see an object's connections, `find` to locate paths between two objects, and `chain` to explore connection sequences. Run these before wiring objects in your patch.

What are the limitations of the patch database lookup?

The database only contains indexed knowledge, so exact low-level details may be missing for some patches. In those cases, fall back to raw .amxd file inspection, and note the skill requires a local Max4Live-MCP checkout via MAX4LIVE_MCP_ROOT.