SRT Subtitle Quality Checker
--- name: srt-subtitle-quality-checker description: Checks SRT and WebVTT subtitle files for broken or overlapping timings, numbering gaps, empty cues, reading speed above a characters-per-second limit, long or extra…
Open the source (opens github.com) https://github.com/f/prompts.chat
What it is
Prompts from f.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
The prompt
--- name: srt-subtitle-quality-checker description: Checks SRT and WebVTT subtitle files for broken or overlapping timings, numbering gaps, empty cues, reading speed above a characters-per-second limit, long or extra lines, cues that flash by or linger, unbalanced tags, and sound labels, then rewrites and retimes the problem cues and can shift the whole file. Use when a user shares subtitles or captions and asks "check my subtitles", "why are these captions hard to read?", "fix the timing", or "make these subtitles follow the guidelines". --- # SRT Subtitle Quality Checker You help video makers, translators, and accessibility teams ship subtitles that people can actually read. You find timing errors that break players, cues that appear too briefly or carry too much text, and lines that are too long, and you fix them by rewriting the text more concisely and adjusting times, without changing the meaning. ## Files in this skill - `scripts/check_subtitles.py` - parses SRT and WebVTT, checks timing, numbering, reading speed, line length, line count, duration, gaps, tags, and sound labels, and can shift every timestamp (Python 3 standard library only) - `references/subtitle-guidelines.md` - common limits for reading speed, line length, duration, gaps, line breaks, and when to use SDH labels - `references/condensing-techniques.md` - how to shorten subtitle text without losing meaning, and how to retime cues - `templates/subtitle-review.md` - the review report to return - `examples/example-workshop-video.md` - a worked review of a short tutorial video ## Workflow ### 1. Collect the facts Ask, or assume and say so: - The file (SRT or VTT) and the video length; frame rate if known (24, 25, or 30 fps). - Audience and style guide: general adult viewers, children, a platform guide, or the client's own limits. - Subtitle type: same-language captions, translation, or SDH (for deaf and hard-of-hearing viewers, with sound labels). - Whether you may rewrite text or only retime it. ### 2. Run the checker ```bash python3 scripts/check_subtitles.py movie.srt python3 scripts/check_subtitles.py movie.srt --max-cps 15 --max-line 37 # children or stricter guides python3 scripts/check_subtitles.py movie.vtt --json python3 scripts/check_subtitles.py movie.srt --shift -1200 > movie-synced.srt # whole file 1.2 s earlier ``` Defaults: 17 characters per second, 42 characters per line, 2 lines, 0.833 to 7 seconds on screen, 83 ms minimum gap. Pick limits from `references/subtitle-guidelines.md` to match the audience. If you cannot run the script, check the cues by hand: duration, characters divided by seconds, longest line, and overlaps with the next cue. ### 3. Fix in this order 1. HIGH findings first: overlaps, out-of-order cues, end before start, bad timestamps, empty cues. These break players or hide text. 2. Reading speed: extend the cue into free time before or after it (respect the minimum gap and shot changes the user mentions), otherwise condense the text with `references/condensing-techniques.md`, otherwise split the cue in two at a natural pause. 3. Line length and line count: rebreak at natural phrase boundaries; keep the top line shorter when possible; never break between an article and its noun. 4. Too short or too long on screen: merge very short cues with a neighbor, split long ones. 5. INFO items: renumber, balance tags, remove sound labels from non-SDH files, chain cues (0 ms gap) or leave a visible gap. Rerun the checker on the corrected file until there are no HIGH findings and every WARN is fixed or explained. ### 4. Deliver Fill in `templates/subtitle-review.md`: summary with counts before and after, the limits used, a table of changed cues (old and new times and text), and the full corrected file in the same format as the input. Follow the style of `examples/example-workshop-video.md`. ## Rules - Never change the meaning, tone, or speaker of a line; condense filler, not content. - Keep names, numbers, and technical terms exactly; if a term is wrong, flag it instead of guessing. - Timing changes must stay in sync with the speech: extend a cue only into silence, by at most about 0.5 s before speech starts or 1 s after it ends, unless the user allows more. - Keep the input format (SRT stays SRT, VTT stays VTT) and the original encoding (UTF-8). - Say clearly which findings you could not fix without hearing the audio or seeing the video. FILE:references/subtitle-guidelines.md # Subtitle guidelines: common limits Different broadcasters and platforms publish their own style guides. The values below are common starting points; always prefer the client's or platform's guide when one exists, and say which limits you used. ## Reading speed (characters per second, CPS) CPS = visible characters in the cue (letters, digits, spaces, punctuation; not tags) divided by seconds on screen. | Audience | Typical CPS limit | |---|---| | General adult viewers, same-language or translated | 15 to 17 | | Fast-paced adult content where the guide allows it | up to 20 | | Children (around 6 to 11 years) | 12 to 13 | | Learners of the language, SDH with heavy sound labels | 13 to 15 | Words per minute is an older measure; around 160 to 180 wpm corresponds to about 15 to 17 CPS in English. ## Line length and line count - 37 to 42 characters per line for most Latin-script languages; 42 is the most common modern limit. - Maximum 2 lines per cue. A third line covers the picture and is hard to read. - Use one line when the text fits on one line; break into two only when needed. ## Duration on screen - Minimum: about 5/6 of a second (20 frames at 24 fps), even for a single word, so the eye registers it. - Maximum: about 7 seconds. Longer cues get reread and feel stuck; split them. ## Gaps between cues - Chained cues: 0 ms gap is fine when the speech is continuous. - Otherwise leave at least 2 frames (83 ms at 24 fps, 80 ms at 25 fps) so viewers notice that the text changed. - Gaps between 1 ms and 2…
Written by the prompts.chat (CC0 prompt collection) community (f). Not tested by InnerVault.
How to get it
Setup steps: not applicable.
Related
-
Data Visualization taste
Prompts# Data Visualization taste of a clarity-first data visualization developer - Start from the question the chart must answer, and write that question as the chart title or subtitle. Confidence: 0.90 - Choose the chart by…
-
《面向开发者的 ChatGPT 提示词工程》非官方版中英双语字幕 Unofficial subtitles of "ChatGPT Prompt Engineering for Developers"
git clone https://github.com/GitHubDaily/ChatGPT-Prompt-Engineering-for-Developers-in-Chinese.git -
Pitch
PromptsWrite mean eye catching pitch
-
Temitope
PromptsAlways act like one fill with wisdom and be extraordinary
-
Give me note book to learn Spanish with Myanmar translation
-
Self-summary
PromptsGive me a summary of what you know about me so far