Milystudio transcribe media
Skill Mily-Labs/agent-skills/plugins/milystudio-studio/skills/milystudio-transcribe-media
Transcribe and align speech in MilyStudio with local engines. Use for transcripts, word timing, diarization, searchable dialogue, or subtitle preparation.From its SKILL.md
npx -y skills add Mily-Labs/agent-skills --skill milystudio-transcribe-mediaAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 192 tokens by cl100k_base, as published. Nobody here has run it
milystudio-transcribe-media
Operate through the MilyStudio project, action, and job interfaces. Inspect capabilities before choosing commands because editor features may vary by installed release.
Workflow
- Inspect audio quality, languages, speakers, duration, and available local engines.
- Choose model, language, diarization, and alignment settings without sending media to a cloud by default.
- Run a cancellable transcription job and retain engine/version metadata.
- Review low-confidence regions, speaker changes, word timing, and source sync.
Guardrails
- Never edit project JSON, the UI store, or generated manifests directly when a typed action exists.
- Keep original media read-only and write only inside the active project artifact directories.
- Use dry-run before mutation, include the expected project revision, and stop on conflicts.
- Record assumptions, action IDs, job IDs, resulting revision, validation evidence, and unresolved risks.
What ships with it: 1 file
208 B alongside SKILL.md
agents/
- openai.yaml208 B
Gives 0 of the 12 instructions most media documents skills give in 192 tokens
Counted across 157 of the 158 authors here whose files we hold, read 2026-08-07
- Provide posting time recommendationsin 7 of 157, across 5 files
- Track metrics over time to identify trendsin 6 of 157, across 2 files
- Read marketing context file before startingin 6 of 157, across 5 files
- Choose platforms based on audience presencein 6 of 157, across 4 files
- Adapt tone for each platformin 6 of 157, across 4 files
- Ensure data completeness before analysisin 5 of 157, across 1 file
- Compare metrics within same time periodsin 5 of 157, across 1 file
- Account for platform-specific benchmarksin 5 of 157, across 1 file
- Separate organic and paid metricsin 5 of 157, across 1 file
- Include context when interpreting resultsin 5 of 157, across 1 file
- Keep tweets under 280 charactersin 5 of 157, across 3 files
- Download top-K results with an attribution sidecarin 5 of 157, across 2 files
Said here and by no other author read
- inspect capabilities before choosing commands
- inspect audio quality languages and engines
- choose transcription settings locally by default
- run a cancellable transcription job
- retain engine and version metadata
- review low-confidence regions and speaker changes
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.