SRT Proofreader

Proofread SRT subtitles by using srts/source.md as terminology reference while preserving subtitle indices and timestamps. Use when users ask to proofread or...

Security Scan

The skill's files and runtime instructions are consistent with its stated purpose (proofreading SRTs using srts/source.md and splitting/merging large files); it requests no credentials or network access and includes a small, readable Node script for splitting/merging.

Purpose & Capability

The name/description (SRT proofreading with source.md terminology) matches the code and instructions: the included script only splits and merges .srt sections and the SKILL.md describes using git to track edits. There are no unrelated credentials, binaries, or external services requested.

Instruction Scope

SKILL.md restricts actions to the srts/ directory, requires srts/source.md, limits edits to typo/terminology changes, preserves indices/timestamps/structure, and instructs using git to review changes. It does not instruct reading unrelated system files or sending data externally. It does direct the agent to run git commands and to edit files — which is expected for this purpose.

Install Mechanism

No install spec (instruction-only) and the included script is shipped with the skill (low risk). One small mismatch: the skill's instructions invoke 'node scripts/srt_sections.mjs' but the registry metadata lists no required binaries; ensure Node.js is available in the runtime environment before using the split/merge features.

Credentials

The skill requests no environment variables, credentials, or config paths. All file access is limited to the srts/ workspace and the script writes a local manifest in the output directory.

Persistence & Privilege

The skill is not always-enabled and is user-invocable. It does not modify other skills or global agent configuration. It may initialize a git repository and commit inside srts/ (documented), which is expected behavior for producing git-tracked edits.

Assessment

This skill appears coherent and low-risk, but before installing: 1) verify Node.js is available if you plan to use the split/merge commands (the metadata doesn't list Node as a required binary); 2) back up your srts/ files (the skill will write files and may run git init and commit in that folder); 3) ensure srts/source.md exists and contains the terminology you want enforced; 4) review the included scripts/srt_sections.mjs yourself (it's small and readable) to confirm behavior; and 5) when running, inspect the git diff before pushing changes elsewhere. If you want stronger isolation, run the skill in a sandboxed workspace.

Execute the workflow in order. Keep edits minimal and deterministic.

1. Enter srts/

1. Change directory to the task's srts/ folder.
2. Stop and report if srts/ does not exist.

2. Ensure Git Baseline

1. Check whether srts/ is already inside a git repository.
2. If not inside a git repository:
   • run git init
   • run git add .
   • run git commit -m "init srt"
3. Do not rewrite existing history.

3. Require and Read source.md

1. Check whether srts/source.md exists.
2. If missing, stop immediately and tell the user: 还没有创建 source.md.
3. Read source.md before editing subtitles.
4. Extract terminology and proper nouns from source.md, then use them as authoritative wording.

4. Select the Main .srt File

1. List candidates in srts/ with:
   • extension .srt
   • filename not starting with . or _
2. Require exactly one candidate.
3. If zero candidates, stop and report.
4. If multiple candidates, stop and ask the user which file is the main subtitle file.

5. Handle Large Files (>400 lines)

1. Count lines in the main .srt.
2. If line count is <=400, edit directly.
3. If line count is >400:
   • split into section-001.srt, section-002.srt, ... using scripts/srt_sections.mjs
   • edit each section sequentially
   • merge sections back and overwrite the original main .srt using the same script
4. Use this script interface:
   • tool path: scripts/srt_sections.mjs
   • split: node scripts/srt_sections.mjs split --input <main.srt> --output <dir> --chunk 400
   • merge: node scripts/srt_sections.mjs merge --input-dir <dir> --output <main.srt>

6. Subtitle Editing Rules

1. Edit only typo-level text issues and term consistency.
2. Never modify subtitle sequence numbers.
3. Never modify timestamp lines (-->).
4. Preserve original line structure and blank-line boundaries.
5. Use source.md terminology as first priority.
6. Do not introduce new trailing punctuation on the final subtitle text line.

7. Final Verification

1. Review git diff and confirm index/timestamp lines are unchanged.
2. Confirm only subtitle text lines were modified.
3. Report completion with a short summary of corrected term categories.