All courses / Automation
The tool you keep wishing existed takes about an afternoon to make now
Every editor has a list. A panel that renames the selected clips the way the archive wants them. A script that builds the same twelve compositions you build every Monday. A button that exports the four formats your client always asks for.
None of it exists, because building it used to mean learning to program. Over two days you build working tools for Premiere and After Effects with an AI assistant doing the typing — and you leave knowing how to test them, so you are not shipping code you do not understand.
- Length2 days
- FormatOn site or online
- LanguageNorwegian or English
- CategoryAutomation
After the course you can
Build your own plugins with AI
- Build, test and install a working UXP panel for Premiere
- Build a ScriptUI tool for After Effects that does a job you actually have
- Write expressions that would normally need a developer
- Set up reusable skills and an MCP server so the assistant knows your way of working
- Test a tool before trusting it, fine tune the UI, and hand it to a colleague
What we cover
The program
Setting up an assistant that knows your job
- Connecting an MCP server
- Installing and configuring the assistant with the right permissions
- Giving it knowledge of your workflow, your naming rules and your delivery specs
- Prompts that produce precise, testable results instead of plausible guesses
- Reusable skills: teaching it something once instead of explaining it every time
Knowing what to build
- Panel, script or expression — what each one is for
- Which problems are worth automating and which are not
- De-mystifying an existing tool to understand how it works
A panel for Premiere
- What UXP is and how a panel is put together
- Building a simple demo panel
- Loading, reloading and debugging it while you work
- Building a panel your team needs
A tool for After Effects
- ExtendScript and ScriptUI — the correct stack for After Effects
- Building a simple script
- Installing it so it appears in the menu for the whole team
- Building a script your team needs
Advanced expressions
- Getting expressions written, explained and corrected
- Rigs that would take a day by hand
- Keeping them readable so the next person can maintain them
Working safely
- Testing before you trust — the habit that makes all of this viable
- Backups and version control for tools as well as projects
- The most common traps
Distribution
- Packaging a tool so a colleague can install it
- Packaging a tool to sell it
- Keeping it working across versions and machines
The honest bit
You will not become a developer in two days, and the course does not pretend otherwise. What you become is someone who can build and verify a small tool for a job you understand better than any developer does — which for this kind of work is the more useful of the two.
Who it is for
Editors, motion designers, graphic designers and content producers who want to automate their own workflow in Premiere, After Effects or both. It works for people who have never written a line of code and for people who already script.
Prerequisites
Working knowledge of Premiere or After Effects. No programming experience required. You need a Claude Pro or Max subscription, a machine with the software installed and permission to install developer tools and load panels.
Bring
Bring the list. The one in the back of your head, of things you and your team do by hand every week. That list is the curriculum for day two.
Open courses
Prefer a fixed date for one person?
Also runs as an open course at Qross Kurssenter — classroom in Oslo and live online on the same dates.
Questions
About this course
I have never written code. Is this really for me?
Yes, and that is the reason it exists. The assistant writes the code. Your job is to describe the tool precisely and to test whether it does what you asked, and both of those are editing skills rather than programming skills.
What do we end up owning?
Whatever you build during the two days, in your own files, on your own machines. There is no platform to stay subscribed to for the tools to keep working.
Will these tools survive a Premiere update?
Small tools usually do. When one breaks it is normally a single call that changed, and you leave able to find it and fix it — which is the whole point of spending day two on building and testing rather than on more features.
Related courses
Related courses
1 dayTalk to the timeline
Half the work in an edit suite is not editing.
2 daysAdobe Premiere — beginners
Most people who edit in Premiere taught themselves, which means each of them invented a way of working that nobody else understands.
2 daysAdobe Premiere — advanced
After a while everyone settles into habits.
Want this for your team?
Tell me what goes wrong today and you get a written plan and a price back. Two sentences is enough.