Quark Subtitle Rescue
Analysis
This skill has a clear subtitle-recovery purpose, but it asks the agent to run external Quark scripts with a Quark login cookie and bulk-change cloud folders, so users should review it carefully before installing.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Confirm tool root exists: `quark_subtitle_tool/`... Run: `python quark_subtitle_tool/batch_subtitle_runner.py`
The primary operational scripts live in a separate local tool directory, while the reviewed file manifest only includes the skill docs and scripts/report_progress.py. The code that performs the account-changing work is therefore outside the supplied artifact set.
User asks for **batch subtitles across many Quark subfolders**... If wrong-match batch is found, rollback before continuing.
The skill's intended workflow includes bulk cloud-folder mutation and rollback behavior. Although this matches the purpose, the artifacts do not clearly require dry-run mode or explicit user confirmation before uploads or rollback/delete actions.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Ensure config exists: `~/.config/quark_subtitle.json` with valid `cookie`.
This asks the agent to use a Quark account session cookie. That is high-impact account authority, especially because the workflow performs bulk uploads and rollback actions, and the registry metadata does not declare a credential or config-path requirement.