Install StarCut for AI agents

Install StarCut

Reply to the user in the language they are currently using. The instructions below are written only in English so there is one execution contract.

This guide is generated for the current environment:

Mode: production
Marketplace: https://github.com/starrank-soft/starcut-plugin.git
Bundle: https://github.com/starrank-soft/starcut-plugin/tree/main/opencode
MCP server: https://api.starcut.io/mcp

Host gate

Run installation only inside an OpenCode project on the machine where StarCut will be used. OpenCode reads project skills from .opencode/skills and project MCP settings from opencode.json.

If this is not the correct host surface, stop and ask the user to open that host and send:

Read starcut.io/opencode.md and install StarCut for me. Complete authentication and verification.

Execution contract

Read this whole guide before running commands. Complete installation, login, and verification in order. Do not stop after an intermediate success. Do not claim later steps passed when an earlier step failed.

OpenCode uses a project bundle for skills plus project MCP config. Materialize the bundle into the OpenCode project before treating MCP auth as complete.

Clone the StarCut plugin repository if it is not already on this machine, then use its absolute path as STARCUT_PLUGIN_REPO:

git clone https://github.com/starrank-soft/starcut-plugin.git
STARCUT_PLUGIN_REPO=E:\starcut-plugin

Clone the plugin repository if it is not already on this machine, then set:

SOURCE=<STARCUT_PLUGIN_REPO>/opencode

Example after git clone:

STARCUT_PLUGIN_REPO=E:\starcut-plugin
SOURCE=E:\starcut-plugin\opencode

Before installing, verify Node.js is available:

node --version

Use the bundled helper for login and configuration. Do not recreate its flow with inline shell, Python, or curl, and never paste credentials into the conversation.

Install project skills

Do this before MCP auth when possible. Skills are local files under PROJECT/.opencode/skills/; MCP authentication does not create them.

1. Ask the user which OpenCode project root should receive StarCut skills if the current workspace is ambiguous. Call that directory PROJECT.
2. Refuse to continue until PROJECT is an absolute existing directory.
3. Sync the .opencode/skills bundle and merge opencode.json into PROJECT. Do not overwrite unrelated MCP servers in an existing file.

Preferred: one-shot install script

& "<STARCUT_PLUGIN_REPO>\opencode\install.ps1" -Project "<ABS_PROJECT_ROOT>" -McpUrl "https://api.starcut.io/mcp"

This copies skills into the project, merges mcp.starcut, and runs opencode mcp auth starcut. If it fails, use the manual steps below.

Manual skills sync

macOS/Linux:

SOURCE="<STARCUT_PLUGIN_REPO>/opencode"
PROJECT="<ABS_PROJECT_ROOT>"
mkdir -p "$PROJECT/.opencode"
rsync -a "$SOURCE/.opencode"/ "$PROJECT/.opencode"/

Windows PowerShell:

$Source = "<STARCUT_PLUGIN_REPO>\opencode"
$Project = "<ABS_PROJECT_ROOT>"
New-Item -ItemType Directory -Force -Path (Join-Path $Project ".opencode") | Out-Null
robocopy (Join-Path $Source ".opencode") (Join-Path $Project ".opencode") /E /NFL /NDL /NJH /NJS /nc /ns /np
if ($LASTEXITCODE -ge 8) { throw "robocopy failed with exit code $LASTEXITCODE" }

Merge mcp.starcut from $SOURCE/opencode.json into $PROJECT/opencode.json without replacing other servers.

Confirm before continuing:

Test-Path (Join-Path $Project ".opencode\skills\basics\SKILL.md")

Log in

From PROJECT, authenticate the StarCut MCP server with OpenCode's CLI:

cd "$PROJECT"
opencode mcp auth starcut

Complete the browser authorization flow once, then start a new OpenCode session.

Verify

Confirm the project skills bundle is present:

test -f "$PROJECT/.opencode/skills/basics/SKILL.md"

Windows PowerShell:

Test-Path (Join-Path $Project ".opencode\skills\basics\SKILL.md")

In the new OpenCode session, confirm the StarCut project tools are available. If the project skills bundle, MCP auth, or authentication state is wrong, fix that exact step and verify again.

StarCut skills (local playbooks)

OpenCode loads the StarCut playbooks from PROJECT/.opencode/skills/. MCP authentication alone does not copy these local SKILL.md files into the project.

Expected directories under PROJECT/.opencode/skills/: basics, graphics, media-gen, media-import, timeline-editing, transcription.

Do not report installation success until PROJECT/.opencode/skills/basics/SKILL.md exists and the StarCut project tools are available in a new session.

Start editing

After installation succeeds, tell the user to start a fresh conversation and send the prompt below in their language. Do not add implementation details.

StarCut is ready. Help me start a new video project. Briefly tell me how you can
help bring it to life, then ask what materials I have and what I want the finished
video to be like.

Completion

Report success only after all of these are true:

1. The plugin or project bundle is installed and enabled.
2. starcut is authenticated against https://api.starcut.io/mcp.
3. The user received the short startup prompt for a fresh conversation.

If any step fails, report the exact failed step and error without claiming later steps passed.