Stratawright daw-cli skill
Stratawright
The daw-cli skill drives the Stratawright digital audio workstation: tracks, levels, VST3 and AU plugins, routing and MIDI
- 133 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent changes the workstation project: tracks, clips, routes and levels, including cleaning recorded takes
- The skill calls VST3, AU and CLAP plugins, which means third-party binary code
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/stratawrightDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent changes the workstation project: tracks, clips, routes and levels, including cleaning recorded takes
- The skill calls VST3, AU and CLAP plugins, which means third-party binary code
This is third-party code. Review the repository files before installing.
What it does
Stratawright is an open-source digital audio workstation built to be driven by an AI agent. The repository holds both the program and the `daw-cli` skill. The skill teaches the agent to use the `daw-cli` command-line client, which talks to a running workstation over the UNIX socket `/tmp/daw_session.sock`. Through the client the agent reads and changes session state, starts the transport, creates and configures tracks, sets levels, hosts VST3, AU and CLAP plugins, builds buses and signal routes, and edits clips and MIDI on the timeline. There is also signal analysis without a graphical interface. The author describes typical requests like this: level tracks for streaming, strip background noise and silence from recorded takes, and sort 100 tracks into buses by the meaning of their names, for example sending `GTR_L_57` to the guitar bus. Setup starts with building the workstation, and the skill is installed separately.
Who it is for. Music producers and sound engineers whose projects grow beyond a hundred tracks and who want to hand routine session prep to an agent.
Good fit when
- A session of a hundred tracks needs sorting into buses and colors, which takes half an hour by hand
- Track levels have to be matched for streaming with one sentence instead of manual tuning
- Recorded takes have to be searched for silence and background noise and cleaned
- A plugin chain, such as a vocal one, has to be applied to several tracks at once
- A project is assembled by script and the workstation has to be called from the agent's batch commands
Not a fit when
- You need a ready commercial workstation with support: Stratawright ships as source under the MIT license
- The workstation is not running: `daw-cli` works only with a running application
- You need recording and mixing without compiling an application: Stratawright has to be built first
Example request
Bring all vocal tracks to one level for streaming and send the `GTR_*` guitars to a shared bus, do not delete the source clipsLimitations
The skill does not work without a running Stratawright workstation, which is first built with the repository's `install_dependencies.sh` and `build.sh release --package` scripts. Communication goes over the `/tmp/daw_session.sock` socket, so the agent and the workstation must be on the same machine. The reference links inside `SKILL.md` point to the author's local paths, so take `error_codes.md` and `command_schema.json` from the `skills/daw-cli/references/` folder.
How to disable. Delete the `daw-cli` skill from the agent's skills folder. Close the workstation like an ordinary application and delete the built files together with the cloned repository.
FAQ
How do I install the daw-cli skill?
Clone the repository and run `npx skills add ./skills/daw-cli`. Or copy the `skills/daw-cli/` folder into the agent's skills directory, for example `~/.claude/skills/daw-cli`.
Do I need to build the workstation itself?
Yes, the skill controls a running application. The README suggests handing the build to the agent, which runs `./scripts/install_dependencies.sh` and `./scripts/build.sh release --package`.
Which plugins does the workstation support?
VST3, AU and CLAP. The agent can load plugins and apply one chain across several tracks.
How do I check that the agent sees the workstation?
Run `daw-cli status`. If the workstation is not running or the `/tmp/daw_session.sock` socket is unavailable, the command reports a connection error.
Which agents does the skill work with?
The README names Claude Code, Codex, Cursor, Hermes and Gemini CLI, as well as OpenCode and over 50 more environments. The skill installs under the Agent Skills standard.
Discussion
No questions or reviews yet.
Related
SkillsA skill that teaches the agent to build narrated videos through narrator-ai-cli: source, template, music, voice, script and composing
Kling CLI
kling-cli
A skill for the Kling command-line tool: the agent makes video and images from text and a reference, drives motion and keeps reusable characters
watch-cli is a skill and CLI that hands an agent the frames and transcript of any social video so it can read the clip itself.
A skill that turns a script into a finished video with voice-over, subtitles, a cover and a publish text, frames drawn by code.
A CLI and coding-agent skills assemble rough cuts from your footage and save editable projects for further review
A loop skill: the agent generates a target screenshot, builds toward it, and uses a critic subagent to close the gap until they match
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Stratawright daw-cli (this card) | no | 133 | ||
| Ableton MCP | no | not required | 3,349 | an MCP server for Ableton Live, while this is its own open workstation with a command-line client |
| Claude AI Music Skills | no | 662 | a plugin with skills for song creation, while this controls mixing and tracks inside a workstation |
README in short
The README presents the project as an open workstation for working with an agent and compares the manual process with plain-language commands. It then covers a three-step setup, example scenarios, agent capabilities, key workstation features, a build-from-source guide and the MIT license. Translations in four languages are available.
README badge
Original SKILL.md
--- name: daw-cli description: >- Instructs agents to control Stratawright DAW via the daw-cli command-line IPC interface. Covers session state, transport, track management, gain staging, VST3/AU plugin hosting, signal routing, clips, MIDI timeline editing, and non-visual DSP analysis & audio intelligence. Requires the DAW application to be running. --- # Stratawright DAW CLI Control ## Overview `daw-cli` is the command-line IPC client for **Stratawright DAW**, allowing AI agents and automation tools to query and mutate session state, manage tracks, perform gain-staging, host VST3/AU/CLAP plugins, configure signal routing & bus topology, execute clip and MIDI timeline edits, and perform non-visual DSP analysis & audio intelligence in real time. All commands communicate with the running DAW application using a UNIX domain socket. Binary location (if not installed on system PATH): - Quoted path: `"./build/release/src/Agentic\ layer/daw-cli"` (Release build) - Quoted path: `"./build/debug/src/Agentic\ layer/daw-cli"` (Debug build) - Standard executable name (if symlinked / on PATH): `daw-cli` ## References Directory - [error_codes.md](file:///Users/goldenfung/Documents/agent-based-daw/skills/daw-cli/references/error_codes.md): Detailed IPC error codes, trigger causes, and recovery actions. - [command_schema.json](file:///Users/goldenfung/Documents/agent-based-daw/skills/daw-cli/references/command_schema.json): Machine-readable JSON schema defining all verbs, subcommands, flags, types, and defaults. --- ## Prerequisites 1. **DAW Application Must Be Running**: The GUI/Server application must be active before running `daw-cli`. 2. **UNIX Socket Path**: The server listens on `/tmp/daw_session.sock`. 3. **Connectivity Check**: Always verify connection state first before executing batch commands: ```bash daw-cli status ``` If the DAW is not running, `daw-cli` will fail immediately with exit code `71` (`DAW_NOT_RUNNING`). --- ## Output Formats & Parsing