MediaKit video tools: 30 video processing commands

Prerequisites: mediakit-cli installed (check the shared skill's preflight checks first); a Volcengine account with auth configured for Cloud-mode tools; real input media files before asking for parameters; an agent able to read Chinese (the skill text is written in Chinese) Install "MediaKit video tools: 30 video processing commands" for me. The MediaKit video playbook: 30 video-domain tools over the mediakit-cli binary — AI upscaling and restoration, smart transcoding and remux, quality assessment, frame extraction, invisible watermarking, scene and semantic segmentation, storyline analysis, highlight reels, marketing recaps, ASR subtitles, subtitle OCR and erasure, face blur, portrait and greenscreen matting, metadata probing — each with its Cloud/Local mode, command and reference doc; includes hard usage rules (read the shared skill first, never fabricate parameters, set MEDIAKIT_SURFACE=skill and MEDIAKIT_RUNTIME) and clarification routing to sibling domains. Repository: https://github.com/volcengine/mediakit-cli/blob/main/skills/byted-mediakit-video/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "byted-mediakit-video". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install mediakit-cli, configure auth for Cloud-mode tools, read the shared skill's preflight checks, prepare the input media files). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.