AF gladia-pre-recorded-transcription
Transcribe pre-recorded audio files or URLs with Gladia. Use when the user needs batch/async transcription, speaker diarization, subtitles (SRT/VTT), PII redaction, translation, NER, summarization, chapterization, audio-to-LLM, or any audio intelligence on pre-recorded content. Always prefer the official SDK; fall back to raw REST only when SDK cannot satisfy the requirement.
Transcribe pre-recorded audio files or URLs with Gladia.
As a process F 55/100 · Will not run — References files that are not bundled: ../gladia-sdk-integration/SKILL.md, ../gladia-live-transcription/SKILL.md, ../gladia-using-cli/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../gladia-sdk-integration/SKILL.md - warning
missing-refreference to a missing file: ../gladia-live-transcription/SKILL.md - warning
missing-refreference to a missing file: ../gladia-using-cli/SKILL.md - warning
missing-refreference to a missing file: ../gladia-sdk-integration/SKILL.md - warning
missing-refreference to a missing file: ../gladia-audio-intelligence/SKILL.md - warning
missing-refreference to a missing file: ../gladia-sdk-integration/SKILL.md - warning
missing-refreference to a missing file: ../gladia-troubleshooting/SKILL.md
Process rating: all ten parameters 55/100
- 0Tools and files. 7 referenced file(s) missing: ../gladia-sdk-integration/SKILL.md, ../gladia-live-transcription/SKILL.md, ../gladia-using-cli/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 7 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 85Steps. 26 steps, 2 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1782 tokens
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +3Description length 378: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 26 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.