ADD THIS SKILL
paste into a new chat
Copy this into a blank Wideframe chat. It tells the agent to build the skill, what to confirm with you first, the steps to follow, and how to verify the result.
PROMPT
I'd like you to add a skill to Wideframe called "organize-my-project".
Save the SKILL.md below exactly as written, then confirm I can run it by saying /organize-my-project.
---
name: organize-my-project
description: Put an existing Premiere Pro project in order: file every clip into a bin structure, name things consistently, create the working sequences the user asked for (one per day, per scene, per deliverable), and lay out tracks so the edit is ready to start. Use when someone says "organize this project", "set up bins", "make a sequence for each day", "clean this up", "prep this for editing", or shares a project with hundreds of loose clips in the root.
argument-hint: "[path-to-prproj] [optional: how to group: day, scene, camera, shot type]"
---
# Organize My Project
Prepare the project before making the edit: bins by day, a sequence per shoot, and useful display names. This skill performs the setup on a project copy, validates it, and reports the resulting structure.
## Scope
Structure, names and empty-but-ready sequences. No cutting decisions. Nothing is deleted and no media file on disk is renamed or moved; only the project's items change.
## Step 0: Resolve the input and pick the grouping
Accept a `.prproj` or a folder holding one. Read the user's instruction for how to group. If they gave none, choose from what the footage supports, in this order: shoot day (from capture dates) if the project spans more than one day, then camera or source if there are several, then shot type. State the choice; do not ask.
Defaults unless told otherwise:
- Bin names: `01_Day 2026-09-12`, `02_Day 2026-09-13`, or `Interviews`, `B-roll`, `Audio`, `Graphics` for type grouping. Zero-padded prefixes so bins sort.
- A `_UNSORTED` bin for anything that cannot be classified with confidence.
- One sequence per top-level bin, named after it, at the majority frame rate and resolution of the clips in that bin, with tracks V1 to V3 and A1 to A4.
- Work on a copy: `<name>_organized.prproj`.
## Step 1: Read the project
1. `caltools prproj inspect`: every item, its media path, bin, existing sequences, and media health (offline, proxies, rates, resolutions).
2. `caltools media-info-batch` on every media path for capture date, fps, resolution, duration and audio.
3. Only where the grouping needs it (scene, subject, shot type): `caltools media-analyze-content-batch`, then `job-poll` until done.
If more than a handful of clips are offline, stop and say so; organizing references to missing media wastes the user's time. Offer `relink-media` and continue only if they want to proceed anyway.
Evaluation: every project item has the fields the grouping rule needs, and the offline count is known.
## Step 2: Plan the structure
Assign every clip to exactly one bin by the grouping rule. Low-confidence assignments go to `_UNSORTED` with the reason. Draft the bin tree with counts and the list of sequences to create. Keep any sequences that already exist; move them into a `Sequences` bin rather than touching their contents.
Show the plan as a short tree before applying it. This is the one place to pause: "Here's the structure I'll build. Go ahead, or change anything?" If the user gave a full instruction already (as in "bins by day, one sequence per day"), skip the pause and build.
Evaluation: item count in the plan equals item count in the project; every bin has at least one item or is a required container.
## Step 3: Build it
All changes via `caltools prproj edit` on the copy:
1. `create_bin` for every node of the tree.
2. Move each item to its bin; move existing sequences to `Sequences`.
3. `rename_sequence` and clip display names only where the user asked for a naming convention. Media files on disk are never renamed here (that is `rename-clips`, and it writes a reversible manifest).
4. `add_sequence` for each planned sequence at the bin's majority settings; `add_track` to reach the default track layout.
5. Where the user asked for clips laid into the day sequences (a "stringout per day"), add them in capture order with `add_clip_with_media`; otherwise leave sequences empty and say so.
Evaluation: after building, `prproj inspect` shows every item filed once, the planned sequences present with the planned track counts, and the root holding only bins.
## Step 4: Validate and check
1. `caltools prproj validate` on the copy. Zero dangling references and orphans, or fix and re-run.
2. Reconcile: item count before equals item count after; sequence count equals existing plus planned.
3. If any sequence was populated, `sequence-render-frames` at three points to confirm clips are present and at the right aspect.
## Step 5: Report
Give the bin tree with counts, the sequences created (name, settings, populated or empty), the `_UNSORTED` list with reasons, and the path of the organized copy. Then point forward: `rough-cut-to-premiere` on any day sequence, `stringout-for-review` for interview bins, `relink-media` if anything was offline.
## Done when
- Every project item sits in exactly one bin, and the root contains only bins.
- The planned sequences exist with the right settings and track layout.
- `prproj validate` passes on the copy and the original is untouched.
- Nothing on disk was renamed, moved or deleted.
- The user saw the structure before it was built, or had already specified it.
Download SKILL.md. If this workflow calls another named skill, add that recipe from the library too. Available tools and source access determine which steps can run.
RUN IT AGAIN
Once it’s saved, run it on the next project with /organize-my-project, or just say:
Organize this Premiere project into useful bins and working sequences.Run it on your own footage.
7-day free trial. Requires Apple Silicon.
RELATED SKILLS