-- Workflow --

1. Import Clip
2. Download script
3. Create Image
4. Create Title and Tags

-- Original Prompt --

Use Opus Clip for this YouTube video VIDEO LINK
When parsing the clip use my default settings but ensure it uses ClipAnything with lengths under 30 seconds.
Apply Brand template named Preset template 1.  
Return a list of each of the clips created.  
For each clip, using Opus Clip download the transcript.  
Use the Transcript to create a [$youtube-short-image].  
Use the Transcript to create a [$youtube-title-tags] .  
Save the Transscript using the clip number and name like 1_NAME-OF-CLIP
Save the Image using the clip number and name like 1_NAME-OF-CLIP
Save the Titles and Tags using the clip number and name like 1_SeoPackage
Save to C:\\Data\OpusDemo\<Name>
Always return the Opus credits used for all calls in this request.


-- AI Enhanced Prompt --

# Opus Clip → Shorts Packaging Pipeline

## Step 1 — Create the clips

**All Opus Clip operations in this entire run — video processing, clip listing, transcript downloads, and credit reporting — MUST go through the Opus Clip MCP Server tools.** Never use browser automation, the Opus Clip web UI, or guessed API calls as a substitute. If the Opus Clip MCP Server is not connected or its tools are unavailable, STOP immediately and tell me — do not attempt the task another way.

1. Use the Opus Clip MCP Server to process this YouTube video: VIDEO LINK
2. Use my default project settings with these overrides:
   - Clipping mode: **ClipAnything**
   - Maximum clip length: **30 seconds**. If any generated clip still exceeds 30 seconds, keep it but flag it in the final report — do not silently include or discard it.
   - Brand template: **Preset template 1** (exact name).
3. When processing completes, list every clip created: clip number, Opus Clip's title, and duration.

Every clip in that list goes through Step 2. All of them.

## Step 2 — Per-clip loop

Repeat ALL of the following for each clip, in order (clip 1 fully finished before clip 2 starts):

1. **Transcript** — download this clip's transcript via the Opus Clip MCP Server.
   Save as `{N}_{NAME-OF-CLIP}.txt`
2. **Short image** — run [$youtube-short-image](C:\Users\swthomas98\.codex\skills\youtube-short-image\SKILL.md), deriving the image description from this clip's transcript (distill the transcript's hook per the skill's rules).
   Save the image as `{N}_{NAME-OF-CLIP}.png`
3. **Titles and tags** — run [$youtube-title-tags](C:\Users\swthomas98\.codex\skills\youtube-title-tags\SKILL.md) on this clip's transcript.
   Save the output as `{N}_SeoPackage.md`

**Naming rules:**
- `{N}` = clip number from the Step 1 list.
- `{NAME-OF-CLIP}` = Opus Clip's title, sanitized: spaces → dashes; strip every character that is not a letter, number, or dash. The transcript (.txt) and image (.png) share this same base name.

## Step 3 — Save location

Save all files flat into `C:\Data\OpusDemo\{VIDEO-NAME}` (create the folder if it does not exist).

**Resolving `{VIDEO-NAME}`, in this order:**

1. Use the YouTube video's title, sanitized with the same rule as clip names: spaces → dashes; strip every character that is not a letter, number, or dash (e.g., "Logic Apps: Easy Auth vs SAS?" → `Logic-Apps-Easy-Auth-vs-SAS`).
2. If the video title cannot be determined, use the Opus Clip Project ID for this run instead, exactly as Opus Clip reports it.
3. Never fall back to a generic or invented folder name. Resolve the folder name ONCE at the start of the run and state it before saving anything — every file in this run goes into that one folder.

## Step 4 — Final report (always produce this, even if some steps failed)

1. The resolved save folder path, and whether it came from the video title or the Project ID.
2. A table: clip # | clip name | duration | files saved.
3. **Opus credits used for every call in this request, itemized per call, with a total.**
4. Any clip over 30 seconds, and any step that failed.

## Rules

- Every Opus Clip interaction uses the Opus Clip MCP Server tools — no exceptions, no fallback methods. Credits reported in Step 4 are the credits consumed by those MCP calls.
- Do not stop, summarize, or ask for confirmation between clips. The task is complete only when every clip has all THREE files saved (transcript, image, SEO package). Ending early is a task failure.
- If a step fails for one clip, retry it once; if it fails again, note the failure and continue with the remaining clips. Never let one clip's failure abandon the batch.
- Ask me before re-running Opus Clip video processing (it costs credits). Every other step proceeds without asking.
- Never invent a transcript, score, or clip name — if a value is unavailable, mark it as missing in the report.