Best fit
Subtitle files can parse yet still ship overlapping cues, zero-length intervals, blank captions, or reading speeds that make the result unusable.
// Productivity
Subtitle Timeline QA
Flag malformed cue timing, overlaps, empty text, and excessive reading speed in a normalized subtitle timeline.
What problem does Subtitle Timeline QA solve?
Subtitle files can parse yet still ship overlapping cues, zero-length intervals, blank captions, or reading speeds that make the result unusable.
Use it to
- QA machine-generated captions before upload.
- Find overlapping subtitle cues.
- Review a localized track against a reading-speed threshold.
What it returns
- findings.csv with stable codes and record identifiers
- review-manifest.csv with every reviewed item
- result.json with READY, REVIEW, or BLOCK gate
- report.md with a human-readable decision handoff
A representative input and result
input {"cues":[{"id":"1","start_ms":0,"end_ms":2000,"text":"Welcome."}]}
result READY; one cue checked for order, duration, overlap, emptiness, and reading speed.
Access and approval boundaries
- Read access to one user-supplied local JSON evidence file.
- Write access only to the selected local output directory.
- No browser, network, credential, account, environment-variable, or external-action permission.
Known limitations
- Version 1 evaluates normalized cues and does not parse every vendor-specific styling extension.
- Reading speed thresholds are configurable review aids, not universal accessibility certification.
- It never changes wording or timing automatically.
// choose with context
Is Subtitle Timeline QA the right skill?
It returns
findings.csv with stable codes and record identifiers. review-manifest.csv with every reviewed item.
Do not use it as
Version 1 evaluates normalized cues and does not parse every vendor-specific styling extension.
Compatibility, access, version, and licence
- Reads or accesses
- Declared local scope: one owner-selected local JSON input, one owner-selected local output directory.
- Compatibility
- Normalized UTF-8 JSON input documented in the package. Python 3.10 or newer on Windows, macOS, or Linux. Local files only; no live account or provider connection.
- Version
- 1.0.0
- Licence
- Review the package licence and seller terms at the linked destination.
Questions
Does it change or upload anything?
No. It reads supplied local evidence and writes only to the selected output directory.
Is this an AI judgment?
No. The packaged checker is deterministic and applies documented rules to the supplied input.
What does a ready result mean?
It means no automated finding was produced. The responsible owner still reviews the original source and decides what to do.
How does malformed input behave?
Invalid JSON, duplicate identifiers, missing required arrays, and invalid core values fail closed.
Can I audit the result?
Yes. Every finding carries a stable code, record identifier, severity, source, and message.
Subtitle Timeline QA keeps proof and approval boundaries visible.
The listing includes the tested package, realistic samples, declared permissions, and known limitations.
Get Subtitle Timeline QA on Agensi