Bilibili All In One
ReviewAudited by ClawScan on May 2, 2026.
Overview
The skill appears purpose-aligned for Bilibili tooling, but it can use full Bilibili session cookies, optionally store them, and publish or edit videos when explicitly confirmed.
Install only if you are comfortable giving the skill Bilibili session cookies for authenticated features. Prefer using it without credentials for read-only features, keep persistence disabled unless necessary, review publisher dry-runs before confirming, and use a throwaway/test Bilibili account for evaluation.
Findings (4)
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.
If the cookies are exposed or misused, another process could act as your Bilibili account.
The skill uses full Bilibili session cookies rather than narrowly scoped API keys; this is disclosed and purpose-aligned for publishing and high-quality downloads, but it grants meaningful account authority.
"credential_scope_warning": "These are Bilibili session cookies... could be replayed against Bilibili by other software. Use a test/throwaway account and rotate cookies after use."
Use a test account where possible, provide cookies only for features that need them, and rotate or revoke cookies after use.
If confirmed, the skill can publish or change videos on your Bilibili account.
The Publisher module can upload, schedule, draft, and edit Bilibili videos, which are account-mutating actions; the documentation includes a dry-run and explicit confirmation safeguard.
`upload` / `draft` / `schedule` / `edit` ... 默认只会返回预览 ... 必须显式传入 `dry_run=False` 并且 `confirm=True` 才会真正执行
Review dry-run previews carefully and only allow dry_run=false with confirm=true when you intend to perform the account change.
Persisted cookies can survive across sessions and could be reused if the local file is accessed by another process.
The skill can persist and later reload session cookies when persistence is enabled; the code also shows it is opt-in and includes permission and age checks.
DEFAULT_CREDENTIAL_FILE = ... ".credentials.json" ... elif self._persist and os.path.exists(self._credential_path): self._load_from_file(self._credential_path)
Leave BILIBILI_PERSIST disabled unless needed, keep the project directory private, and use auth.clear_persisted() or delete .credentials.json when finished.
Video merge operations may run a local ffmpeg binary on downloaded media files.
The downloader may invoke ffmpeg to merge video/audio streams; this is expected for video downloading and the code documents mitigations against shell injection.
the one subprocess call in this module (`ffmpeg`): ... We NEVER call `shell=True` ... resolve the ffmpeg binary once via `shutil.which("ffmpeg")`Use a trusted ffmpeg installation and keep downloads in a user-controlled output directory.