Skip to content
Back to skills

Music Master

ASecurity

Run a mastering pass (LUFS loudness normalization + peak limiting) on an existing production

  • 73,733 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 2, 2026
ai-agents

Works with

  • mcp

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add ruvnet/ruflo --skill music-master --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Music Master?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Music Master
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ruvnet-music-master/badge)](https://www.skillsdirectory.com/skills/ruvnet-music-master)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…