apple-final-cut-pro

Inspect, generate, and patch FCPXML files for Final Cut Pro interchange via Executor.

Updated Oct 15, 2019
One-click install
npx skills add https://github.com/kkkaoru/dotfiles --skill apple-final-cut-pro-kkkaoru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apple-final-cut-pro
Source: https://github.com/kkkaoru/dotfiles/tree/main/.agents/skills-stroage/apple-final-cut-pro
Command: npx skills add https://github.com/kkkaoru/dotfiles --skill apple-final-cut-pro-kkkaoru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing Final Cut Pro timelines programmatically is constrained by the lack of a full live automation API, and directly mutating a live .fcpbundle database risks corruption. This Skill provides a safe FCPXML-first workflow for inspecting, generating, and patching timeline interchange files and delivering them through the native Open Document path. ## Core Features & Use Cases - FCPXML Inspection and Querying: Use interchange_inspect and interchange_query to examine structure, assets, resource IDs, timelines, and metadata without opening the UI. - FCPXML Generation and Patching: Create new .fcpxml files with interchange_write or copy-and-patch existing leaf values with interchange_patch, with DTD-based validation via fcpxml_validate. - Offline Media Editing: Build rendered MP4/M4A assets with media_edit_plan and media_edit, then verify with media_verify_video, audio_measure, and video_frame_measure. - Use Case: Export an FCPXML from Final Cut Pro, patch clip metadata and timing values in rational seconds, validate against the installed edition's DTD, and re-import through app_open_document without touching the live library. ## Quick Start Use the apple-final-cut-pro skill to inspect this exported FCPXML file, patch the clip name values, validate it, and open the result in Final Cut Pro.

Frequently Asked Questions about apple-final-cut-pro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I edit a Final Cut Pro timeline programmatically?

Export or build an FCPXML file, inspect it with interchange_inspect and interchange_query, then create a new file with interchange_write or patch specific values with interchange_patch. Deliver the result through app_open_document using the native Open Document path rather than UI automation.

How to validate FCPXML before importing into Final Cut Pro?

Use fcpxml_validate, which applies the DTD matching the installed Final Cut edition with network and catalog access disabled. Note that DTD success does not resolve media, prove effect fidelity, or guarantee importability, so test imports in an isolated library.

Can I edit a live Final Cut Pro library or .fcpbundle directly?

No. Never mutate a live .fcpbundle database or assume a complete read/write timeline automation API exists. Work on exported FCPXML files or write new standalone .fcpxml files, and import them through the documented Open Document mechanism.

Does FCPXML validation guarantee successful import into Final Cut Pro?

No. DTD validation only confirms XML structure against the schema; it does not resolve media, verify effects, or establish importability. Final Cut Pro may still prompt for an event, library, missing media, or license during import.

What are the limitations of Final Cut Pro automation via FCPXML?

FCPXML interchange is not a live timeline control API. Share/export, effects, keyframe editing, and browser organization require Custom Share Destinations, Workflow Extensions, FxPlug, or UI-only fallback through Peekaboo after explaining the native gap.