Help me make my first short video edit on this computer. I am a beginner. 1. Confirm that you can read files and run local tools in the video-editing folder I opened. If not, explain the exact access or app step I need. Do not pretend you have inspected a file. 2. Work inside that folder. Create inbox, working, exports and library only if missing. Keep my original files unchanged. 3. Check the tools already available. Use FFmpeg for the first simple edit. Check caption support and a local transcriber such as Whisper. Before installing anything, explain its purpose, download size if known and any cost. Use a project-specific environment for Python packages. Add only what this edit needs; leave Remotion until I ask for animation. 4. Find the clip in inbox. If there is more than one, show filenames and ask me to choose. Inspect its duration, dimensions, orientation, audio and colour information. 5. Make a five-second test MP4 in working. Convert HEVC or HDR only if needed for compatibility; HDR needs proper tone mapping, not just a different filename or colour tag. Keep speech and picture together. 6. Open the test for me to check sound and natural-looking colour. Tell me what passed, what is missing and where the file is. Stop before editing the full clip. If a step fails, explain the cause before attempting one relevant fix. If that fails too, stop and give me the exact next action.

Make one finished short video from the clip in inbox. Use the brief below. If a detail is blank, use the stated default or ask me only when needed. MY BRIEF Video file: Ask me to choose if inbox contains more than one clip. Format: Vertical 9:16 talking-head video. Names or words to spell correctly: Ask me about uncertain names, numbers or technical terms. Closing action: Keep the spoken ending; do not invent a comment keyword or add a new claim. THE EDIT 1. Confirm the source filename. Transcribe the speech and show me the transcript with timestamps. Flag uncertain words; never invent what I said. 2. Propose a cut list with source start/end times, words to remove and a reason. Remove obvious false starts, repeated takes and dead time. Keep natural breaths, the meaning and my speaking speed. Do not force a target length. Wait for my corrections and approval. 3. Assemble the approved cuts, with audio and picture cut together. Then generate or remap caption timings against the FINAL cut, not the original recording. 4. Add readable captions: maximum two lines, sentence case, strong contrast and natural phrase breaks. Use my corrected wording. Keep text clear of my face and the platform's buttons and caption area. Show me an early and a late frame to check placement. 5. Use a clean style by default. No music, extra footage or animation for this first edit. For a screen tutorial, preserve the readable interface and use a background around it instead of cropping away controls. 6. Show a complete draft MP4 at working/first-edit-preview.mp4. Wait for my approval. If a tool cannot inspect the video, say which checks I need to do myself. 7. After approval, export exports/first-edit.mp4 as H.264 video with AAC audio, SDR/BT.709, yuv420p and fast-start playback. Aim for 1080 x 1920 for vertical, or 1920 x 1080 for landscape, without claiming extra detail from low-resolution footage. Keep the source frame rate unless a change is needed. Keep the file under 95 MB while retaining readable text and speech. 8. Verify the finished file: it opens, has audible speech, correct duration and orientation, no unintended black gaps, no clipped words and captions in sync near the beginning and end. Save corrected captions as exports/first-edit.srt too. Give me clickable links, the folder location and a short list of anything I must check myself. Keep originals untouched. Do not publish or upload anything.

Use the approved edit in this project. Add a hook card and, only if useful, a closing card. 1. Read the final transcript. Suggest three short hook lines that match what I actually say and what this video delivers. Do not invent results or promises. Let me choose. 2. If I supplied a visual reference, use it for style direction. Otherwise use a clean, high-contrast card that matches the captions. Keep my face and existing text visible. The hook appears over the opening for long enough to read, without adding a separate intro. 3. Use my supplied closing action. If I have not supplied one, ask whether to keep the spoken ending. Never invent a keyword funnel. 4. Prefer the tools already working. If I request animated graphics, check whether Remotion is available and whether this computer meets its current operating system requirements. Explain any new installation or licence requirement first. Use its current official documentation and skills where available. 5. Time cards against the final edit and visually check them. Show a preview, including the opening and closing frames, before exporting a new version. Keep the approved clean edit.

Build a small searchable library from the assets I put in library. Start with up to 15 files so I can check your categories first. 1. Inspect representative frames across each clip, and multiple frames of animated GIFs. Write one plain-English description: who or what is visible, what happens and when it would be useful. If you cannot inspect it, mark it unreviewed; do not describe it from the filename alone. 2. Leave every source file where it is. Propose organised COPIES inside library/organised: my-footage/[place-or-event], behind-the-scenes, screens/[tool], gifs/[mood] and screenshots/[tool]. Use descriptive filenames and avoid overwriting duplicates. Show the plan before copying. 3. Only make converted video copies when needed for editing compatibility. Preserve orientation, natural colour and GIF animation. Make thumbnails or a contact sheet so I can review the descriptions. 4. Create library/INDEX.md with original path, organised path, description, useful moments, duration, orientation, tags, review status and source/permission notes supplied by me. Use relative clickable file links where possible. A saved GIF or downloaded image is not automatically cleared for reuse; mark unknown permissions for review. 5. Show me five indexed examples and the contact sheet. Wait for corrections before processing the rest. On later runs, add only new or changed assets; do not duplicate or repeatedly convert the same files.

Read the FINAL edited transcript and use the approved edit in this project. Suggest up to three moments where an image or clip would genuinely make the point clearer. Zero is fine. Look in this order: 1. My reviewed library/INDEX.md and the actual matching asset. 2. A real screenshot or screen recording of the exact tool or page discussed. 3. A GIF from my reviewed library, for a reaction beat only. 4. Stock footage only for a generic scene if nothing above fits. Give the source link and licence information for review before downloading. Show a table: time in the FINAL edit, exact spoken words, proposed asset with preview/path, why it helps, permission status. Do not invent an asset or use a tool logo as proof of what the tool does. If you lack access to capture a screen, tell me precisely what to record and where to save it. Keep private account details out of captures. Wait for my selections. Add only those assets, mute their audio and keep my dialogue audible throughout. Preserve readable interface details; hold screen captures long enough to read, starting around 3.5 seconds and adjusting to the actual content. Avoid covering captions or my face unnecessarily. Check timing against the final audio. Show a preview before a new export; preserve the previous approved file. Use the same export settings and final checks as the first edit.

Show me the folder you are working in and the filenames inside inbox. Compare that with the clip I intended to use. Tell me where to put the file or which folder to reopen; do not guess which video I mean.

Explain what this installation does, why this edit needs it and the exact error or permission requested. Check what is already installed. Try one relevant fix, then stop with the next action if it still fails.

Check whether the local preview server is running and which address and port it uses. Restart only that preview process if needed. Give me a working link or a local preview MP4. Keep the current edit.

Compare the source and export colour metadata, rotation and aspect ratio. Show me a five-second corrected sample, using proper HDR-to-SDR tone mapping if needed. Keep the source and do not convert the entire library yet.

Compare sync at the start and end of the final cut. Check frame rate, audio/video cut boundaries and caption timestamps. Correct the cause and show a short preview from both points before exporting again.

Read the export error, check free disk space and inspect the current file settings. Attempt a short test render before the full export. If size is the only issue, calculate an appropriate bitrate for under 95 MB, preserving readable text and audible speech. Do not just rename the file.

Help me fix this video-editing problem. Keep my originals and the last working version. Problem: Describe what you can see failing, or ask me for the error message and affected filename. 1. Inspect the relevant file, error or process before guessing. Explain the likely cause in one plain-English sentence. 2. Propose the smallest relevant fix. Tell me if it needs a new installation, permission, paid service or upload before proceeding. 3. Attempt that fix and check the result. If it fails again, stop and state what worked, the remaining blocker and the exact action I need to take. Do not keep reinstalling things or rebuild the whole project.

We have approved one complete exported video. Turn the process that actually worked into a reusable reel-edit skill. 1. First confirm the output file passed our checks. Save only the steps and tools we used successfully. Do not add tools or promised capabilities we have not tested. 2. Use the current skill creator or official installation guidance for this app. Create a discoverable SKILL.md with a name and description; confirm where it was saved and how I invoke it. Do not assume a skills folder without checking. 3. Include source-file selection, preserving originals, transcript corrections, cut approval, final-timeline captions, preview approval, export settings and the final-video checklist. B-roll and animation stay optional. 4. Record my approved colours, fonts and text placement in this project. Ask for missing preferences instead of inventing them. Merge with any existing AGENTS.md rather than overwriting it. 5. Save links to the working scripts/templates so the skill can actually use them. Do not embed private filenames, secrets or account details. 6. Show me a short invocation for one named clip. Test on a second clip with the same approval steps before suggesting batch editing.