rajat974/yellowworkshops-skill

yellowworkshops

The creator bought yellowworkshops and added this plugin. This skill gets their own computer ready the first time (about 10 minutes, once), keeps it up to date, opens the guide, and then hands every edit to the full editor skill (ugc-reels-editor). Creators are not technical: never ask them to type commands; run everything yourself and talk in plain words.

Run on their own computer

Everything runs on the creator's own Windows PC or Mac through the Claude desktop app's Code tab (or Claude Code). If the status check says SANDBOX, you're in a small cloud sandbox, not on their computer: tell them, in one or two lines, to open the Claude desktop app, choose Code, pick a folder on their computer and ask again there. Never copy their footage anywhere to work around it.

The setup commands

The scripts are in the scripts folder next to this file (this skill's base directory). Use the one for the computer:

• Windows (PowerShell): powershell -NoProfile -ExecutionPolicy Bypass -File "<skill dir>\scripts\start.ps1" <command>
• Mac (bash): bash "<skill dir>/scripts/start.sh" <command>

Commands: status · all --key YWS-XXXX-XXXX-XXXX · update --daily · diag. The first run fetches a private copy of Python (checksum-pinned) into ~/yellowworkshops/runner; nothing is installed system-wide and no admin password is needed.

Every time the creator asks for a reel (or anything yellowworkshops)

1. Run status. It prints JSON and then one of READY, NOT_SET_UP or SANDBOX: ….
2. NOT_SET_UP: set up (below), then continue with their request.
3. READY: run update --daily (quick; at most one real check a day). If it prints UPDATED to …, tell them in one line what's new (the text after the colon). Then hand over to the editor: use the ugc-reels-editor skill if it's listed; otherwise read ~/.claude/skills/ugc-reels-editor/SKILL.md and follow it. Run the editor's scripts with the Python in ~/yellowworkshops/ugc-reels-home.json (python_cmd) — the engine only runs with that Python. New projects go in ~/yellowworkshops/projects/<reel name>/.

First-time setup

1. You need their licence key (YWS-XXXX-XXXX-XXXX, in their purchase email). If they haven't given it, ask for it — the only question you ask. Tell them in one line: "Setting up your computer now: about 10 minutes, once. Your videos never leave this computer."
2. Run all --key <KEY>. It downloads about 1 GB, so run it in the background and wait for it to finish (don't poll in a loop). It prints a numbered step list ([3/7] Activating your licence…) with download percentages; pass on the step titles briefly, not every line. If a command is cut off by a time limit, run the same command again: finished steps are skipped and downloads resume.
3. Read the result by its last line and exit code:
   • READY: … (exit 0) → tell them it's set up, mention "type guide anytime for ideas", then continue with their request (step 3 of the section above). The editor skill was just added to ~/.claude/skills/ugc-reels-editor; if it isn't listed yet in this session, read its SKILL.md directly.
   • NEEDS_KEY (exit 11) → ask for the key, run again with --key.
   • SANDBOX: … (exit 10) → see "Run on their own computer".
   • SETUP_ERROR: <reason> (exit 1) → fix it with the playbook below, then run all again. Details are in ~/yellowworkshops/install-log.txt.

Fix-it playbook (SETUP_ERROR)

Fix what you can yourself, explain the rest in one or two plain sentences, then retry.

• Couldn't reach / couldn't download → check the internet (curl -I https://yellowworkshops.com). A company network, VPN or firewall may block downloads: ask them to try another network (phone hotspot), then retry.
• Only N GB free → tell them how much to free and where (Recycle Bin/Trash, Downloads); you can show the biggest folders in their Downloads, but delete nothing yourself without their clear OK.
• Key already used on another computer → one computer per licence. Offer: on the old computer say "move my yellowworkshops licence" (it runs reels deactivate), or write to [email protected] if that computer is gone.
• Key not found / refunded → ask them to copy the key again from the email (letters O vs 0); otherwise support.
• Antivirus / couldn't unpack / a program is still using it → close other Claude sessions editing a reel and the editor window; if an antivirus quarantined files, ask them to allow the yellowworkshops folder in their home folder.
• Windows "path too long" → the home folder path is very long; set YWS_HOME to a short path such as C:\yellowworkshops for the setup command, and retry.
• FFmpeg/engine doesn't start on this Mac → note the macOS version from status; macOS 12 or newer is needed. Older Macs aren't supported: say so kindly and point them to [email protected] for a refund.
• Download list isn't signed / setup helper too old → update this plugin (/plugin update yellowworkshops — run it for them if you can, otherwise tell them that one line), then retry.
• Anything else → run diag, explain what you see, and offer to write a support email for them to send to [email protected] with the diag output (it contains no footage or names).

guide

When the creator types guide, "what can I ask?" or "show me examples": open the yellowworkshops Guide, a page of copy-ready prompts. If ~/yellowworkshops/ugc-reels-home.json has guide_url, open that artifact. Otherwise publish assets/guide.html from the editor skill (~/.claude/skills/ugc-reels-editor/assets/guide.html) once as an artifact, save its URL as guide_url in that JSON, and open it. It holds no reel data. If the page isn't there yet, give them eight good example prompts in chat instead.

Other requests

• Update / get the new styles → update (without --daily), then ~/yellowworkshops/bin/reels styles update (Windows: %USERPROFILE%\yellowworkshops\bin\reels.cmd styles update); report what changed and name any new styles (they show with a New badge in the editor's Gallery).
• Move the licence to a new computer → on this computer run ~/yellowworkshops/bin/reels deactivate (Windows: %USERPROFILE%\yellowworkshops\bin\reels.cmd deactivate), then on the new computer add the plugin and set up with the same key.
• Something's broken → status, then diag; fix with the playbook.

Privacy (a promise to the creator)

Their footage, audio, frames, transcripts and renders never leave their computer. The setup downloads only public program files from yellowworkshops.com (each checked against our signed list); activation sends only the licence key and a hashed computer ID.