This document exhaustively declares every network destination, credential touchpoint, subprocess, and deletion this skill can perform, so that users and automated security reviewers can verify the claims against the code.

TL;DR: the core pipeline (HTML design → render → MP4/PDF/PPTX export) runs 100% locally with zero network calls and zero API keys. All cloud-touching code is isolated in scripts/cloud/, is strictly optional, uses only keys you supply, sends data only to the corresponding vendor's official API, and refuses to run without explicit consent (--yes flag or HUASHU_CLOUD_OK=1). There is no telemetry. No data is ever sent to any server controlled by the skill author.

That is the entire list. grep -rn "https://" --include="*.py" --include="*.mjs" --include="*.js" --include="*.sh" scripts/ to verify.

• No key is hardcoded anywhere; the repo ships only .env.example placeholders (.env is gitignored).
• Keys are read from the skill's own root .env or process environment — never from files elsewhere on your machine. ai-review-video.py extracts only the single ARK_API_KEY variable; it does not load the rest of the file into the environment.
• Keys are transmitted exclusively to the corresponding vendor's official endpoint listed above, over HTTPS, as auth headers.
• references/react-setup.md option B (pasting an Anthropic key into a demo page input) is explicitly marked local-demo-only and not recommended; the default options require no key at all.

Both cloud scripts print exactly what will be sent to which host and exit before any network call unless you pass --yes or set HUASHU_CLOUD_OK=1. Everything else in this skill never needs the gate because it never leaves your machine.

All subprocess calls invoke local media tools only: ffmpeg, ffprobe, ffplay, Playwright/Chromium for HTML rendering and screenshots. No shell-to-network combinations, no curl-pipe-sh patterns.

Recursive deletion is limited to temp directories the scripts themselves create with unique timestamp+PID names (.video-tmp-*, .seek-tmp-*, _narration/.tmp, Python tempfile.TemporaryDirectory). No script ever deletes user data or anything outside its own scratch space.

Mainstream registry packages only (playwright, sharp, pptxgenjs, pdf-lib, requests), installed via standard npm/pip/uv — no binary downloads from arbitrary URLs. One documented exception to be aware of: npx hyperframes init (optional animation backend, see references/hyperframes-backend.md) installs 19 hyperframes documentation skills into ~/.claude/skills/. This is called out with a warning in the docs before the command.

scripts/design-gate-hook.sh is never installed automatically — nothing in this skill writes to settings.json. If you manually opt in, its entire behavior is: block long-video render commands (exit 2) until a design-approval file exists. It makes no network calls, writes nothing, deletes nothing.

fetch_images.py and ai-review-video.py disable inheriting proxy environment variables (trust_env = False / clearing ALL_PROXY etc.) for their own requests. This exists to survive stale local proxy configurations that break TLS — not to evade monitoring. If you need these requests to go through your proxy, set it explicitly in the script invocation.

Found something that contradicts this document? Please open an issue — a mismatch between this file and the code is treated as a bug.