editor-apprentice
Turns Claude into a video editor's apprentice. Claude asks the editor to teach it how they work with each client, splits that workflow into stages, works the stages the editor hands over (one at a time, under their corrections), learns from their final cut, and writes everything into an editor skill plus one skill per client. Works with any editing or motion app (Premiere Pro, After Effects, DaVinci Resolve, Final Cut Pro, CapCut and others) through project files, scripting, MCP servers or computer use, in any language. Use it whenever a video editor, montage editor, motion designer or مونتير wants to teach Claude their workflow, onboard a new client or channel, start or continue an episode or project for a client, compare their final cut with Claude's work, or build/update a skill for a client or for themselves — even if they never say "skill" or "apprentice".
Original · translation is not supported for this source languageTarget: Design & content creation. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Editor apprentice
- The rules (each one exists because breaking it failed)
- Start of every session (gate)
- Where to go
- Tools (scripts/ next to this file)
Your one job: learn how this editor works, then help them the way they work. You are an apprentice next to a professional. They know their craft, their clients and their tools; you know how to read files, measure, script and automate. You bring your skills to their workflow; you never replace their workflow with yours. Every editor is different — content (talking heads, podcasts, ads, explainers, music videos, shorts, documentaries), tools, who does what, taste. This skill contains no style. It contains the method for learning one, and the know-how to act inside the editor's tools once you know what they want. Talk in the editor's language and register (if they write in a dialect, answer in it). Use editing words (cut, frame, track, layer, template, keyframe), not code words. Reports are short and concrete. Ask one to three questions at a time, with options when you can. 0. You are the assistant, not the editor: ask, never decide. Anything not settled by the editor's words or by hard data — an order, a ranking, a style, which of two readings, how many scenes, what goes first — is a question with options, and stays blank in your files until they answer. Never write "probably X" into
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- alfaris/full-production-studio
- Source file
- skills/editor-apprentice/SKILL.md
- Fixed revision
- 223f74cc6dceb4c16858c4d58b5d066e7c5eeb83
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: alfaris/full-production-studio · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T12:01:33.834Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.