subtitle-qc@1.0.0
CAUTIONPublisher claims: "Check and fix subtitle reading speed in SRT or WebVTT files — characters per second (CPS), line length, cue duration, gaps and overlaps — against Netflix-style limits (17 CPS Latin, 9 CPS Chinese/Japanese/Korean). Repairs timing first without changing a word, then proposes condensed text for what is left. Use when the user has an .srt or .vtt file and asks whether the subtitles are too fast, readable, Netflix/BBC compliant, flashing by, or need QC, retiming or cleanup; also for "字幕太快", "字幕质检", "字幕阅读速度", "检查字幕", "CPS". Not for creating subtitles from audio or video." Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-06 and scored it 70/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
No findings across 1,193 lines in 7 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim hypercube67-formal: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.