Youtube and Bilibili Subtitle Extraction and Summary
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill’s subtitle workflow is coherent, but it automatically uses Bilibili browser cookies and stores them locally, so users should review the account-access implications before installing.
Install only if you are comfortable letting the skill use yt-dlp and, for Bilibili, access Chrome login cookies and save them locally. Consider preinstalling a trusted yt-dlp version, setting a dedicated BILIBILI_COOKIES_FILE path with restricted permissions, and deleting the cookie file when finished.
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.
The skill may access and reuse the user’s Bilibili logged-in session, and the resulting cookie file could grant account access if exposed.
The skill directs the agent to read Bilibili login cookies from the user’s Chrome profile and store them in a local cookie file, even though the registry metadata declares no primary credential.
Bilibili subtitles require login cookies. Always use a cookies file — refresh from Chrome if missing or stale (>30 days): ... yt-dlp --cookies-from-browser chrome --cookies "$BILI_COOKIES"
Require explicit user approval before reading browser cookies, declare the credential requirement in metadata, store cookies in a clearly scoped/protected location, and document how to delete or rotate them.
A future or compromised yt-dlp/PyPI update could change behavior on the user’s machine.
The skill installs and updates an external package at runtime rather than relying on a pinned install specification. This is expected for subtitle extraction but introduces provenance and version drift risk.
if ! command -v yt-dlp &>/dev/null; then ... pip install -q yt-dlp || pip3 install -q yt-dlp ... fi yt-dlp -U --quiet 2>/dev/null || true
Prefer a reviewed, pinned yt-dlp version installed through an explicit install spec or ask the user before installing/updating packages.
The agent may prefer this workflow whenever it sees a matching URL, even if the user expected a simpler fetch or page-summary action.
The skill contains explicit routing instructions that override an alternative tool choice for a broad set of video URLs. This is aligned with the stated purpose, but users should know it affects agent behavior.
Triggers: ANY URL containing youtube.com, youtu.be, bilibili.com, or b23.tv — use this skill immediately, do NOT use fetch-content.
Narrow the trigger to explicit subtitle/summary requests or keep the override but ensure the agent asks before running commands or using cookies.