open-my-premiere-project

I'd like you to add a skill to Wideframe called "open-my-premiere-project".

Save the SKILL.md below exactly as written, then confirm I can run it by saying /open-my-premiere-project.

---
name: open-my-premiere-project
description: Read an existing Premiere Pro project, tell the user what is in it and what state it is in, then offer three concrete next steps and run the one they pick. Use when someone shares a .prproj, says "here's my project", "look at the sequence called …", "what's in this project", or drops a project folder into the chat. This is the first thing to run for anyone who arrives with a project rather than raw footage.
argument-hint: "[path-to-prproj-or-project-folder]"
---

# Open My Premiere Project

Most people who come to Wideframe with a project already open in Premiere want to know two things fast: did Wideframe read it correctly, and what can it do for them next. This skill answers both in one pass and ends by doing real work on the project, not by describing what could be done.

## Scope

Read only until the user picks a next step. Nothing in the project is changed before that. Once they pick, the work happens on a copy of the project unless they say otherwise, and it always ends with `prproj validate` so the file they open in Premiere is clean.

## Step 0: Resolve the input

Accept a `.prproj` path, a folder that contains one, or a workspace. If a folder holds more than one project, list them by modified date and ask which one. If nothing was shared, ask for the project in one sentence and stop.

Do not ask any other question yet. First-time users have not learned the vocabulary; show them the project first.

## Step 1: Inspect

Run `caltools prproj inspect` on the project. Collect:

- Every sequence: name, duration, resolution, frame rate, track count, clip count, whether it has markers.
- Bins and how many items sit in each.
- Media: total clips, how many are offline or missing, how many are proxies, the mix of frame rates and resolutions.
- Captions tracks, MOGRTs, adjustment layers and multicam sources if any exist.

If the project fails to parse, stop and say exactly what failed (version, corruption, missing file). Do not guess.

Evaluation: you can name every sequence and give the offline count before writing a word to the user.

## Step 2: Tell them what you see

Write a short summary in plain language. Lead with the sequence that looks like the active edit (most recently modified, or the one the user named), then the media health, then anything unusual. Keep it to a screen. Example shape:

"This project has 4 sequences. 'Chiro v3' looks like the working cut: 6 min 12 s, 1080p 23.976, 48 clips on 3 video tracks, no markers. 212 media items in 5 bins; 3 are offline (all from the 'Drone' bin). Frame rates are mixed: 23.976 and 59.94. No captions yet."

If anything is offline, mixed-rate, or otherwise likely to bite them in Premiere, say so here in one sentence each. Do not fix it yet.

Evaluation: every number in the summary comes from the inspect output. Nothing is estimated.

## Step 3: Offer three next steps and ask one question

Choose three actions that fit what you found, from this list, and offer them as a short numbered menu. Always include a repair item if the project has offline media or mixed frame rates.

- Relink the offline clips (then validate).
- Conform mixed frame rates so slow-motion clips play at the right speed (`interpret_fps`) and match the sequence settings (`sequence-media-set`).
- Add captions to the working cut (hand off to `caption-this`).
- Put a marker at every soundbite or every mention of a topic (transcribe, then `prproj edit add_marker`).
- Organize the bins by scene, day or shot type (hand off to `organize-my-project`).
- Cut social clips from the working sequence (hand off to `social-clips`).
- Render a review MP4 of the working cut.

Ask exactly one question: "Which of these should I do first?" Accept a number, a name, or a different request.

Evaluation: the menu has three items, one of them addresses a real problem found in Step 1, and nothing has been modified yet.

## Step 4: Do the work

Run the chosen action. Rules that apply to every action:

- Work on a copy: `<name>_wideframe.prproj` next to the original, unless the user asks for in-place.
- Use `caltools prproj edit` for project changes. Never hand-edit XML.
- After the change, run `caltools prproj validate`. If it reports dangling references, orphans or a schema problem, fix and re-run before reporting.
- If the action produces a sequence worth watching, render a review MP4 with `caltools sequence-render-final` at the sequence's own resolution and frame rate, then confirm the file with `media-info-batch`.

Evaluation: validate passes, the clip count in the edited sequence matches expectations, and the review render plays with audio.

## Step 5: Report and point forward

Report in three lines: what changed, where the file is, what to open in Premiere. Then name the two menu items they did not pick, so they know the next move.

## Done when

- The user has an accurate plain-language picture of their project, including any offline media or mixed frame rates.
- Exactly one next step was chosen by the user and completed.
- The delivered `.prproj` passed `prproj validate` and the original is untouched.
- A review MP4 exists for any sequence that was changed.