Project Packaging Wizard
Package a project for hand-off without shipping terabytes by accident
Consolidation and archiving can behave unexpectedly — copying full clips, collecting too much media, or producing massive packages. This recipe provides a guided packaging flow that produces a clean folder structure, media manifest, checksums, and editor-specific "how to open" notes for the recipient.
INGREDIENTS
PROMPT
Create a skill called "Project Packaging Wizard". Inputs: - project_root - handoff_target (editor | colorist | archive) - handles (e.g., 128f) - max_package_gb - include_proxies (yes/no) Behavior: - Build a packaging folder structure. - Create manifests + checksums. - Provide editor-specific packaging steps and warn if projected size explodes.
How It Works
This skill walks you through packaging a project for another editor, a colorist, or
cold-storage archive. It creates a standardized folder template, generates a manifest
with checksums, estimates the package size before copying, and gives editor-specific
packaging recommendations.
What You Get
- Standardized packaging folder: PROJECT_FILES, MEDIA_USED, PROXIES_OPTIONAL, EXPORTS_REFERENCE, MANIFESTS
- File manifest with sizes, hashes (SHA-256), and clip counts
- Size estimate with a warning if the package exceeds your budget
- Editor-specific packaging steps for Premiere Pro, DaVinci Resolve, and Final Cut Pro
- Configurable handles policy (e.g., 8 seconds, 48 frames, 128 frames)
Setup Steps
- Set your project root and choose a handoff target (editor, colorist, or archive)
- Configure handles and max package size
- Decide whether to include proxies
- Run the skill and review the manifest before copying or uploading
Tips
- Always estimate size before copying — a 2TB project with 128-frame handles might still be 500GB+
- Checksums let the recipient verify nothing was corrupted in transit
- For colorist handoffs, include a reference export so they can compare before and after
- Archive packages should include the full manifest for future you