studio-setup

Installation
SKILL.md

Studio Setup

Two questions, two scripts. What can I use right now is the bundled scripts/doctor.py. How do I get the rest is video-studio setup. Answer both against the machine in front of you — describing an installed tool as missing wastes the user's time and makes everything else you say suspect.

Requires

scripts/doctor.py ships with this skill — stdlib-only, so the status report works the moment the skill is installed. It reads keys from .env in the current project, then ~/.config/video-studio/.env, then the shell.

setup.py does not ship here: it installs into the engine's own composer directory, so it is not a lone file. It needs pip install 'video-studio-engine @ https://github.com/scrollmark/social-skills/archive/refs/heads/master.tar.gz' and runs as video-studio setup. Without that install there is no install plan and no auto/system/manual classification — you keep doctor's report of what is reachable, but you lose the one thing that stops an agent from running a package-manager install nobody asked for, and you are back to fixing gaps by hand. references/tooling-inventory.md in this skill is the map; only doctor knows the state.

Checking an Environment

python3 scripts/doctor.py           # what is reachable right now
python3 scripts/doctor.py --json    # same, machine-readable

Doctor reports per category — public-domain archives, stock, generated video, generated images, generated audio, voice — plus the required binaries. It checks that a key is present, not that it works; a key can still be rejected at call time for spent quota or a withdrawn model, and the individual scripts report that.

To teach the workflow rather than describe it, video-studio tutor --list names the shipped tutorials; --step <name> <n> serves ONE step, and that is the design. A tutorial pasted whole is a document, not a lesson — nobody reads the middle and you cannot tell what landed. Serve a step, let them try it, ask whether it worked, then move. --show is for you to plan with, never to paste. Start with getting-started; it says up front which steps need a composer this repo does not ship.

Installs
45
GitHub Stars
16
First Seen
Aug 21, 2026