Skip to content
Back to search

nextwork

MarketplaceWorks with Claude CodeGitHubIncomplete

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/nextwork-projects/ai-video-editor-cooked with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/nextwork-projects/ai-video-editor-cooked'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/nextwork-projects--ai-video-editor-cooked/badge.svg)](/listings/nextwork-projects--ai-video-editor-cooked)

HTML

<a href="/listings/nextwork-projects--ai-video-editor-cooked"><img src="/api/listings/nextwork-projects--ai-video-editor-cooked/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

The first time, the sidebar shows **Getting started** with three steps. It ticks them off as you go and goes away once your first cut is ready.

1. **Set up.** Press **Start setup**. It checks your computer and installs what is missing: Python, ffmpeg, Node, the free transcription model and the renderer (about 1.5 GB, most of it the renderer). On GitHub's clean runners this took 25-36 s on Linux, 33-49 s on a Mac and 66-75 s on Windows, with the 75 MB test model in place of the 500 MB default. A home connection is slower. Anything that needs your password, Claude gives you to paste into your own terminal. While it installs, it offers two optional keys (see [Keys](#keys)). 2. **Analyse a format.** Paste 3 to 6 links to videos edited the same way, or paste a profile and tick its videos. Press **Analyse this format**. Claude measures them (about 3 minutes, free) and saves a style you can rename. The style lists the videos it came from. 3. **Make a video.** Drop in your clip. The new style is already picked. Press **Make my video**. No video yet? Pick **Use the sample take**.

Claude also asks a few questions once (platform, brand, captions, sound). Each is multiple choice and the first option is fine. The answers are saved in `~/.ai-video-editor/profile.json`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 30 lines
  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "nextwork",
  4. "owner": { "name": "NextWork", "url": "https://nextwork.ai" },
  5. "metadata": {
  6. "description": "NextWork's open-source video plugins: measure how a short-form creator edits, then edit your own talking-head video in that style."
  7. },
  8. "plugins": [
  9. {
  10. "name": "creator-teardown",
  11. "source": "./plugins/creator-teardown",
  12. "description": "Break down any short-form creator's videos: view counts, word-level transcripts, measured pace, cuts, zooms and caption style.",
  13. "version": "2.7.54",
  14. "category": "media",
  15. "tags": ["video", "analysis"],
  16. "keywords": ["creator", "tiktok", "youtube-shorts", "transcription", "teardown"],
  17. "skills": ["./skills/creator-teardown"]
  18. },
  19. {
  20. "name": "ai-editor",
  21. "source": "./plugins/ai-editor",
  22. "description": "Edit your own talking-head video in a creator's measured style: retakes and pauses cut, then zooms, captions and cards rendered with Remotion on your laptop or AWS Lambda.",
  23. "version": "2.7.54",
  24. "category": "media",
  25. "tags": ["video", "editing"],
  26. "keywords": ["video-editing", "captions", "jump-cut", "remotion", "talking-head"],
  27. "skills": ["./skills/setup", "./skills/start", "./skills/cut", "./skills/style-edit", "./skills/overlays", "./skills/taste", "./skills/motion-design", "./skills/motion", "./skills/product-video", "./skills/clips", "./skills/improve", "./skills/update", "./skills/post", "./skills/logo-pack", "./skills/skill-improver", "./skills/skill-maker", "./skills/broll-reel", "./skills/trial-reels"]
  28. }
  29. ]
  30. }
README.md · README · 385 lines
  1. <img src="docs/logo.svg" width="64" height="64" alt="">
  2. # cooked.
  3. cooked. edits your talking-head video for you. You give it two things:
  4. Full setup guide [here](https://nextwork.ai/projects/5610da9c-bb29-42b6-a4a4-e30420ec671d?utm_source=github&utm_medium=nextwork-projects&utm_campaign=profile&utm_content=ai-video-editor-cooked)!
  5. 1. **Your video.** It cuts out the retakes, false starts and pauses.
  6. 2. **3 to 6 videos edited the same way.** They can come from one creator or from several. It measures
  7. how they are edited: cut speed, zooms, captions, cards, graphics, sound. That set of numbers is a
  8. **style**, and you keep it.
  9. Then it edits your video in that style. You approve the cut, then the look, then the render. It runs in
  10. [Claude Code](https://claude.com/claude-code) on your computer, with a window in your browser.
  11. It also makes:
  12. - **Shorts from a long video or podcast.** Paste the link. It finds the clips and edits each one.
  13. - **A product video from a website.** Paste the URL. It asks what to show, records the real product
  14. and cuts a launch film with its own music.
  15. - **A creator teardown.** Paste a profile. You get what makes their videos work, and a style.
  16. ![Six frames from an edit of the sample take: word captions, a captured page and logos timed to the words](docs/screens/after-talking-head.jpg)
  17. <!-- TODO(owner): drop a 10-second before/after demo GIF at docs/demo.gif, then replace this comment with: ![Before and after](docs/demo.gif) -->
  18. Built by [NextWork](https://nextwork.ai). Free and open source (MIT). Works on Mac, Windows and Linux.
  19. ## Start here
  20. You need [Claude Code](https://claude.com/claude-code) and a Claude account (a paid plan or an API
  21. key). Pick one of three ways to get the editor. After that, open it from a terminal every time:
  22. ```
  23. nextwork-editor
  24. ```
  25. One command opens everything: your editor in the browser, at the same address every time (bookmark it),
  26. and Claude Code behind it, listening for what you make there. Run it again when the window is already open
  27. and it opens the window, plus a new Terminal window with Claude if none is listening. `nextwork-editor
  28. --window-only` opens just the window. If the window ever says nobody is listening, press **Connect Claude**:
  29. it opens Claude in a new Terminal window for you. Inside Claude Code, `/ai-editor:start` or **edit my video**
  30. does the same. Setup adds the command; `python3 plugins/ai-editor/skills/setup/scripts/setup.py
  31. uninstall-launcher` removes it.
  32. **The window.** A sidebar on the left has **+ New video**, **Home**, **Your videos**, **Styles**, your
  33. folders, the video being made right now with its progress, and **Settings**. The panel button folds the
  34. sidebar into a row of icons. To make a video: drop in your clip (or click one you added before), pick a
  35. style, press **Make my video**. **Make it in a new Claude chat** keeps that video's questions in their
  36. own chat. The first time, Claude Code asks whether you trust this folder: press the down arrow to pick
  37. **Yes, I trust this folder**, then Enter (Enter alone picks **No, exit**). It is your videos folder.
  38. Your videos are saved in one folder, wherever you start: `~/Movies/AI Editor` on a Mac,
  39. `~/Videos/AI Editor` on Windows and Linux. Change it in Settings (or set `AI_EDITOR_LIBRARY`).
  40. ### Way 1: open this folder in Claude Code (easiest)
  41. **1. Install Claude Code** (skip if you have it). Open a terminal:
  42. - **Mac:** press Cmd + Space, type `Terminal`, press Enter. Paste this and press Enter:
  43. ```
  44. curl -fsSL https://claude.ai/install.sh | bash
  45. ```
  46. - **Windows:** press the Windows key, type `PowerShell`, press Enter. Paste this and press Enter:
  47. ```
  48. irm https://claude.ai/install.ps1 | iex
  49. ```
  50. - **Linux:** open your terminal app and paste the Mac line.
  51. **2. Get this folder.** Either:
  52. - **No git:** at the top of this page click the green **Code** button, then **Download ZIP**. Unzip
  53. it (double-click on Mac, right-click > **Extract All** on Windows). You get a folder called
  54. `ai-video-editor-cooked-main`.
  55. - **With git:** `git clone https://github.com/nextwork-projects/ai-video-editor-cooked.git`
  56. **3. Open Claude Code in that folder.** In the terminal type `cd ` (with a space after it), drag the
  57. folder onto the terminal window, press Enter. Then type `claude` and press Enter. The first time,
  58. it asks you to log in.
  59. **4. Say yes when it asks whether you trust this folder.** That lets the editor load. Then type
  60. **edit my video**.
  61. **5. Pick "Open the home page".** The editor opens in your browser. Follow
  62. [Getting started](#getting-started) below.
  63. The folder's `.claude/settings.json` turns the editor on. If Claude says the editor is not loaded,
  64. it offers to install it: say yes, then type `/reload-plugins`.
  65. **Fewer Allow prompts.** A Claude Code the editor opens (`nextwork-editor`, **Connect Claude** or "Open a new Claude" on
  66. the home page) already allows the editor's own commands and nothing else: its Python and Node scripts,
  67. `ffmpeg`, `ffprobe` and `npx remotion`. Started Claude Code yourself? Pick "Yes, and don't ask again"
  68. the first time each is asked, or put the same rules in your library folder's `.claude/settings.local.json`
  69. (replace `<plugin>` with the plugin folder, the path in the first command Claude runs):
  70. ```json
  71. {"permissions": {"allow": ["Bash(python3 <plugin>/*)", "Bash(node <plugin>/*)", "Bash(ffmpeg *)", "Bash(ffprobe *)", "Bash(npx remotion *)"]}}
  72. ```
  73. ### Way 2: install the plugin, then use any folder
  74. Inside Claude Code, type these two lines (same on every computer):
  75. ```
  76. /plugin marketplace add nextwork-projects/ai-video-editor-cooked
  77. /plugin install ai-editor@nextwork
  78. ```
  79. If it asks, type `/reload-plugins`. Then say **edit my video**. `creator-teardown` installs with it.
  80. Your edits land in your library folder (above), wherever you started Claude Code.
  81. ### Way 3: other agents (Codex, Cursor, Gemini CLI, Copilot)
  82. In a terminal, on a computer with [Node.js](https://nodejs.org):
  83. ```
  84. npx skills add nextwork-projects/ai-video-editor-cooked
  85. ```
  86. `AGENTS.md` (and its copy `GEMINI.md`) tells the agent where to start. The skills share code in
  87. `plugins/ai-editor/lib/` and the renderer in `plugins/ai-editor/remotion/`, so if your agent copies
  88. single skill folders, clone the whole repo too.
  89. ### Want to change the editor itself?
  90. Most people never need to. The plugin plus your own folder covers it: your styles, skills and
  91. settings live in your folder and stay when the editor updates. See
  92. [docs/customise.md](docs/customise.md).
  93. If you want to change the editor's own code:
  94. 1. On GitHub, press **Fork** at the top of this page. You get your own copy.
  95. 2. In Claude Code, install the editor from your copy:
  96. ```
  97. /plugin marketplace add <your-github-name>/ai-video-editor-cooked
  98. /plugin install ai-editor@nextwork
  99. ```
  100. 3. Clone your fork and change anything you like.
  101. 4. When a new version comes out, say **update the editor** (see [Updating](#updating)).
  102. ## Getting started
  103. The first time, the sidebar shows **Getting started** with three steps. It ticks them off as you go
  104. and goes away once your first cut is ready.
  105. 1. **Set up.** Press **Start setup**. It checks your computer and installs what is missing: Python,
  106. ffmpeg, Node, the free transcription model and the renderer (about 1.5 GB, most of it the
  107. renderer). On GitHub's clean runners this took 25-36 s on Linux, 33-49 s on a Mac and 66-75 s on
  108. Windows, with the 75 MB test model in place of the 500 MB default. A home connection is slower.
  109. Anything that needs your password, Claude gives you to paste into your own terminal. While it
  110. installs, it offers two optional keys (see [Keys](#keys)).
  111. 2. **Analyse a format.** Paste 3 to 6 links to videos edited the same way, or paste a profile and
  112. tick its videos. Press **Analyse this format**. Claude measures them (about 3 minutes, free) and
  113. saves a style you can rename. The style lists the videos it came from.
  114. 3. **Make a video.** Drop in your clip. The new style is already picked. Press **Make my video**.
  115. No video yet? Pick **Use the sample take**.
  116. Claude also asks a few questions once (platform, brand, captions, sound). Each is multiple choice and
  117. the first option is fine. The answers are saved in `~/.ai-video-editor/profile.json`.
  118. ## Keys
  119. Both are optional and free to start. They make edits better and use less of your Claude usage.
  120. Skip either and Claude does that job instead. Add them later by saying **finish setup**.
  121. - **ElevenLabs** transcribes every "um", false start and retake, so the cut is cleaner. Without it,
  122. Whisper transcribes on your computer, which tidies some of those away.
  123. - **Gemini** (Google AI Studio) watches a format's videos and reads its fonts, colours and graphics.
  124. Never paste a key into the chat. Claude gives you a command that saves it from your own terminal.
  125. Keys live in `~/.config/creator-teardown/.env`.
  126. ## The editor
  127. Each video has an editor page. It opens on the cut, then on each render.
  128. - **Your video beside its transcript.** The transcript follows playback. Struck words were cut.
  129. - **Suggested cuts.** Claude marks words it thinks should go. Keep them one by one, or press
  130. **Accept all**.
  131. - **Change the cut yourself.** Select words to cut or restore them. **Preview** plays the cut with
  132. your changes. **Apply** keeps them. Undo and Discard are there too.
  133. - **Notes.** Pause anywhere and leave a note. **Send notes** starts the next round. Approve when it
  134. looks right.
  135. - **The look.** After the cut, Claude makes a sheet of frames from the styled edit. Approve, or say
  136. what to change. You can also move, trim, swap or delete anything by hand.
  137. - **The render.** Claude times each place to render on your video and shows the cost first. The
  138. render opens on the same page: watch it, leave notes, send them or approve.
  139. - **Teach your style.** When you approve the final video, **Teach your style from this video** turns
  140. your notes into short rules for that style. You see each rule and tick the ones to keep.
  141. A correction you say in the chat ("captions too small", "fewer zooms") is saved to
  142. `~/.ai-video-editor/taste.md` and used on every video after.
  143. ## Styles
  144. **Styles** is one list of every style you can edit with. Each card says where it came from: built by
  145. you, learned from your edits, or from a creator's videos. Tabs filter the list: **All**,
  146. **Built by you**, **From creators**.
  147. - **Card edit** is a sample style that comes with the editor: real screenshots, logos, photos and
  148. clips on cards behind you, a title pill on the hook, a numbered list, and a red X over a card that
  149. does not apply.
  150. - **New style** opens three choices: **Analyse a format** (paste 3 to 6 videos), **Build it
  151. yourself** (set captions, zooms, cut, cards and sound), or **Use your own skill** (see below).
  152. - A style's page shows it on your video, with its captions, zooms, cut, cards and sound as options.
  153. Changes save as you go. Make any style your default.
  154. - **Skill styles.** A style can run a Claude Code skill instead of using settings. Its card says
  155. "Runs /<skill>". Making a video cuts it as usual, then runs that skill on the approved cut and puts
  156. its render on the editor page.
  157. - **Archive** a style from its ⋯ menu to hide it. An **Archived** tab shows up when you have any,
  158. with Unarchive and Delete. **Delete** moves the style to the Trash.
  159. - **Folders** in the sidebar filter your videos and styles. Drag a card onto a folder to file it.
  160. **New folder** is next to New style and at the top of Your videos.
  161. **Your videos** lists every video, with its editor page and a ⋯ menu (Remove from this list, Move to
  162. folder, Download, Move to Trash). **Clear working files** in Settings never deletes your clips, a cut,
  163. a final video or your notes.
  164. Files land in your library folder, or in a project folder you name: `videos/` (clips you dropped in),
  165. `edits/<name>/`, `clips/<name>/`, `product/<name>/` and `creator-teardowns/<handle>/`.
  166. ## Skills
  167. The editor is a set of Claude Code skills. Three of them help you with your own:
  168. - **logo pack.** Gets the official, brand-colour logo of every company, app and tool named in a video,
  169. checks each one and shows them on one sheet. The edit uses them, and shows logos named together side
  170. by side.
  171. - **skill improver.** Turns a finished video's notes into one-line rules in the style or skill that
  172. made it, after you say yes. It is what **Teach your style from this video** runs.
  173. - **skill maker.** Helps you build your own editing skill. It asks a few questions, runs the task once
  174. without a skill, writes three test cases, drafts the skill, tests it in a fresh agent and fixes it
  175. with you.
  176. For example, say **make a skill** and describe trial reels: short re-cuts of a reel you already
  177. posted, each with a new opening line and hook. skill maker writes the skill and tests it. Then
  178. **New style > Use your own skill** turns it into a style, so every video you make with that style gets
  179. the trial-reel treatment. Your skills live in your own folder and stay when the editor updates.
  180. ## Updating
  181. If you installed the plugin (Way 2), turn on auto-update once: in Claude Code type `/plugin`, open
  182. **Marketplaces**, pick **nextwork**, then **Enable auto-update**. Claude Code then downloads new versions in
  183. the background and loads them the next time you open it (or after `/reload-plugins`).
  184. To update by hand, type these in Claude Code:
  185. ```
  186. /plugin marketplace update nextwork
  187. /plugin update ai-editor@nextwork
  188. /reload-plugins
  189. ```
  190. If you cloned or forked the folder, say **update the editor**. Claude makes a backup branch, pulls the
  191. new version in, keeps your changes and runs the self-checks. If they fail, it takes you back to the
  192. backup. It never pushes unless you ask. Settings also shows when an update is ready.
  193. Your styles, skills and settings live in your library folder, not in the plugin, so they stay.
  194. ## What you can say
  195. | Skill | Say | You can paste |
  196. |---|---|---|
  197. | `start` | "edit my video", "make my video look like @creator", "new video" | a video file path; a Google Drive, Dropbox or OneDrive share link; a YouTube or TikTok link; a creator profile |
  198. | `setup` | "set up the editor", "finish setup", "add my Gemini key", "set up Modal" | |
  199. | `creator-teardown` | "break down @creator", "tear down @creator" | a TikTok, YouTube or Instagram profile, or single video links |
  200. | `cut` | "cut my video", "remove my mistakes" | a video file path |
  201. | `style-edit` | "style it", "add captions and zooms", "render the edit", "export to Final Cut" (or Premiere, Resolve, CapCut) | |
  202. | `overlays` | after a render: "add an animation here", "make a diagram of how this works", "this card is wrong", "swap the logo", "show the real page instead", "fewer cards" | |
  203. | `taste` | "captions too small", "fewer zooms" | |
  204. | `logo-pack` | "make a logo pack", "get the logos for this video", "the logos look fake" | |
  205. | `skill-maker` | "make a skill", "create a skill", "turn this into a skill", "help me write a skill" | |
  206. | `skill-improver` | "teach my style from this video", "turn my notes into rules", "make this feedback stick" | |
  207. | `clips` | "clip this video", "make shorts from my podcast" | a long video, a YouTube link, a podcast episode (Apple Podcasts, RSS, YouTube) |
  208. | `trial-reels` | "make trial reels of this", "test other hooks on this reel", "post the trial reels" | an approved reel, or its raw take |
  209. | `product-video` | "make a launch video for my site" | a website URL |
  210. | `update` | "update the editor", "get the latest version", "sync my fork" | |
  211. | `improve` | "improve the editor", "process suggestions" (for people working on this repo) | |
  212. `motion-design` is a reference the other skills read; you do not call it yourself.
  213. A Spotify episode is usually locked: paste the same episode from Apple Podcasts, YouTube or its RSS
  214. feed. An iCloud link opens a web page, not the file: download the video first and give its path.
  215. ## What it costs
  216. The editor is free. These are what you may pay for. Numbers marked *estimate* are worked out from
  217. published prices, not measured on a bill.
  218. | Part | Cost | Notes |
  219. |---|---|---|
  220. | Claude | Your Claude plan's usage | Not yet measured per video. The keys below lower it. |
  221. | Gemini key (reads a creator's look) | Free | Google AI Studio's free tier, no card. On the paid tier a 7-video teardown measured about $0.02. |
  222. | ElevenLabs key (keeps every "um") | Free for a few hours a month | Optional. Without it, Whisper transcribes on your computer for free. |
  223. | Render on your laptop | Free | Often the fastest for a short video. The styled 44.9-second cut of the sample take (1,346 frames) rendered in 35-84 s on a laptop also running other work; `edit.py estimate` was within 25% of the render in 3 of 4 tries. Claude prints the numbers for your video before you pick. |
  224. | Render on Modal | $0.03 for the 44.9-second sample cut (2.7 min on 3 machines, at Modal's rates). $0.18-0.19 for the whole 3.4-minute sample take rendered uncut (6,167 frames, measured on the bill). About $0.06 for 60 s and $0.54 for 10 min (*estimate*). | The Starter plan includes $30 of free credit a month. The uncut 3.4-minute take took 3.1 min on Modal (4.3 min when the laptop was overloaded during the join) and 6.8 min on a busy laptop. The first render also builds the render machine once (about 2 min). |
  225. | Render on GitHub Actions | Free | Counts against 2,000 free minutes a month on private repos. The 44-second sample cut took about 7 minutes. |
  226. | Render on AWS Lambda | A few cents to a few dollars (*estimate*) | Your own AWS account, card needed. Not measured yet. Claude quotes each render first. |
  227. ### Cloud renders
  228. - **Modal** (modal.com): your video is split into pieces that render at once on rented machines,
  229. then joined on your laptop. Say **set up Modal**; Claude walks you through the free account and
  230. logs this computer in.
  231. - **GitHub Actions**: free, no card. Claude packs the renderer and your footage into a **private**
  232. repo in your account (it asks first), renders on up to 20 machines and downloads the result. Say
  233. **set up GitHub rendering**.
  234. - **AWS Lambda**: many machines at once on your own AWS account. One-time setup of about 20 minutes.
  235. Say **set up Lambda rendering**.
  236. ## Your data
  237. - Everything runs on your computer unless you pick a cloud render. After a cloud render your footage
  238. is deleted from the service, unless you said to keep it.
  239. - A product video of a logged-in site uses its own browser profile, never your main one. You log in
  240. by hand, and Claude asks to delete the login when the video is done.
  241. - Names, emails and account details on screen are blurred by default, your own included.
  242. - It never clicks anything that creates, deletes, pays, publishes or invites unless you said yes
  243. for that video.
  244. - A suggestion you share to help everyone has your names, handles and web addresses removed first.
  245. ## Troubleshooting
  246. | Problem | What to do |
  247. |---|---|
  248. | Something is missing or broken | Say **run the editor doctor**. Every line reads `ok`, or `FIX` with the exact command for your computer. |
  249. | Doctor says something moved off the pinned versions | Say **repair the editor setup**. Claude runs `setup.py repair` from wherever the plugin is installed, and it puts the exact pinned set back. From a cloned folder (Way 1) you can run it yourself: `python3 plugins/ai-editor/skills/setup/scripts/setup.py repair` (`py` instead of `python3` on Windows). |
  250. | You skipped a key or step | Say **finish setup**. Only the skipped steps run. |
  251. | Where do Claude's questions show up? | In the editor's window or review page when one is open in front of you; answer there. Otherwise in the terminal. Permission prompts (Allow or Deny for a command) always show in the terminal. |
  252. | Claude does not know "edit my video" | The editor is not loaded. Type `/reload-plugins`, or install it with Way 2. |
  253. | `python3` not found | Mac: `brew install python`. Windows: `winget install -e --id Python.Python.3.12`, then open a new terminal. Linux: `sudo apt install -y python3 python3-venv`. |
  254. | Node is too old on Debian or Ubuntu | Doctor prints the fix: it adds NodeSource's signed package source, then installs Node. |
  255. | Chrome or Chromium installed as a Flatpak | Only logged-in product videos need your Chrome, and a Flatpak one cannot be used. Install Google Chrome or your distro's `chromium` package; doctor says which it found. |
  256. | A tool installed on Windows is still "not found" | Close and reopen Claude Code: a `winget` install only shows up in a new terminal. |
  257. | `yt-dlp returned nothing` | The site changed. Doctor shows how to update yt-dlp, or paste single video links. |
  258. | An Instagram profile fails | Instagram has no free way to list a profile. Paste 10 or more reel links. |
  259. | `Gemini rejected the key` | Make a new key at the link it prints. The teardown carries on without it meanwhile. |
  260. | A Drive or Dropbox link fails | Share it as **Anyone with the link**, and link the video file, not the folder. |
  261. | `the Modal render failed` | Claude offers the laptop render instead. |
  262. | You logged into a site for a product video and want that login gone | Say **log me out of <site>**. Claude runs `login.mjs logout <site>`. From a cloned folder (Way 1): `node plugins/ai-editor/skills/product-video/scripts/login.mjs logout <site>`. |
  263. | Where are my keys? | `~/.config/creator-teardown/.env`, shared by both plugins. With `AI_EDITOR_HOME` set, `$AI_EDITOR_HOME/.env` instead, and the shared file is never read. |
  264. Without Claude, from a cloned folder (Way 1), one command does the whole install and is safe to re-run:
  265. ```
  266. python3 plugins/ai-editor/skills/setup/scripts/setup.py bootstrap
  267. ```
  268. Every install gets the same versions: Python packages from a hashed lock file
  269. (`plugins/ai-editor/requirements/requirements.lock`), Node packages from `package-lock.json`, and
  270. each model checked against its sha256.
  271. ## License
  272. This repo is MIT. See [LICENSE](LICENSE) and [NOTICE](NOTICE).
  273. The tools it runs have their own licences:
  274. | Tool | Licence | What it means for you |
  275. |---|---|---|
  276. | [Remotion](https://www.remotion.dev/license) (the renderer) | Remotion License | Free for individuals and for companies of up to 3 people. Bigger companies need a Remotion company licence. |
  277. | [GSAP](https://gsap.com/community/standard-license/) (animation in the renderer, and the `gsap-skills` plugin) | GSAP Standard License | Free, commercial use included, every plugin too. Not an OSI open-source licence. It bans using GSAP in a no-code visual animation builder that competes with Webflow's. |
  278. | [HyperFrames](https://github.com/heygen-com/hyperframes) (the `hyperframes` plugin, and code ported from it) | Apache-2.0 | Free. Ported code keeps HeyGen's copyright, listed in [NOTICE](NOTICE). |
  279. Assets fetched while editing: brand logos from [Simple Icons](https://simpleicons.org) (CC0), icons
  280. from [Lucide](https://lucide.dev) ([ISC licence](https://lucide.dev/license)).
  281. ## Contributing
  282. - The rules every video follows, for every user:
  283. [plugins/ai-editor/PRINCIPLES.md](plugins/ai-editor/PRINCIPLES.md).
  284. - Open this folder in Claude Code and say **improve the editor**: the `improve` skill turns the
  285. corrections users marked "would help everyone" into rules, checks and tests here.
  286. - What is next: [docs/BACKLOG.md](docs/BACKLOG.md). What changed: [CHANGELOG.md](CHANGELOG.md).
  287. - In this folder the editor loads from your working copy. To turn it off while you work, set
  288. `"ai-editor@nextwork": false` under `enabledPlugins` in `.claude/settings.local.json`.
  289. - Run the checks before a pull request:
  290. ```
  291. python3 tests/check_plugins.py
  292. claude plugin validate --strict .
  293. python3 tests/smoke.py
  294. ```
  295. plus each script's `demo` (the list is in `.github/workflows/check.yml`). The model evals cost
  296. money; `tests/run_evals.sh --runs 1 --case <case>` runs one.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.