export-checklist
Skill0 starsChanged 41 days agoMITView on GitHub
Pre-export quality-control checklist and recommended export settings by destination (YouTube, vertical short-form, festival, archive). Use when the user is about to render or deliver a video, asks which codec, bitrate, resolution or loudness to use, or wants to avoid common delivery mistakes.
In this repository4 other files it gives its agents.
- color-scriptSkill
- cut-listSkill
- scene-breakdownSkill
- shot-listSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Ask only what is missing:
- Distinctive: line 24
Run the universal QC pass (below) on whatever the user can confirm.
- Distinctive: line 31
Picture: no dropped frames, no black flashes at cuts, no stray frames at head/tail, no leftover offline media or placeholders
- Distinctive: line 34
Audio: no clipping, consistent dialogue level, music not masking speech, no pops at cuts, stereo not accidentally mono (or the reverse)
- Distinctive: line 37
Rights: every music track, font, stock clip and logo has a license or permission.
- Distinctive: line 52
QC checklist: only the items relevant to this delivery, as a tick list
- Distinctive: line 58
Never claim a platform's requirements are fixed.
- Distinctive: line 59
If information is missing, give the safest default and say it is a default.
- Distinctive: line 60
Do not recommend upscaling or frame-rate conversion unless the user needs it.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Export Checklist
Catch the mistakes that cost a re-render: wrong frame rate, clipped audio, burned-in captions in the danger zone, unlicensed music.
Inputs to collect
Ask only what is missing:
- Destination(s): YouTube / streaming, vertical short-form (TikTok, Reels, Shorts), festival or screening, client delivery, archive
- Project specs: resolution, frame rate, color space, whether captions are burned in
- Editing tool: Premiere Pro, DaVinci Resolve, After Effects, other (to name the right export menu)
Process
- Run the universal QC pass (below) on whatever the user can confirm.
- Recommend per-destination settings from the table, adapted to their project.
- Flag the top three risks for this specific delivery.
- Remind them to verify against the platform's current published specs, since platform requirements change.
Universal QC pass
- Picture: no dropped frames, no black flashes at cuts, no stray frames at head/tail, no leftover offline media or placeholders
- Frame rate and resolution: match the project; never "convert" frame rate casually, it creates judder
- Color: confirm the working color space and the delivery space; check a still on a second display; watch for crushed blacks and clipped whites
- Audio: no clipping, consistent dialogue level, music not masking speech, no pops at cuts, stereo not accidentally mono (or the reverse)
- Loudness: streaming platforms commonly normalize around -14 LUFS integrated; keep true peak safely below 0 dBTP (around -1 dBTP is a common safe target)
- Text and captions: spelling checked, readable at phone size, kept inside the platform's UI-safe margins (leave generous margins at top and bottom for vertical)
- Rights: every music track, font, stock clip and logo has a license or permission; automated copyright systems can mute or block uploads
Starting-point settings (verify against the destination's current guidance)
| Destination | Container / codec | Resolution & fps | Notes |
| YouTube / streaming | MP4, H.264 (or H.265/AV1 if supported) | Native project resolution, native fps | High bitrate source gives the platform better re-encodes; export at project resolution, do not upscale |
| Vertical short-form | MP4, H.264, AAC audio | 1080x1920, 24-60 fps (match footage) | One master usually serves Shorts, Reels and TikTok; design for the most restrictive UI overlay (right-edge buttons, large bottom area, Reels typically the biggest), keep text and faces in the upper-middle of frame; check each platform's current max length; strong first 1-2 seconds; avoid excessive sharpening |
| Festival / screening | ProRes 422 HQ or the festival's stated spec | Project resolution and fps | Follow the festival's delivery sheet exactly; ask for it |
| Client review | MP4, H.264, moderate bitrate | 1080p | Burn a timecode only if requested |
| Archive / master | ProRes 422 HQ/4444 or DNxHR, plus project files | Original | Keep project, media list and a plain-text notes file |
Output format
- Destination summary: one line per destination with the recommended preset
- QC checklist: only the items relevant to this delivery, as a tick list
- Top 3 risks: specific to the project
- Export menu hints for the user's tool (e.g. Premiere: Export Settings, match sequence settings; Resolve: Deliver page, render settings)
Rules
- Never claim a platform's requirements are fixed; they change. Say "verify against current specs".
- If information is missing, give the safest default and say it is a default.
- Do not recommend upscaling or frame-rate conversion unless the user needs it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.