Free Skill from EZJ Online

Stop deciding every overlay by hand

A Claude skill that reads your script in Notion, works out where overlays actually belong, and writes them in for your editor.

I built this for a coaching business's content team. Deciding and writing every overlay was the slowest part of their week. Now it's a review pass in Notion.

Works inClaude CodeClaude appNotion
Scroll to get the prompt

From script to editor ready

01 Paste the Notion link It opens the script row in your content calendar and reads the format first.
02 It sets the density From how the video is shot, not how many steps it has. A story gets zero. A tutorial gets about eight.
03 It checks your bank Reads your overlay bank live and reuses what fits, so your best overlays keep working.
04 It writes the rest New overlays in your voice where the bank has nothing, and a flag where it would have to guess.
05 Written in place Inline in your script, in your annotation color. Your spoken lines never change.

Copy. Paste. Done.

Paste this into Claude Code. It installs the skill and walks you through the setup.

install-overlay-assistant.txt
Install the overlay-assistant skill from https://github.com/ezjonline/ezj-automations/tree/main/skills/overlay-assistant into my Claude Code skills directory. Clone https://github.com/ezjonline/ezj-automations, copy the skills/overlay-assistant folder to ~/.claude/skills/overlay-assistant, confirm the skill is available, then walk me through filling the Brand Brain in references/brand-brain/ (where my scripts live in Notion, my overlay bank link, my annotation color, and two scripts I already annotated) and check my Notion connection.
  • 5 video types it can tell apart
  • 3 overlay types, matched to the video
  • 0 lines of your script it rewrites

Knowing when not to overlay

Over-annotating is the main way this goes wrong, so the skill is built around one rule: an overlay goes in only where a visual adds something the words can't.

  1. Tutorials get the most. A label per lesson, director notes for the demos, and a designed list where there's a real list.
  2. Walkthroughs get screenshots. One insert per setting, nothing else.
  3. Process videos get a few. Only at the moments there's something to actually look at.
  4. Stories get none. If you're talking to camera and it's carried by the story, it leaves the script clean.

What you need

  • Claude with Notion connectedSo it can read your script and write the overlays back.
  • A content calendar in NotionOne row per video, with the script in the page.
  • Your overlay bank (optional)A Notion page of overlays you reuse. It reads it live every run.
  • Two annotated scriptsSo it learns your density, your phrasing and your color.

What it will not do

It won't touch your spoken script, your hook or your caption. It won't design graphics, invent a stat, or name a template page it can't see. If a line says "use my usual transition", it flags it for you instead of making one up.

Try it with

example-prompt.txt
Add the overlays to this script: [paste the Notion link to the script]

Free AI Audit

Want the whole system, not just the skill?

This is one piece of how I run my business. Book a free AI Audit and I'll map out what the full setup looks like for yours.

Get my free AI Audit

P.S. The hard part was never writing overlays. It was knowing when to leave a line clean. That's what this gets right.

More free resources