algonormative

Analog Rytm Agent Bridge — Development skill for Claude Code

Development community

A control plane that lets a coding agent operate an Elektron Analog Rytm MKII — validated deltas, raw SysEx snapshots, readback verification, byte-exact rollback.

How to install Analog Rytm Agent Bridge

This entry records only its repository, not the path inside it, so there is no exact command to give. Open algonormative/analog-rytm-agent-bridge and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Analog Rytm Agent Bridge does

A control plane that lets a coding agent operate an Elektron Analog Rytm MKII — validated deltas, raw SysEx snapshots, readback verification, byte-exact rollback.

Alternatives in Development

Epic Publish — Publish a validated epic update back to the issue and local cache 243.5k ★
Agent Skills Platform — Build tested agent skills and govern their lifecycle through a user-defined marketplace: evidence, discovery 2.4k ★
Agent Skill Creator — Build tested agent skills and govern their lifecycle through a user-defined marketplace: evidence, discovery 2.3k ★

README

analog-rytm-agent-bridge

**Let your coding agent use your Analog Rytm MkII with MCP.**

*Thirty-two semantic tools covering the whole instrument — patterns and p-locks, kit sounds and machines, scenes and performance macros, songs, the sample RAM, and audio capture. The agent reads the device's real state, proposes a change in musical terms, and commits it on the next beat.*

[Site](https://algonormative.github.io/analog-rytm-agent-bridge/) · [MCP setup](docs/MCP.md) · [Quick start](#quick-start) · [Tools](#the-agent-surface) · [Safety](#the-safety-model) · [Capabilities](docs/CAPABILITIES.md)

claude mcp add rytm -- npm run mcp

That attaches the full tool surface to your agent against a mock device — no hardware, no MIDI cable, nothing at risk. Ask it *"what's on pattern A01?"* and it will reach for `rytm_inspect_pattern`.

What this is

An Analog Rytm holds twelve voices, 128 patterns, kits, sounds, scenes, performance macros, songs, and 127 sample slots of state that a person edits by hand. This bridge exposes that state to a coding agent as semantic operations, so you can say *"give the snare a conditional fill every 4th pass"* or *"chain A01 into A02 twice and mute the toms on the last one"* and have it land on the hardware, on the beat.

The vocabulary is musical intent rather than SysEx addresses, and the agent works from a compact summary of what is actually on the device rather than a guess. Capture is part of the loop too — it can play what it wrote, record it, and listen back.

It is also usable without an agent. The daemon and CLIs are ordinary tools for inspecting, validating, queueing, and applying Rytm operations.

The safety model

The short version: hardware has no ctrl-Z, so every persistent change is validated against decoded device state, snapshotted as raw SysEx, applied at a musical boundary, read back, and restored byte-exactly if the readback disagrees. Read the rest before pointing it