
Subtitle Packager
- 697 installs
- 19 repo stars
- Updated July 27, 2026
- postplusai/postplus-skills
subtitle-packager is a PostPlus media-production skill that converts normalized timed transcript JSON into SRT, ASS, and editor-ready caption packages without re-running speech-to-text.
About
subtitle-packager is a PostPlus skill in the Media and Creative Production family that packages an already-normalized timed transcript JSON into subtitle deliverables. It handles subtitle chunking, timing normalization, and export to SRT and ASS formats plus editor-ready caption bundles. The skill explicitly does not call speech-to-text or video analysis models, so it assumes stable transcript input from an upstream step. Developers and media engineers reach for subtitle-packager when caption timing and format conversion are the remaining work after transcription. It fits video pipelines, localization handoffs, and editor workflows where re-transcribing would waste compute and risk timing drift.
- Input boundary: stable normalized-transcript.json from audio- or video-transcription only
- Exports SRT and ASS with chunking, timing normalization, and readable caption packaging
- Explicit stop when timing is missing—no invented timestamps unless user requests heuristics
- Internal state under .postplus/subtitle-packager; final captions delivered outside .postplus
- Does not invoke speech-to-text or video analysis models
Subtitle Packager by the numbers
- 697 all-time installs (skills.sh)
- +42 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #341 of 1,335 Generative Media skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/postplusai/postplus-skills --skill subtitle-packagerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 697 |
|---|---|
| repo stars | ★ 19 |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 27, 2026 |
| Repository | postplusai/postplus-skills ↗ |
How do you export SRT and ASS from transcript JSON?
Turn an existing normalized timed transcript JSON into SRT, ASS, and editor-ready caption packages without re-running speech-to-text.
Who is it for?
Developers with a stable normalized timed transcript JSON who need SRT, ASS, or editor caption exports.
Skip if: Jobs that still need speech-to-text, video scene analysis, or raw audio transcription from scratch.
When should I use this skill?
A normalized timed transcript JSON exists and the task is subtitle chunking, timing normalization, or SRT/ASS packaging.
What you get
SRT files, ASS subtitle files, and editor-ready caption packages with normalized chunk timing.
- SRT files
- ASS subtitle files
- Editor-ready caption packages
By the numbers
- Exports to SRT and ASS subtitle formats
- Belongs to PostPlus media-production skill family
Files
Subtitle Packager
Use When
- A stable timed transcript already exists and the job is subtitle chunking,
SRT/ASS generation, readable caption packaging, or editor handoff.
- This skill packages transcripts. It must not call speech-to-text or video
analysis models.
Do Not Use When
- The task belongs to ideation, QA, or another released skill listed in the handoff section.
- Required inputs are missing and guessing would change the result.
Input Boundary
- Primary input is
normalized-transcript.jsonfromaudio-transcriptionor
video-transcription with stable timing.
- If timing is missing or invalid, stop and say so plainly. Do not invent timing
unless the user explicitly asks for heuristic timing.
- Preserve source transcript path, subtitle mode, output path, and source basis
in handoff notes or intermediate JSON.
Path And Handoff
- Keep chunking inputs, intermediate subtitle JSON, and render artifacts under
.postplus/subtitle-packager when they are internal state.
- Keep final user-facing
.srt,.ass, and editor handoff files outside
.postplus.
- Start with one normalized transcript before broader batch packaging.
- Return final subtitle paths, source transcript path, selected chunk mode, and
any profile path used.
Stop Conditions
- Stop when required user intent, source evidence, or owned input artifacts are
missing and guessing would change the result.
- If an owned CLI or script command fails, report the exact error and stop. Do
not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools.
Public Command Boundary
- Choose the smallest matching command or workflow from the user input and run
it directly.
- If an owned CLI or script command fails, report the exact error and stop. Do
not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools.
Related skills
How it compares
Use subtitle-packager after transcription is done; pick a speech-to-text skill first when no normalized transcript JSON exists.
FAQ
Does subtitle-packager run speech-to-text?
subtitle-packager does not run speech-to-text or video analysis models. The PostPlus skill expects a stable normalized timed transcript JSON and focuses on subtitle chunking, timing normalization, and exporting SRT, ASS, and editor-ready caption packages.
What subtitle formats does subtitle-packager output?
subtitle-packager outputs SRT and ASS subtitle files plus editor-ready caption packages from normalized transcript JSON. It is designed for handoff to video editors and players after upstream transcription is complete.
Is Subtitle Packager safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.