---
name: show-me-around
description: A guided first session. Explain in a few lines what Wideframe does, find out what the user has to work with, and then do something real on their own files before the conversation ends. Use when someone says "walk me through what Wideframe can do", "how do I get started", "what should I do first", "what is this", or sends a first message with no footage, no project and no task.
argument-hint: "[optional: a folder, project, or what they make]"
---

# Show Me Around

A tour that only describes features leaves them where they started. This skill keeps the explanation to a screen, finds out what they actually have, and finishes by running one of the other first-session skills on it, so their first conversation ends with a file they can open.

## Scope

Orientation plus one real task. It does not try to demonstrate everything.

## Step 0: Look before talking

Check the workspace and the message for anything to work with: attached files, a folder, a `.prproj`, a link, a drive path. Note what is there. Do not ask yet.

## Step 1: The short version

Say what Wideframe is in plain terms, in this shape and no longer:

"Wideframe is an editor's assistant that works on your footage and your Premiere projects. Give it a folder of clips or a .prproj and it can:

- Read and transcribe everything, then tell you what you have.
- Build a rough cut or a stringout and hand it back as a Premiere project that opens clean.
- Add captions, cut social clips, sync cameras, fix frame rates, organize bins.
- Bring footage in from Drive, Dropbox, Frame.io, YouTube or an external drive.

The output depends on the task: an editable Premiere project, a review MP4, captions, or a workspace report. These workflows leave source media in place and make project edits on a copy."

Adjust the bullets to the person: if they said they cut wedding films, lead with rough cut and social clips; if they said podcasts, lead with stringout, captions and multicam.

## Step 2: Ask the one question

Based on Step 0:

- If they shared a `.prproj`: "I can start by opening that project and telling you what's in it. Want me to?"
- If they shared footage: "I can build a first rough cut from this, or a stringout if it's interview footage. Which?"
- If they shared nothing: "What do you have right now: a Premiere project, a folder of footage, or a link to where it lives?"

One question. Wait for the answer.

## Step 3: Do the real thing

Route to the matching skill and run it fully, following that skill's own rules (defaults, one question, validate, render):

- Project → `open-my-premiere-project`
- Footage, general → `rough-cut-to-premiere`
- Footage, interview or talking head → `stringout-for-review`
- A link or drive path → `bring-in-footage`, then the first two options
- Several cameras → `sync-my-cameras`
- "Just show me something" with nothing to share: offer to bring in a public video they name (`bring-in-footage` with a link) and caption it (`caption-this`), so the first task has a concrete output.

Do not narrate the tour while the skill runs; the skill's own report is the tour.

Evaluation: by the end of Step 3 a `.prproj` that passed `prproj validate` or a rendered MP4 exists for the user's own material.

## Step 4: Close with the map

After the task's report, three lines:

- What they now have and where it is.
- The two most useful next skills for their kind of work, by name and one phrase each.
- That they can type `/` to see every skill, and `/wf:create-skill` to teach Wideframe a workflow of their own once they have a repeatable one.

## Done when

- The explanation fit on one screen and was adjusted to what the user said they make.
- Exactly one question was asked before work started.
- A first-session skill ran to completion on the user's own files, or on a named public video if they had nothing.
- The user leaves with a file to open and two named next steps.