daw-smoke

Verify REAPER DAW features with live plugin swaps and reloads.

1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielraffel/burl --skill daw-smoke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daw-smoke
Source: https://github.com/danielraffel/burl/tree/main/.agents/skills/daw-smoke
Command: npx skills add https://github.com/danielraffel/burl --skill daw-smoke

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that changes to reloads, editors, or format-adapters in a Digital Audio Workstation (DAW) like REAPER actually work as intended within the host environment.

Core Features & Use Cases

  • Functional Verification: Confirms the behavior of DAW features beyond what static validation tools can achieve.
  • DAW-Specific Testing: Tailored for REAPER, it can perform live plugin swaps and reloads to verify in-host functionality.
  • Use Case: Before deploying a change to a DAW, use this Skill to automate tests that ensure the change behaves correctly in a real-world scenario.

Quick Start

Run the 'daw-smoke' skill with the 'reload' mode to verify a reload/editor/format-adapter change in REAPER.

Frequently Asked Questions about daw-smoke

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

FAQPage Schema
How do I verify REAPER plugin functionality after making code changes?

To verify REAPER plugin functionality after code changes, you can perform live plugin swaps and reloads within a real DAW session to ensure the changes behave as intended in the host environment.

What is DAW functional verification and when do I need it?

DAW functional verification confirms the behavior of features like reloads, editors, or format-adapters in a Digital Audio Workstation, which you need before deploying changes to ensure they work beyond static validation.

Can I test audio engineering plugin reloads in a live REAPER session?

Yes, you can test audio engineering plugin reloads in a live REAPER session by using automated testing scripts to perform live swaps and verify in-host functionality.

Does DAW testing with this approach require specific software or dependencies?

DAW testing with this approach requires REAPER and its associated testing scripts to perform the live plugin swaps and reloads needed to verify changes in the host environment.

Why does static validation fail to catch DAW plugin issues?

Static validation fails to catch DAW plugin issues because it cannot confirm the actual functional behavior of reloads or format-adapters within the live host environment like REAPER.

What is the best way to automate functional verification for REAPER format-adapters?

The best way to automate functional verification for REAPER format-adapters is running the 'daw-smoke' skill in 'reload' mode to verify changes through live plugin swaps in a real session.