Prepare WaveTone 2.61 audio analysis workflows by inspecting audio metadata and recording tempo, labels, and intended settings in a JSON project manifest. Launch the Windows application to perform analysis and save its outputs.
Control WaveTone 2.61 workflows through a JSON manifest and launch the real Windows WaveTone executable.
Review the instructions the agent will receive before you install.
Use this skill when an agent needs to prepare, inspect, and launch WaveTone 2.61 audio transcription workflows.
WAVETONE_EXE to wavetone.exe or WAVETONE_HOME to the extracted
WaveTone directory when the default portable path is not used.All commands support the top-level --json flag.
cli-anything-wavetone --json wavetone doctor
cli-anything-wavetone --json project new input.wav -o project.wt.json
cli-anything-wavetone --project project.wt.json --json audio probe
cli-anything-wavetone --project project.wt.json --json project set-tempo --bpm 120 --meter 4/4
cli-anything-wavetone --project project.wt.json --json project add-label chorus --time 64.0
cli-anything-wavetone --project project.wt.json --json wavetone launch
project: create manifests, set tempo, add labels, update intended analysis
settings, and attach a WFD saved from WaveTone.audio: probe audio metadata before opening it in WaveTone.wavetone: run doctor, list supported formats, or launch the real GUI.session: record lightweight event logs for multi-step agent workflows.defaults: show default analysis settings.The JSON project manifest is not a WaveTone WFD file. It is an agent-facing plan for the source audio, intended analysis settings, labels, and tempo metadata. Use WaveTone itself to perform analysis and save WFD/MIDI/text/WAVE outputs.
When running in automated checks, use:
cli-anything-wavetone --json wavetone launch input.wav --wait 1 --terminate
This confirms that the real backend can be started without leaving a persistent GUI process behind.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use Reasonix to build or improve a Python command-line interface for existing software. The workflow covers source analysis, interactive commands, JSON output, tests, documentation, and installation checks using the software’s own backend where possible.
Build and improve Python command interfaces for GUI applications with OpenClaw. The skill guides source analysis, command design, testing, and packaging, including interactive sessions and structured JSON output for agents.
Use Codex to build Python command-line tools for applications with graphical interfaces. Analyze source code, add commands, test against the actual software, validate packaging and documentation, and discover tools already generated or installed.
Inspect and edit 3MF files for 3D printing. Detect cylindrical holes, change their diameters, repair mesh issues, and compare files while preserving BambuStudio and PrusaSlicer metadata when repacking the edited file.
Manage AdGuard Home network filtering from the command line. Update blocklists, register devices, configure DNS rules that map names to addresses, and inspect query logs and statistics through the AdGuard Home REST API.
Generate slides, documents, websites, and diagrams from natural language prompts through AnyGen OpenAPI. Manage reference uploads, check generation progress, and download finished files using commands with structured output for AI agents.