audio-transcription-workflow
Skill2 starsChanged 45 days agoMITView on GitHub
Transcribe local audio files or voice notes into markdown files using the legacy VoiceNote Bot workflow: local Whisper primary, OpenAI transcription fallback, and OpenRouter GPT-5 nano cleanup. Make sure to use this whenever the user wants audio files, voice recordings, dictations, interviews, or Telegram-style voice notes turned into markdown/text files without using Telegram, especially for batch folders or when they want the same cleanup behaviour as the old Telegram path.
- Reads credentials
In this repository41 other files it gives its agents.
- skills/web-asset-generator/CLAUDE.mdCLAUDE.md
- academic-writingSkill
- agent-os-childSkill
- agy-pSkill
- amazon-uk-scraperSkill
- artifact-variationsSkill
- capture-dashboardSkill
- claude-channelsSkill
- claude-pSkill
- code-documenterSkill
- context7-docsSkill
- context7-searchSkill
- deep-researchSkill
- docx-draftSkill
- grill-meSkill
- handoffSkill
- long-horizon-waiting-strategiesSkill
- openapi-schemaSkill
- opencode-pluginSkill
- pi-extensionSkill
- pi-web-ui-internal-api-orchestrationSkill
- pptx-draftSkill
- saas-idea-finderSkill
- scraping-redditSkill
- scraping-twitterSkill
- secret-scanningSkill
- socialmedia-optimizationSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- text-to-speechSkill
- thematic-analysisSkill
- transcribe-audioSkill
- video-deep-understandingSkill
- video-useSkill
- web-asset-generatorSkill
- web-crawlingSkill
- web-create-assetsSkill
- web-data-acquisitionSkill
- webfetch-skillSkill
- youtube-captionSkill
- youtube-searchSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill when the user wants to convert one or more local audio files into cleaned markdown transcripts using the same core workflow …
- Distinctive: line 22
Use this skill instead of a basic one-shot transcription skill when the user wants any of the following:
- Distinctive: line 26
cleanup/editing: after raw STT
- Distinctive: line 115
If the user explicitly wants no cleanup:
- Distinctive: line 142
Prefer a user-specified output directory.
- Distinctive: line 144
Run the bundled script.
- Very specific: line 145
Read the generated .md files if you need to summarise results back to the user.
- Very specific: line 155
If Whisper fails and OPENAI_API_KEY is missing, that file fails.
- Distinctive: line 156
If OpenRouter cleanup fails or no OpenRouter key can be resolved from the environment / shell startup file / optional legacy dotenv …
- Distinctive: line 162
After running the script, give a short operational summary such as:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Audio Transcription Workflow
Use this skill when the user wants to convert one or more local audio files into cleaned markdown transcripts using the same core workflow as a legacy voice-note transcription bot path, but without Telegram, webhooks, or queues.
What this skill does
For each input audio file, the bundled script:
- tries local Whisper first
- falls back to OpenAI transcription (
gpt-4o-mini-transcribeby default) if Whisper fails - runs OpenRouter cleanup with
openai/gpt-5-nanounless cleanup is explicitly skipped or the API key is unavailable - writes a markdown file with a YAML metadata header and the cleaned transcript body
- writes a
transcription_manifest.jsonsummary into the output directory
Prefer this skill over simpler transcription paths when
Use this skill instead of a basic one-shot transcription skill when the user wants any of the following:
- the same workflow as the old VoiceNote Bot
- markdown output files, not just inline text
- batch transcription of many files or a folder
- cleanup/editing after raw STT
- voice notes placed on disk rather than sent through Telegram
Inputs this skill accepts
- a single audio file
- multiple audio files
- a folder containing audio files
- a glob such as
/path/to/*.m4a - recursive folder traversal with
--recursive
Supported formats:
.oga,.ogg,.mp3,.m4a,.wav,.webm,.mp4,.mpeg,.mpga
Output format
Each transcript is saved as a .md file with a metadata header like this:
---
source_file: "note-01.oga"
source_path: "/absolute/path/note-01.oga"
generated_at: "2026-05-28T10:00:00+00:00"
workflow: "local_whisper_primary_openai_fallback_openrouter_cleanup"
language_requested: "auto"
transcription_provider: "whisper"
transcription_model: "local-whisper"
cleanup_applied: true
cleanup_provider: "openrouter"
cleanup_model: "openai/gpt-5-nano"
warnings: []
---The markdown body below the header is the transcript the user should read or reuse.
Bundled script
Use this script:
python3 ./skills/audio-transcription-workflow/scripts/transcribe_audio_to_markdown.py ...Common commands
Single file
python3 ./skills/audio-transcription-workflow/scripts/transcribe_audio_to_markdown.py \
/path/to/voice-note.oga \
--output-dir /path/to/outputMultiple files
python3 ./skills/audio-transcription-workflow/scripts/transcribe_audio_to_markdown.py \
/path/to/a.oga /path/to/b.m4a /path/to/c.wav \
--output-dir /path/to/outputFolder
python3 ./skills/audio-transcription-workflow/scripts/transcribe_audio_to_markdown.py \
/path/to/audio-folder \
--output-dir /path/to/outputRecursive folder
python3 ./skills/audio-transcription-workflow/scripts/transcribe_audio_to_markdown.py \
/path/to/audio-folder \
--recursive \
--output-dir /path/to/outputGlob input
python3 ./skills/audio-transcription-workflow/scripts/transcribe_audio_to_markdown.py \
'/path/to/audio/*.m4a' \
--output-dir /path/to/outputRaw transcript only
If the user explicitly wants no cleanup:
python3 ./skills/audio-transcription-workflow/scripts/transcribe_audio_to_markdown.py \
/path/to/audio-folder \
--output-dir /path/to/output \
--skip-cleanupEnvironment requirements
Expected environment variables:
WHISPER_URL— optional, defaults tohttp://localhost:9000/asrOPENAI_API_KEY— optional but needed for transcription fallbackOPENAI_TRANSCRIPTION_MODEL— optional, defaults togpt-4o-mini-transcribeOPENROUTER_API_KEY— optional but needed for legacy-style cleanup
The bundled script tries to work for low-context agents too.
- Credentials such as
OPENROUTER_API_KEYandOPENAI_API_KEYare resolved in this order: current process environment → a shell startup file such as~/.bashrcvia the shared credential loader → an optional legacy dotenv file pointed to byAUDIO_TRANSCRIPTION_LEGACY_ENVif you deliberately enable that fallback. WHISPER_URLstays simple: current process environment first, otherwise the script uses its built-in localhost default.
That means cleanup should usually work even when an agent has not been explicitly told where the OpenRouter key lives.
How to operate the skill
- Resolve the user's input path(s).
- Decide on an output directory.
- Prefer a user-specified output directory.
- Otherwise use a sensible local folder such as
./transcriptionsnear the current task context.
- Run the bundled script.
- Read the generated
.mdfiles if you need to summarise results back to the user. - Mention:
- where the markdown transcripts were saved
- whether any file used the OpenAI fallback
- whether cleanup was skipped or failed for any file
- where
transcription_manifest.jsonwas saved
Behaviour notes
- The script serialises Whisper access with a local file lock to avoid CPU-heavy concurrent Whisper requests.
- If Whisper fails and
OPENAI_API_KEYis missing, that file fails. - If OpenRouter cleanup fails or no OpenRouter key can be resolved from the environment / shell startup file / optional legacy dotenv fallback, the script still writes markdown using the raw transcript and records a warning in metadata and in the manifest.
WHISPER_URLis intentionally not pulled from any legacy dotenv fallback, because those files may contain hostnames that are wrong for direct host-side agent use.- Output file collisions are handled automatically by appending
-2,-3, and so on.
Good response pattern
After running the script, give a short operational summary such as:
- how many files were processed
- how many succeeded or failed
- output directory path
- whether cleanup matched the legacy path fully or had fallbacks/skips
Example user requests that should trigger this skill
- "Take these voice notes in
/path/to/meeting-notes/and turn them into markdown transcripts." - "Use the old Telegram transcription workflow on these
.ogafiles, but without Telegram." - "Batch transcribe all my interview
.m4afiles into markdown with cleanup." - "I dropped three audio files in Downloads — convert them into transcript markdown files."
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
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.

