agentsclimarketplace
Sign in

Final cut pro workflow

Skill gaelic-ghost/socket/plugins/apple-creator-studio-skills/skills/final-cut-pro-workflow

Guide safe Final Cut Pro libraries, events, projects, media imports, proxy and optimized-media decisions, timeline edits, roles, captions, shares, and Compressor/Motion handoffs. Use when a user needs to inspect, edit, repair, export, or hand off a Final Cut Pro project while preserving source media and existing libraries.From its SKILL.md

Install
npx -y skills add gaelic-ghost/socket --skill final-cut-pro-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.4 KB, 629 tokens by cl100k_base, as published. Nobody here has run it

Final Cut Pro Workflow

Use this skill for Final Cut Pro app operation, not AVFoundation or custom media-code work.

Source Check

Open Final Cut Pro Help or search the local Tips/Help Viewer catalog for Final Cut Pro. Confirm the guide matches the installed app/version before relying on an import, library, proxy, share, or relink path. Read references/library-and-delivery-contract.md before changing a library, event, project, media relationship, or delivery artifact.

Workflow

  1. Classify the task: inspection, library/event organization, import, proxy or optimized-media decision, edit, captions/roles, missing-media repair, Motion handoff, share/export, Compressor delivery, or output verification.
  2. Establish the artifact contract: library/project path, source-media policy, managed-versus-external media state, intended timeline/range, target platform, format, roles/captions, destination, overwrite rule, and deliverable owner.
  3. Inspect before action: selected library/event/project, active timeline, media locations, missing-media/proxy state, render/share state, connected storage, selected ranges, and existing destination contents.
  4. Preserve source state. Use a duplicate library/project or explicit backup before consolidation, relinking, deleting generated files, changing media location, or making wide timeline changes. Do not infer that a generated proxy, optimized copy, or render file is safe to remove.
  5. Make the smallest correct edit. Keep project, event, library, media, and role boundaries clear; explain any tradeoff in proxy quality, optimized-media storage, color/HDR, captions, or sharing settings.
  6. Confirm immediately before importing into a managed library, relinking, consolidating, deleting generated/original media, modifying a shared timeline, rendering, sharing, exporting, or replacing an existing delivery. State the exact source/range, destination, name, format, and overwrite behavior.
  7. Verify the result: inspect library/project state after edits, or inspect the exported artifact for name, location, duration, dimensions, codec/container, audio, captions/roles, color/HDR, and target playback where required.

Guards

  • Do not open, modify, consolidate, or repair an unfamiliar library as a probe.
  • Do not confuse deleting generated media with a harmless operation; inspect whether original, optimized, proxy, render, or cache assets are selected.
  • Do not relink or reveal missing media by guessing a replacement path.
  • Do not claim a Motion template is installed or a Compressor delivery is valid until the receiving app or output artifact has been checked.
  • Hand source-code media processing, codecs, and application implementation to apple-dev-skills.

Handoffs

  • motion-workflow for titles, effects, generators, and transitions authored for Final Cut Pro.
  • compressor-workflow for an explicit delivery preset, batch, and artifact verification after Final Cut Pro creates the source master.
  • apple-dev-skills:avfoundation-media-pipeline-workflow or video-codec-processing-workflow for code-level media handling.

What ships with it: 2 files

1.8 KB alongside SKILL.md

agents/

references/

Gives 0 of the 12 instructions most automation workflows skills give in 629 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

  • Write conventional commit messagesin 36 of 745, across 35 files
  • Delete branches after mergein 30 of 745, across 21 files
  • Make atomic commitsin 25 of 745, across 15 files
  • Write minimal code to pass testsin 22 of 745, across 10 files
  • Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
  • Use try-catch for error handlingin 20 of 745, across 8 files
  • Run tests before committingin 20 of 745, across 12 files
  • Write tests before implementationin 20 of 745, across 8 files
  • Configure branch protection rulesin 19 of 745, across 5 files
  • Explain the why in commit messagesin 19 of 745, across 9 files
  • Refactor code while tests remain greenin 19 of 745, across 6 files
  • Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

  • Inspect the current project state before acting
  • Establish an artifact contract before changing library relationships
  • Preserve source state using a duplicate or explicit backup
  • Make the smallest correct edit
  • State exact source, destination, and overwrite behavior before destructive actions
  • Confirm the guide matches the installed app version

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,736. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.