Run a mastering pass (LUFS loudness normalization + peak limiting) on an existing production
Scanned 9/2/2026
Install to Claude Code
npx -y skills add ruvnet/ruflo --skill music-master --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Music Master?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ruvnet-music-master)More formats (shields.io, HTML) on the badges page.
---
name: music-master
description: Run a mastering pass (LUFS loudness normalization + peak limiting) on an existing production
allowed-tools: mcp__cogmusic__master mcp__cogmusic__get_production mcp__plugin_ruflo-core_ruflo__memory_store
argument-hint: "<production-id>"
---
# Music Master
Applies loudness normalization (default target -14 LUFS, common streaming-platform standard) plus a peak limiter to an already-generated production.
## When to use
The user wants a "radio-ready" or streaming-normalized version of a track they've already generated.
## Steps
1. Call `mcp__cogmusic__master({ id: "<production-id>" })`.
2. The result includes `lufs_before` and `lufs_after` — report both so the user can see the actual loudness change, not just "done."
3. Update the cached entry in `music-productions` (if one exists) with the new `lufs_before`/`lufs_after`/`has_mastered: true` fields so later lookups don't need a round-trip.
4. Mastered audio isn't returned inline over MCP — point the user at the dashboard. See [ADR-0001](../../docs/adrs/0001-music-contract.md).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...