agentleFS
godot-fungodot-fun/gai/.agents/skills/audio-sample-rate-standardize/SKILL.md

audio-sample-rate-standardize

Skill210 starsChanged yesterdayMITView on GitHub

Standardizes a single audio file to 44100 or 48000 Hz and exports 16-bit PCM WAV using FFmpeg. Use when the user wants sample rate standardization, resample to 44.1 kHz or 48 kHz, WAV export at project sample rates, or mentions 44100, 48000, or PCM WAV conversion without loudness normalization.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When this skill applies, read and follow dependency-manager — run scripts as documented, install missing tools into .dependency/.

    line 12
  2. Very specific:

    Default output: <audio-dir>/audio-sample-rate-standardize/<name>.wav (source files are read-only):

    line 16
  3. Very specific:

    Use the bundled script, not hand-written -ar / -c:a commands.

    line 48
  4. Very specific:

    Do not use --output pointing at the source file.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audio Sample Rate Standardize

Export 16-bit PCM WAV at 44100 or 48000 Hz only. No loudness processing. Directories are not supported; run once per file to process a folder.

Rules

When this skill applies, read and follow dependency-manager — run scripts as documented, install missing tools into .dependency/.

Quick Start

Default output: <audio-dir>/audio-sample-rate-standardize/<name>.wav (source files are read-only):

.dependency/python/python .ai/audio-sample-rate-standardize/standardize.py --audio path/to/audio.mp3

Example: audio/sfx/tank/tank_move.mp3 → audio/sfx/tank/audio-sample-rate-standardize/tank_move.wav

Sample Rate Rule

Source rateOutput
≤ 44100 Hz44100 Hz
> 44100 Hz48000 Hz
RateTypical use
44100 HzMusic, games, CD
48000 HzGames, film, video

Common Flags

--audio · --output

.dependency/python/python .ai/audio-sample-rate-standardize/standardize.py --audio Audio/SFX/tank_move.mp3 --output Audio/SFX/out

Never overwrite source files. The script writes only to audio-sample-rate-standardize/ (or --output). All outputs are .wav regardless of input format. Supported inputs: .wav, .mp3, .ogg, .flac, .aac, .m4a, .wma.

Agent Notes

  1. Use the bundled script, not hand-written -ar / -c:a commands.
  2. No loudness normalization — LUFS targeting is a separate step in the audio pipeline.
  3. Missing Python/FFmpeg → populate .dependency/ per dependency-manager, retry same command.
  4. Do not copy, move, or replace the source with the output — tell the user where audio-sample-rate-standardize/ files are; they swap assets manually when ready.
  5. Do not use --output pointing at the source file; the script refuses paths that would overwrite the input.
  6. FFmpeg details: reference.md

Tests

From repo root:

.dependency/python/python .ai/audio-sample-rate-standardize/test_standardize.py

Manual CLI examples: cli/audio-sample-rate-standardize.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.