Shorts Studio — router

Follow ${CLAUDE_PLUGIN_ROOT}/references/rules.md (modes, questions, honesty, data handling). CLI: "${CLAUDE_PLUGIN_ROOT}/bin/shorts-studio".

0. Engine check

The commands below run the Shorts Studio engine. Installed as the Claude Code plugin it is already present and shorts-studio is on the Bash PATH. If shorts-studio doctor is not found (for example, this skill was added with npx skills add), ask the user before installing anything, then:

• Claude Code: /plugin marketplace add bloxy-studios/shorts-studio → /plugin install shorts-studio@shorts-studio.
• Other agents: git clone --depth 1 https://github.com/bloxy-studios/shorts-studio ~/.shorts-studio/engine and read every ${CLAUDE_PLUGIN_ROOT} path below as ~/.shorts-studio/engine.

Then run shorts-studio doctor --setup once (project-local runtime; never sudo or global installs).

1. Resolve intent

If the request is ambiguous between two rows, ask one AskUserQuestion with those options.

2. Check state before acting

"${CLAUDE_PLUGIN_ROOT}/bin/shorts-studio" doctor            # once per session if unsure
"${CLAUDE_PLUGIN_ROOT}/bin/shorts-studio" project list
"${CLAUDE_PLUGIN_ROOT}/bin/shorts-studio" project show <project> --json   # decisions already made

Reuse an existing project when the user refers to it; never re-ask decisions stored in project.json (decisions). Infer the mode: explicit "do everything yourself" → autonomous; "show me first" → director; otherwise guided.

3. Hand off

Invoke the chosen skill with the user's arguments. Stay in the main conversation for all questions; worker agents return uncertainties to you.

Completion check

You named the workflow you are running, its project directory, and the mode, and the downstream skill's own completion check passed (or you reported what blocked it).

Example

User: "Make three shorts from https://youtu.be/VIDEO_ID, clean podcast style." → intent = clip, preset = clean-podcast, count = 3, mode = guided → run /shorts-studio:clip.