SRT Proofreader
v1.0.0Proofread SRT subtitles by using srts/source.md as terminology reference while preserving subtitle indices and timestamps. Use when users ask to proofread or...
⭐ 0· 364·0 current·0 all-time
by@kapiai
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & 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.Like a lobster shell, security has layers — review code before you run it.
latestvk972m7mcbz0p5vbz94vwzkzj0182md0t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.