acestep-lyrics-transcription
Skill0 starsChanged 7 months agoMITView on GitHub
Transcribe audio to timestamped lyrics using OpenAI Whisper or ElevenLabs Scribe API. Outputs LRC, SRT, or JSON with word-level timestamps. Use when users want to transcribe songs, generate LRC files, or extract lyrics with timestamps from audio.
3 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- sdbds/ACE-Step-1.5-for-windowsword for word, first seen Oct 8, 2026
- ace-step/ACE-Step-1.5word for word, first seen Oct 8, 2026
- ace-step/ace-step-skillsword for word, first seen Feb 13, 2026
Other versions3 projects use a version of this.
Word for word · 3
- ace-step/ACE-Step-1.5★ 13k100% same
- sdbds/ACE-Step-1.5-for-windows★ 101100% same
- ace-step/ace-step-skills★ 91100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- acestep-docsSkill
- acestep-lyrics-transcriptionSkill
- acestep-simplemvSkill
- acestepSkill
- acestep-songwritingSkill
- acestep-thumbnailSkill
- acestep-docsSkill
- acestep-simplemvSkill
- acestepSkill
- acestep-songwritingSkill
- acestep-thumbnailSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Very specific: line 23
Use AskUserQuestion to ask the user to provide their API key, with the following options and guidance:
- Distinctive: line 34
If the user wants to switch providers, also run:
- Very specific: line 38
After configuring, re-run config --check-key to verify the key is set before proceeding.
- Distinctive: line 80
CRITICAL: After transcription, you MUST manually correct the LRC file before using it for MV rendering.
- Very specific: line 97
Keep all [MM:SS.cc] timestamps exactly as-is (timestamps from transcription are accurate)
- Very specific: line 98
Do NOT add structure tags like [Verse] or [Chorus] — the LRC should only have timestamped text lines
≈ “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.
Files
Lyrics Transcription Skill
Transcribe audio files to timestamped lyrics (LRC/SRT/JSON) via OpenAI Whisper or ElevenLabs Scribe API.
API Key Setup Guide
Before transcribing, you MUST check whether the user's API key is configured. Run the following command to check:
cd "{project_root}/{.claude or .codex}/skills/acestep-lyrics-transcription/" && bash ./scripts/acestep-lyrics-transcription.sh config --check-keyThis command only reports whether the active provider's API key is set or empty — it does NOT print the actual key value. NEVER read or display the user's API key content. Do not use config --get on key fields or read config.json directly. The config --list command is safe — it automatically masks API keys as *** in output.
If the command reports the key is empty, you MUST stop and guide the user to configure it before proceeding. Do NOT attempt transcription without a valid key — it will fail.
Use AskUserQuestion to ask the user to provide their API key, with the following options and guidance:
- Tell the user which provider is currently active (openai or elevenlabs) and that its API key is not configured. Explain that transcription cannot proceed without it.
- Provide clear instructions on where to obtain a key:
- OpenAI: Get an API key at https://platform.openai.com/api-keys — requires an OpenAI account with billing enabled. The Whisper API costs ~$0.006/min.
- ElevenLabs: Get an API key at https://elevenlabs.io/app/settings/api-keys — requires an ElevenLabs account. Free tier includes limited credits.
- Also offer the option to switch to the other provider if they already have a key for it.
- Once the user provides the key, configure it using:
cd "{project_root}/{.claude or .codex}/skills/acestep-lyrics-transcription/" && bash ./scripts/acestep-lyrics-transcription.sh config --set <provider>.api_key <KEY> - If the user wants to switch providers, also run:
cd "{project_root}/{.claude or .codex}/skills/acestep-lyrics-transcription/" && bash ./scripts/acestep-lyrics-transcription.sh config --set provider <provider_name> - After configuring, re-run
config --check-keyto verify the key is set before proceeding.
If the API key is already configured, proceed directly to transcription without asking.
Quick Start
# 1. cd to this skill's directory
cd {project_root}/{.claude or .codex}/skills/acestep-lyrics-transcription/
# 2. Configure API key (choose one)
./scripts/acestep-lyrics-transcription.sh config --set openai.api_key sk-...
# or
./scripts/acestep-lyrics-transcription.sh config --set elevenlabs.api_key ...
./scripts/acestep-lyrics-transcription.sh config --set provider elevenlabs
# 3. Transcribe
./scripts/acestep-lyrics-transcription.sh transcribe --audio /path/to/song.mp3 --language zh
# 4. Output saved to: {project_root}/acestep_output/<filename>.lrcPrerequisites
- curl, jq, python3 (or python)
- An API key for OpenAI or ElevenLabs
Script Usage
./scripts/acestep-lyrics-transcription.sh transcribe --audio <file> [options]
Options:
-a, --audio Audio file path (required)
-l, --language Language code (zh, en, ja, etc.)
-f, --format Output format: lrc, srt, json (default: lrc)
-p, --provider API provider: openai, elevenlabs (overrides config)
-o, --output Output file path (default: acestep_output/<filename>.lrc)Post-Transcription Lyrics Correction (MANDATORY)
CRITICAL: After transcription, you MUST manually correct the LRC file before using it for MV rendering. Transcription models frequently produce errors on sung lyrics:
- Proper nouns: "ACE-Step" → "AC step", "Spotify" → "spot a fly"
- Similar-sounding words: "arrives" → "eyes", "open source" → "open sores"
- Merged/split words: "lighting up" → "lightin' nup"
Correction Workflow
- Read the transcribed LRC file using the Read tool
- Read the original lyrics from the ACE-Step output JSON file
- Use original lyrics as a whole reference: Do NOT attempt line-by-line alignment — transcription often splits, merges, or reorders lines differently from the original. Instead, read the original lyrics in full to understand the correct wording, then scan each LRC line and fix any misrecognized words based on your knowledge of what the original lyrics say.
- Fix transcription errors: Replace misrecognized words with the correct original words, keeping the timestamps intact
- Write the corrected LRC back using the Write tool
What to Correct
- Replace misrecognized words with their correct original versions
- Keep all
[MM:SS.cc]timestamps exactly as-is (timestamps from transcription are accurate) - Do NOT add structure tags like
[Verse]or[Chorus]— the LRC should only have timestamped text lines
Example
Transcribed (wrong):
[00:46.96]AC step alive,
[00:50.80]one point five eyes.Original lyrics reference:
ACE-Step alive
One point five arrivesCorrected (right):
[00:46.96]ACE-Step alive,
[00:50.80]One point five arrives.Configuration
Config file: scripts/config.json
# Switch provider
./scripts/acestep-lyrics-transcription.sh config --set provider openai
./scripts/acestep-lyrics-transcription.sh config --set provider elevenlabs
# Set API keys
./scripts/acestep-lyrics-transcription.sh config --set openai.api_key sk-...
./scripts/acestep-lyrics-transcription.sh config --set elevenlabs.api_key ...
# View config
./scripts/acestep-lyrics-transcription.sh config --list| Option | Default | Description |
provider | openai | Active provider: openai or elevenlabs |
output_format | lrc | Default output: lrc, srt, or json |
openai.api_key | "" | OpenAI API key |
openai.api_url | https://api.openai.com/v1 | OpenAI API base URL |
openai.model | whisper-1 | OpenAI model (whisper-1 for word timestamps) |
elevenlabs.api_key | "" | ElevenLabs API key |
elevenlabs.api_url | https://api.elevenlabs.io/v1 | ElevenLabs API base URL |
elevenlabs.model | scribe_v2 | ElevenLabs model |
Provider Notes
| Provider | Model | Word Timestamps | Pricing |
| OpenAI | whisper-1 | Yes (segment + word) | $0.006/min |
| ElevenLabs | scribe_v2 | Yes (word-level) | Varies by plan |
- OpenAI
whisper-1is the only OpenAI model supporting word-level timestamps - ElevenLabs
scribe_v2returns word-level timestamps with type filtering - Both support multilingual transcription
Examples
# Basic transcription (uses config defaults)
./scripts/acestep-lyrics-transcription.sh transcribe --audio song.mp3
# Chinese song to LRC
./scripts/acestep-lyrics-transcription.sh transcribe --audio song.mp3 --language zh
# Use ElevenLabs, output SRT
./scripts/acestep-lyrics-transcription.sh transcribe --audio song.mp3 --provider elevenlabs --format srt
# Custom output path
./scripts/acestep-lyrics-transcription.sh transcribe --audio song.mp3 --output ./my_lyrics.lrcDoes 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
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.

