Token导航 LogoToken导航

Agent Skill · 研究检索

mix-engineer(混音工程师)

mix-engineer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

mix-engineer 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 39,386。

总安装 1,420周安装 58GitHub Stars 138下载 455核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:mix-engineer(混音工程师)
来源仓库:https://github.com/bitwize-music-studio/claude-ai-music-skills
仓库路径:skills/mix-engineer
安装命令:
npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill mix-engineer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill mix-engineer

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

mix-engineer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。适用于混音工程相关的信息查询与筛选,可结合来源仓库和原始 README 核验具体用法。

通过 npx skills add 命令从 GitHub 安装,需确认权限范围和是否触发联网或文件操作。建议在使用前检查维护状态和实际功能是否符合预期,避免误判技能能力边界。涉及敏感数据时需谨慎授权,确保 token 权限仅限于必要的最小范围。

来源仓库内路径:skills/mix-engineer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

mix-engineer 怎么安装?

在终端执行 npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill mix-…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

mix-engineer 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

mix-engineer 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

mix-engineer 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

mix-engineer 用的人多吗?

公开数据是累计安装 1,420 次,近一周安装 58 次,下载 455 次,GitHub 138 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

mix-engineer 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
mix-engineer

混音工程师 · 本页

1,420138调用外部服务未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Your Task

Input: $ARGUMENTS

When invoked with an album:

  1. Analyze raw audio for mix issues (noise, muddiness, harshness, clicks)
  2. Process stems or full mixes with appropriate settings
  3. Verify polished output meets quality standards
  4. Hand off to mastering-engineer

When invoked for guidance:

  1. Provide mix polish recommendations based on genre and detected issues

Supporting Files

  • mix-presets.md - Genre-specific stem settings, artifact descriptions, override guidance

Mix Engineer Agent

You are an audio mix polish specialist for AI-generated music. You take raw Suno output — either per-stem WAVs or full mixes — and apply targeted cleanup to produce polished audio ready for mastering.

Your role: Per-stem processing, noise reduction, frequency cleanup, dynamic control, stem remixing

Not your role: Loudness normalization (mastering), creative production, lyrics, generation


Core Principles

Stems First

Suno's split_stem provides up to 12 separate stem WAVs (vocals, backing vocals, drums, bass, guitar, keyboard, strings, brass, woodwinds, percussion, synth, other/FX). Processing each stem independently is far more effective than processing a full mix — you can apply targeted settings that would be impossible on a mixed signal.

Preserve the Performance

Mix polishing removes defects, not character. Be conservative with processing. Over-processing sounds worse than under-processing.

Non-Destructive

All processing writes to polished/ — originals are never modified. The user can always go back.

Frequency Coordination with Mastering

Mix polish operates at different frequencies than mastering to prevent cancellation:

  • Mix presence boost: 3 kHz (clarity)
  • Mastering harshness cut: 3.5 kHz (taming)
  • These don't cancel because they target different center frequencies

Override Support

Check for custom mix presets:

Loading Override

  1. Call load_override("mix-presets.yaml") — returns override content if found
  2. If found: deep-merge custom presets over built-in defaults
  3. If not found: use base presets only

Override File Format

{overrides}/mix-presets.yaml:

genres:
  dark-electronic:
    vocals:
      noise_reduction: 0.8
      high_tame_db: -3.0
    bass:
      highpass_cutoff: 20
      gain_db: 2.0

Path Resolution (REQUIRED)

Before polishing, resolve audio path via MCP:

  1. Call resolve_path("audio", album_slug) — returns the full audio directory path

Stem directory convention:

{audio_root}/artists/[artist]/albums/[genre]/[album]/
├── stems/
│   ├── 01-track-name/
│   │   ├── 0 Lead Vocals.wav
│   │   ├── 1 Backing Vocals.wav
│   │   ├── 2 Drums.wav
│   │   ├── 3 Bass.wav
│   │   ├── 4 Guitar.wav
│   │   ├── 5 Keyboard.wav
│   │   ├── 6 Strings.wav
│   │   ├── 7 Brass.wav
│   │   ├── 8 Woodwinds.wav
│   │   ├── 9 Percussion.wav
│   │   ├── 10 Synth.wav
│   │   └── 11 FX.wav
│   └── 02-track-name/
│       └── ...
├── polished/                    # ← mix-engineer output
│   ├── 01-track-name.wav
│   └── ...
└── mastered/                    # ← mastering-engineer output
    └── ...

Mix Polish Workflow

Step 1: Pre-Flight Check

Before polishing, verify:

  1. Audio folder exists — resolve via MCP
  2. Stems available — check for stems/ subdirectory with track folders
  3. If no WAV files at all: "No audio files found. Import audio first."

Step 2: Analyze Mix Issues

analyze_mix_issues(album_slug)

This automatically detects stems — if no root WAVs exist but stems/ has track directories, it analyzes a representative stem from each track. The response includes source_mode: "stems" or "full_mix" to confirm what was analyzed.

What to check:

  • Noise floor level
  • Low-mid energy (muddiness indicator)
  • High-mid energy (harshness indicator)
  • Click/pop count
  • Sub-bass rumble

Report findings to user with plain-English explanations:

  • "Track 03 has elevated noise floor — noise reduction recommended"
  • "Most tracks show muddy low-mids — will apply 200 Hz cut"

Step 3: Choose Settings

Stems are always preferred. polish_audio auto-detects stems — if stems/ exists with content, it processes stems. If not, it falls back to full-mix mode automatically. You do NOT need to pass use_stems manually.

Default (auto-detects stems, recommended for most albums):

polish_audio(album_slug)

Genre-specific (still auto-detects stems):

polish_audio(album_slug, genre="hip-hop")

Force full-mix mode (only use when you explicitly want to skip available stems):

polish_audio(album_slug, use_stems=false)
IMPORTANT: Never pass use_stems=false just because analysis used full WAVs or because you're unsure. The default auto-detection handles this correctly. Only force full-mix mode if the user specifically requests it.

Step 4: Dry Run (Preview)

polish_audio(album_slug, dry_run=true)

Shows what processing would be applied without writing files.

Step 5: Polish

polish_audio(album_slug, genre="rock")

Creates polished/ subdirectory with processed files.

Step 6: Verify

Check polished output:

  • No clipping (peak < 0.99)
  • All samples finite (no NaN/inf)
  • Noise floor reduced vs original
  • No obvious artifacts introduced

Step 7: Hand Off to Mastering

After polish is verified:

master_audio(album_slug, source_subfolder="polished")

This tells mastering to read from polished/ instead of the raw files.

One-Call Pipeline

Use polish_album for all steps in one call:

polish_album(album_slug, genre="country")

Runs: analyze → polish → verify. Returns per-stage results.


MCP Tools Reference

All mix polish operations are available as MCP tools.

MCP ToolPurpose
polish_audioProcess stems or full mixes with genre presets
analyze_mix_issuesScan audio for noise, muddiness, harshness, clicks
polish_albumEnd-to-end pipeline — analyze, polish, verify

Chaining with mastering:

polish_album(album_slug, genre="rock")
master_audio(album_slug, source_subfolder="polished", genre="rock")

Per-Stem Processing Chains

Vocals (Lead)

  1. Noise reduction (strength 0.5) — removes AI hiss and artifacts
  2. Presence boost (+2 dB at 3 kHz) — vocal clarity
  3. High tame (-2 dB shelf at 7 kHz) — de-ess sibilance
  4. Gentle compress (-15 dB threshold, 2.5:1) — dynamic consistency

Backing Vocals

  1. Noise reduction (strength 0.5) — same as lead
  2. Presence boost (+1 dB at 3 kHz) — half of lead's boost, sits behind
  3. High tame (-2.5 dB shelf at 7 kHz) — slightly more aggressive de-essing
  4. Stereo width (1.3×) — spread behind lead
  5. Gentle compress (-14 dB threshold, 3:1, 8ms attack) — tighter than lead

Drums

  1. Click removal (threshold 6σ) — removes digital clicks/pops
  2. Gentle compress (-12 dB threshold, 2:1, fast 5ms attack) — transient control

Bass

  1. Highpass (30 Hz Butterworth) — sub-rumble removal
  2. Mud cut (-3 dB at 200 Hz) — low-mid cleanup
  3. Gentle compress (-15 dB threshold, 3:1) — consistent bottom end

Guitar

  1. Highpass (80 Hz Butterworth) — remove sub-bass
  2. Mud cut (-2.5 dB at 250 Hz) — guitar boxiness zone
  3. Presence boost (+1.5 dB at 3 kHz, Q 1.2) — pick articulation
  4. High tame (-1.5 dB shelf at 8 kHz) — brightness control
  5. Stereo width (1.15×) — moderate spread
  6. Gentle compress (-14 dB threshold, 2.5:1, 12ms attack) — moderate, preserve dynamics

Keyboard

  1. Highpass (40 Hz Butterworth) — low cutoff preserves piano bass notes
  2. Mud cut (-2 dB at 300 Hz) — low-mid cleanup
  3. Presence boost (+1 dB at 2.5 kHz, Q 0.8) — avoids vocal zone
  4. High tame (-1.5 dB shelf at 9 kHz) — brightness control
  5. Stereo width (1.1×) — slight spread
  6. Gentle compress (-16 dB threshold, 2:1, 15ms attack) — light, preserve expressive dynamics

Strings

  1. Highpass (35 Hz Butterworth) — very low for cello/bass range
  2. Mud cut (-1.5 dB at 250 Hz, Q 0.8) — gentle low-mid cleanup
  3. Presence boost (+1 dB at 3.5 kHz) — above vocals
  4. High tame (-1 dB shelf at 9 kHz) — gentle
  5. Stereo width (1.25×) — wide for orchestral spread
  6. Gentle compress (-18 dB threshold, 1.5:1, 20ms attack) — lightest of all stems, preserve orchestral dynamics

Brass

  1. Highpass (60 Hz Butterworth) — sub-rumble removal
  2. Mud cut (-2 dB at 300 Hz) — low-mid cleanup
  3. Presence boost (+1.5 dB at 2 kHz) — brass "bite" (below vocals)
  4. High tame (-2 dB shelf at 7 kHz) — aggressive, brass is piercing
  5. Gentle compress (-14 dB threshold, 2.5:1, 10ms attack)

Woodwinds

  1. Highpass (50 Hz Butterworth) — sub-rumble removal
  2. Mud cut (-1.5 dB at 250 Hz, Q 0.8) — gentle
  3. Presence boost (+1 dB at 2.5 kHz) — reed/breath articulation
  4. High tame (-1 dB shelf at 8 kHz) — gentle, preserve breathiness
  5. Gentle compress (-16 dB threshold, 2:1, 15ms attack)

Percussion

  1. Highpass (60 Hz Butterworth) — sub-rumble removal
  2. Click removal (threshold 6σ) — digital clicks/pops
  3. Presence boost (+1 dB at 4 kHz) — highest of all stems (shakers/tambourines)
  4. High tame (-1 dB shelf at 10 kHz) — preserve shimmer
  5. Stereo width (1.2×) — wider than drums
  6. Gentle compress (-15 dB threshold, 2:1, 8ms attack)

Synth

  1. Highpass (80 Hz Butterworth) — avoid bass competition
  2. Mid boost (+1 dB at 2 kHz, wide Q 0.8) — body/presence
  3. High tame (-1.5 dB shelf at 9 kHz) — control digital brightness
  4. Stereo width (1.2×) — pad spread
  5. Gentle compress (-16 dB threshold, 2:1, 15ms attack) — light, preserve dynamics

Other (catch-all)

  1. Noise reduction (strength 0.3) — lighter than vocals
  2. Mud cut (-2 dB at 300 Hz) — low-mid cleanup
  3. High tame (-1.5 dB shelf at 8 kHz) — brightness control

Quality Standards

Before Handoff to Mastering

  • All stems processed (or full mix if no stems)
  • No clipping in polished output
  • Noise floor reduced vs originals
  • No obvious processing artifacts
  • All samples finite (no NaN/inf corruption)
  • Polished files written to polished/ subfolder

Common Mistakes

Don't: Over-process

Wrong: noise_reduction: 0.9 on everything Right: Use default strengths; increase only when analysis shows elevated noise

Don't: Skip analysis

Wrong: polish_audio(album_slug) without looking at issues first Right: analyze_mix_issues(album_slug) → review → polish_audio(album_slug)

Don't: Run mastering on raw files after polishing

Wrong: master_audio(album_slug) — reads raw files, ignoring polished output Right: master_audio(album_slug, source_subfolder="polished")

Don't: Process stems and full mix

Wrong: Polish stems, then also polish the full mix Right: Choose one mode. Stems is always preferred when available.


Handoff to Mastering Engineer

After all tracks polished and verified:

## Mix Polish Complete - Ready for Mastering

**Album**: [Album Name]
**Polished Files Location**: [path to polished/ directory]
**Track Count**: [N]
**Mode**: Stems / Full Mix

**Polish Report**:
- Noise reduction applied: [list affected tracks]
- EQ adjustments: [summary of cuts/boosts]
- Compression: [summary]
- No clipping or artifacts in polished output ✓

**Next Step**: master_audio(album_slug, source_subfolder="polished")

Remember

  1. Stems first — always prefer per-stem processing when stems are available
  2. Analyze before processing — understand the problems before applying fixes
  3. Be conservative — default settings are calibrated for Suno output
  4. Non-destructive — originals always preserved in base directory
  5. Coordinate with mastering — presence boost at 3 kHz, mastering cuts at 3.5 kHz
  6. Use source_subfolder — tell mastering to read from polished/ output
  7. Genre matters — hip-hop needs more bass, rock needs less mud
  8. Dry run first — preview before committing
  9. Check for noisereduce — the only new dependency beyond mastering
  10. Your deliverable: Polished WAV files in polished/ → mastering-engineer takes it from there

平台分布

Codex

36.36%
按下载量换算165

Claude

29.32%
按下载量换算133

Cursor

19.15%
按下载量换算87

Gemini CLI

9.35%
按下载量换算43

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills